Experiment (for review)

[wasnotrice]

As a first exploration of brown shoes, I tried moving Swt into the Shoes namespace, so SwtShoes::Button becomes Shoes::Swt::Button and so on. Motivation: make the various flavors of Shoes feel like one integrated project (from a user perspective).

require 'shoes/swt'

vs

require 'swt_shoes'

But mainly I'm just getting my feet wet with the code. @pjfitzgibbons what do you think?

[pjfitzgibbons]

Did that once and it got very ugly.
Also discovered that the multi-GUI framework need more decoupling.
You'll notice in the current HEAD that the frameworks are completely
separate from the base, and that the frameworks provide implementations to
the hooks that are called in Shoes.

May I fwd this to ML for wider discussion?

And thank you sooo much for looking at this! You represent the first
code-review and think-through, and I appreciate it greatly.

Thanks,
Peter Fitzgibbons
(847) 859-9550
Email: [email protected]
IM GTalk: peter.fitzgibbons
IM AOL: [email protected]

[wasnotrice]

I really like the way you have decoupled the frameworks. I do not actually envision the code ending up all in the same repo, just in the same namespace. It could be similar to datamapper, as an example, where you can get the whole ball of wax, or just the pieces you need. I didn't re-couple anything in this refactor, just adjusted the namespacing.

I can see how it could get messy--in fact, I had thought that it wouldn't work, until I started reading your code. Having some this exercise, I do think it's possibly to use a single-rooted Shors namespace and maintain the decoupling you have established. Perhaps it's just a matter of style.

Re: ML, of course, forward away! It might be helpful to get some more insights

[pjfitzgibbons]

Eric, is this change a dependency of your subsequent pull requests?
Wondering if I absolutely need to merge this immediately ?

[wasnotrice]

Peter, no, you do not need to merge this one. The other work is done within the pre-existing naming scheme. This was intended as a conversation starter :)

[pjfitzgibbons]

I'd be ok with moving on this one. I didn't originally understand your
change. I think your change is ok.
Tell me if you'd like help on this one.

Kindest Regards,
Peter Fitzgibbons
(847) 859-9550
Email: [email protected]
IM GTalk: peter.fitzgibbons
IM AOL: [email protected]

On Thu, Apr 26, 2012 at 5:39 PM, Eric Watson <
[email protected]

wrote:

Peter, no, you do not need to merge this one. The other work is done
within the pre-existing naming scheme. This was intended as a conversation
starter :)

---

Reply to this email directly or view it on GitHub:
#3 (comment)

[wasnotrice]

At this point, I would recommend that we work on the other pull requests first, and then come back to this one. The merges will be painful if we do this one first. It won't be hard to extend this naming change out if it's what we decide to do.

[pjfitzgibbons]

Agreed
Peter Fitzgibbons
(847) 859-9550
Email: [email protected]
IM GTalk: peter.fitzgibbons
IM AOL: [email protected]

On Fri, Apr 27, 2012 at 11:18 AM, Eric Watson <
[email protected]

wrote:

At this point, I would recommend that we work on the other pull requests
first, and then come back to this one. The merges will be painful if we do
this one first. It won't be hard to extend this naming change out if it's
what we decide to do.

---

Reply to this email directly or view it on GitHub:
#3 (comment)