<br><br><div class="gmail_quote">On Mon, Sep 6, 2010 at 1:59 AM, Hannes Hirzel <span dir="ltr"><<a href="mailto:hannes.hirzel@gmail.com">hannes.hirzel@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 9/6/10, Eliot Miranda <<a href="mailto:eliot.miranda@gmail.com">eliot.miranda@gmail.com</a>> wrote:<br>
> Hi All,<br>
><br>
> while all these cool new browsers are great I get on well with the<br>
> standard browser and my multi-window hack around it.<br>
<br>
</div>Interesting,<br>
What do you mean by multi-window hack, Eliot?<br></blockquote><div><br></div><div>In trunk go to preferences browsing and enable Multi-window browsers, then open a Browser. Use e.g. find class to ... find a class. Then use find class to ... find another class; voila the window label says 2. SecondClass. If you mouse in that label with the left/red button you'll find its a drop-down menu which selects between different browsers that now share the same screen real-estate. I depend on this; its a cheap tabbed browser implementation and at least for me I like its light-weight - IMO tabs steal too much screen real estate. The scheme marks changed browsers as red entries in the multi-window menu and won't discard edits in any of the other browsers on close without confirmation, etc.</div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<font color="#888888">--Hannes<br>
</font><div><div></div><div class="h5"><br>
But the multi-window<br>
> hack shows up one major weakness with the default Browser, and that is it's<br>
> use of list indices (systemCategoryListIndex classListIndex<br>
> messageCategoryListIndex messageListIndex). These should just be<br>
> systemCategoryName, className, messageProtocol (categories are in<br>
> System-Organization; classes have protocols) messageSelector. If this<br>
> happened the indices the browser has into the system would never become<br>
> obsolete as does happen for example when one adds a class to a category,<br>
> invalidating any classListIndex values into the same category,<br>
> or systemCategoryListIndexes as happens often when the SystemOrganization<br>
> changes on loading a package. So if anyone is looking for a small useful<br>
> project, someone who probably has RB chops, how about reimplementing Browser<br>
> so that it is essentially unchanged except for the indexes being ripped out,<br>
> buried and stomped on?<br>
><br>
> If someone did this I'd get round to using menu pragmas throughout and<br>
> integrating the RB into the base Browser.<br>
><br>
> cheers<br>
> Eliot<br>
><br>
<br>
</div></div></blockquote></div><br>