Stéphane Ducasse wrote: > I agree. :) > I would love to have that. > this is why we should really have a system to experiment these ideas. > >
The Glamour framework looks useful for browser experimentation. I would really like a modern version of the Whisker browser Doug Way created. > On Sep 12, 2009, at 6:15 PM, Philippe Marschall wrote: > > >> Stéphane Ducasse wrote: >> >>> well for this we will have to rewrite paragraphEditor :) >>> So in making pharo moves forward we will have to accept losing some >>> feedback. >>> >> The feedback is still there. The piece of code is still marked as a >> problem. It just doesn't get in your way. >> >> >>> But yes your idea is cool. >>> >> You'll have to do more than that. I think this whole 80ies style >> browser >> that's based on scrolling, clicking and popups doesn't cut it anymore >> and adding more tabs and buttons isn't gonna fix it. >> >> Example, why is the browser the size it currently is? Because that was >> more or less full screen in the 80ies. Consequence you'll always >> have to >> resize and scroll when you open a browser because the category and >> class >> panes are too small. I see how this was cool, exciting and new in the >> 80ies but today it gets in my way. >> >> Example, I want to go to a method in a class. Either I click '--all--' >> and scroll, scroll, look, scroll, scroll back or I click through the >> protocols until I found on it. When I'm in Eclipse and want to open a >> variable or method declaration I hit Ctrl + O, Eclipse shows me a >> short >> outline of the class. Like in Firefox Awesome Bar it filters the >> list as >> I type part of the name. Once I select something it closes and goes >> there. Zero mouse activity. Zero additional window. When I'm in a >> method >> and want to go to a method invoked there either I Ctrl + click it or I >> hit F3. When I want to see the hierarchy of a class or the inheritance >> of a method I just do Ctrl + T and an inline window opens. It closes >> when I select something or hit Esc. Pharo stacks so many windows on >> top >> of each other that you're never going to find your way back. So at the >> end of the day you just close dozens of windows. >> >> Short anecdote, I our current project we don't ask the user for >> confirmation, ever. If he decides to delete Migros, we do it without >> asking. The previous version of the product did but users just >> developed >> a reflex to click popups away without even reading them. >> >> And don't get me started on breakpoints. Or blocking the UI. >> >> Cheers >> Philippe >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project@lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project@lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
