<div dir="ltr">Hi Marcel,<br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Feb 27, 2015 at 10:02 AM, Marcel Taeumel <span dir="ltr"><<a href="mailto:marcel.taeumel@student.hpi.uni-potsdam.de" target="_blank">marcel.taeumel@student.hpi.uni-potsdam.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">At the moment, programmers can do three things with message categories:<br>
<br>
1. Define their name.<br>
2. Define their content.<br>
3. Define their order.<br>
<br>
Naming is already difficult. Finding the right place for a message can be<br>
challenging, too.<br>
<br>
The thing is that order gets messed up pretty quickly. For example,<br>
extension categories just popup somewhere in between depending on the<br>
projects you have installed.<br>
<br>
My general impression is often that those categories just have *some* order<br>
and *want* to be alphabetized to make any sense out of it. I am not sure but<br>
w/o describing the intent of an order, it may just appear bogus to a<br>
programmer.<br>
<br>
Personally, I am really happy with anything that I do not have to organize<br>
or care for. Message category orders are such a thing. :-)<br>
<br>
But don't get me wrong: I don't want to push my personal expriences onto<br>
everybody. Let's discuss it here. ;-)<br></blockquote><div><br></div><div>Personally I find ordering of protocols really helpful for productivity, especially with complex classes such as the VM's interpreter classes. These are >100 method classes. I do things like put all the bytecode protocols, stack bytecodes, send bytecodes, return bytecodes, etc, next to each other (which of course doesn't work with alphabetization unless one rewrites to bytecodes-stack etc). I was /mortified/ the first time I loaded VMMaker into a clean image because Monticello *does not record protocols order*. I wish this would be fixed. I find myself alphabetising and then, for certain classes, such as the interpreter, carefully putting things in order. This is wasted effort. Monticello really should preserve order. I have no objection to a preference that tells the browser to display protocols alphabetically. Please don't make it the default. When we did this for VisualWorks (I think it was Vassili Bykov) we ordered initialize protocols at the top, private protocols at the bottom, and everything else in the middle.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
Best,<br>
Marcel<br>
<br>
<br>
<br>
--<br>
View this message in context: <a href="http://forum.world.st/The-Trunk-Tools-mt-534-mcz-tp4808262p4808408.html" target="_blank">http://forum.world.st/The-Trunk-Tools-mt-534-mcz-tp4808262p4808408.html</a><br>
<div class=""><div class="h5">Sent from the Squeak - Dev mailing list archive at Nabble.com.<br>
<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">best,<div>Eliot</div></div>
</div></div>