On Fri, Dec 18, 2009 at 1:39 PM, George Herolyants <george.herolyants@gmail.com> wrote:
2009/12/18 Michael Rueger <m.rueger@acm.org>:
Henrik Johansen wrote:
Interestingly enough a lot of the (complex) multiple native window applications have (gone back to) all in one window UIs (Eclipse, all of the Adobe products, ...).
Yeah! That's true. And their look&feel may differ from the underlying os. And everyone uses them without complaining. So what's wrong with pharo? Maybe one of the weak points is that it simulates windowing system inside another one, when other applications (Eclipse, Netbeans...) have strongly defined layout (though customizable)? I think it's a real issue. Pharo Development Environment is *Integrated* but the UI still lacks this integration in some places, IMHO.
But I think multiple windows in the meaning of what for example firefox has will be helpful as well. I mean two or more usual pharo windows "connected" to the same image. Is that possible?
And native basic dialogs may be helpful too, to not reinvent the wheel (aka FileBrowser :).
I vote for the WhiskerBrowser with all the cool OB stuff integrated! ;)
Cheers, George
Hi, you may be interested in SeasideXUL project (http://code.google.com/p/seasidexul/). The rendering of UI with native look&feel is a responsibility of the standard Mozilla XULRunner and there may be several clients connected to one image. However the OmniBrowser binding and code editor is not in the production ready state now. Cheers, -- Pavel