On 14 janv. 2010, at 00:33, Romain Robbes wrote: >>> >>> >>>> Future work: integration in the browser :) >>>> >>> >>> How do you envision that? I tried to not be too browser-specific, as these >>> things are moving targets. >> >> I would not integrate that in browser because it makes the state machine of >> this brittle tools brittler and like that you >> can focus on working set functionality vs browser bugs :) >> > > If anything, WorkingSet makes code browsers look like disposable entities. It > opens so many of them that it even includes a shortcut to close all the > windows opened by it :-).
I was thinking of a browser focused only on items displayed in a working set. However, this is a slightly different definition of working set (one where you can also pinned down some entities). One problem I noticed but related to completion (because I also have this problem with the mercury search bar). When completing a keyword message, spaces are automatically inserted between keyword to put parameters. This fails the search because it does not take the full message, only a part of it. On a sidenote, it seems that installing WrokingSet deactivates the shortcut to Algernon (shift-return). Can someone confirm? > > What I would like to have now is a better window placement, with > possibilities to tile windows. > Has anybody done something like that already? I think that Stéphane did a bit of hacking at one point :) I know the logic is in the RealEstateAgent class. At one time, I thought that making the window appears with the title bar right under the mouse pointer could be a good idea. If the window placement does not suite you, you can click and move the window. Besides, if you open windows through the world menu, that means you clicked in an empty space right before, so good location to start. -- Simon _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
