<div class="gmail_quote">On Wed, Apr 9, 2008 at 2:21 AM, Igor Stasenko <<a href="mailto:siguctua@gmail.com">siguctua@gmail.com</a>> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
What i like in above, that it's self-explanatory, easy to find and<br>
don't requires extra UI/GUI to manage package.<br>
Any developer can describe/define own package in a few minutes as<br>
simple as writing a method!<br>
Just choose appropriate name for a method, like #packageConfiguration.<br>
Then anyone can browse all packages by hitting implementors. :)</blockquote><div><br class="webkit-block-placeholder"></div><div>I don't think whether something requires an extra GUI or not should weigh heavily in evaluating something. With a better browser, you could accomodate a greater variety of things. Years ago, similar thinking led to the use of classes and inheritance to define exception hierarchies and I think that was a mistake. I implemented the original exception handling system for ObjectStudio and I patterned it after the VisualWorks instance based approach (it was instance based then, a sort of hybrid now). Then the ANSI standard came along and I re-implemented it on the theory that standards compliance was of greater importance. But, I felt, and still feel that the instance based approach that VisualWorks had originall was simpler and superior despite not being browser friendly.</div>
<div><br class="webkit-block-placeholder"></div><div>- Stephen</div></div>