> > > I am horrified with all these colored icons on methods. That's worse > > > > > than in the old browser with the button that had 8 different colors > > depending on the state of the method. > > > > Uh? > Lukas I think that david is spending a lot of time on improving the browser > so I would suggest you to be less aggressive and more bringing suggestions.
I am sorry, I did not intend to be aggressive. I tried to give a list of suggestions to improve and simplify the interface. I am only talking about my personal experience using the browser enhancements and how I am confused with all the method icons. The icons are not intuitive and their priority is unclear. I need to keep the wiki open to understand them. > > - I don't want to see part of the "contents" of a method as an icon. > > The super-icon is useless, it only hides valuable information (for > > example that there is a sub-implementation). If I want to know if a > > method calls super (and when) I need to look at the method anyway. > > No I'm sorry but I disagree. > Knowing that there is a supercall is as important as knowing that the > method > is specialized. I think it is misleading. There are methods that only call super under certain conditions or even call different super methods. This might lead to wrong assumptions. > Look at LimitedWriteStream you get instantanly the fact that the three > methods are doing a super send! > and this is really important to know. Again, I think it is most important to see at one glance if there are super and sub implementations. This is the only thing I can't find out with a single click and without loosing the context. In the current implementation this information is sometimes hidden. > > - The same is for abstract method icon. When browsing the > > protocol/interface I don't need to know that. I am more interested if > > any of the subclasses override it. > > No this is your point of view on that. But knowing that a method is > abstract > is useful too Maybe, but it should not hide more important information. > > - The same for extension methods. I see that, because it is in a > > different protocol and because its name is in italic (the same as with > > the extension classes). I don't need yet another icon. > > It depends on which browser you are. Reinforcing the information is often > good. What I am criticizing here is that information is duplicated (icon and category) and not consistently displayed (classes with extension methods are italic, methods have a special icon). > > The only valuable thing for me as a developer is to know if there is a > > super/sub implementation of a method. And maybe if there are halts > > inside. > > Sorry but knowing that there are self flag and halt is extremely valuable. I agree. > But we do not want that click. > I do not know to click on all the method of my class to see if they all do > a supercall. Then we should move to files where we see all the source at one glance ;-) An icon can only tell yes or no. In most cases (such as with super calls) the situation is more complicated. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
