On 18 janv. 2010, at 19:50, Lukas Renggli wrote:
Thanks Lukas. Indeed, it worked and that was the difference between to images. I will set it again for next image. I think it is useful and it was in the previous images. It was my mistake.
Anyway, you don't use PharoDev images ;)
Now...what's "screen state" ??
estate, an area or amount of land or property, in particular
Some people never use the mercury panel, some never use the annotation panel, some never use the button panel. For them, the panels they never use, is a waste of space and time.
The question is if anybody is really using and understanding it (other than just typing a class name)? If I remember correctly it is planned to remove the code from OB.
Yes I use it all the time. I find it more usable than Algernon or even Working Set when I'm looking for class refs/method users. In O2, there is a help text by default which sums up the syntax: - AClass (starting with upper case) when looking for a class - aMethod (starting with lower case) when looking for a method - #AClass, references to AClass - #aMethod, senders of aMethod - 'hello world', look for substring 'hello world' in method strings Of course it is also completion-enabled :) It would be cool if it had a shorcut for Siblings, like in WorkingSet - !AClass - !aMethod It's also true that it eats space for each browser. I think it's should be easy to put a unique search field in a task bar. As part of my Morphic experiments, I played a bit with this idea. As an example, you can perform the following in a workspace (unfortunately it opens two browsers, but should be difficult to tweak). (OBMercuryQuery from: '''hello''' panel: (OBPanel new browser: SystemBrowser default browserClass open model)) find -- Simon