Kjell,
I apologise for my apparent denseness but I can’t work out what you’re asking in the context of my suggested changes to Browser building. If you could perhaps explain a bit more?

> On 24-10-2017, at 3:20 PM, Kjell Godo <squeaklist at gmail.com> wrote:
> 
> i have Methods which have case statements in them which switch off of the Method inputs which act like command line options. so there might be seven different options and seven different cases. do you think that these cases should be separated out into seperate Methods( equal selector prefixes ) one for each of the cases?
> 
> i sometimes feel that if the cases are all similar then it is easier to see the similarity if you can just scroll text up and down.  so just use a case statement.  but it does get more messy upon first glances. but separating them out into seperate Methods is more to the standard.
> 
> But in Dolphin i also have a Tree browser which allows traversing the seperate Window tree bullets keyboard only which can have the same effect as scrolling text so. because you can set up each Window seperately once and it will remember it. but with the SystemBrowser i have to scroll the text of each Method i come to to get to the code and by then i lose track. i suppose i could make a tree file which has these seven Methods in it and i could then get the same eye ball effect as scrolling text. i should try it. or i could get rid of the initial comments at the top of each Method which are according to a repeated template. yes i should probably do this. that way i would not have to scroll text as much and then the SystemBrowser might be good enough more.


tim
--
tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
A bug in the code is worth two in the documentation.