Yes, I will take a look and give my opinions. But on the face of it there are two situations I grapple, one that is useful for me and the other is: useful for newbies who are not the sharpest of lot in a corporate env. Provide an IDE that starts integrated and provides the option to split out windows for the views needed in complex situation as also our sliding sender/ implementer browser ( the TrailBlazer from VA long time back) have its particular use.. Parallels: Debian >> Ubuntu >> Linux Mint.. Interesting viewpoint of Gaucho, I do believe there are similarities to what Gilad argued for in Newspeak.. Vassily worked on. I am not able to download the package though for lack of userid-pwd. On Thu, Feb 16, 2012 at 2:54 PM, Fernando Olivero <fernando.olivero@usi.ch>wrote:

I was just pointing out difficulties with the single-windowed tabbed panes view.

People can chose whatever they prefer, but its undeniable that these type of interfaces hamper with looking at simultaneous views of the system, and making use of placement for remembering a task context, recently there has been research on this area.

I believe this discussion is interesting, because we should re-evaluate pros and cons of the traditional user interfaces, that have been around for long now.

I would like to hear your opinion on the benefits of such interfaces, besides the fact that mainstream IDE's adopted it, it's not that i don't like Eclipse , is more that i'm aware that several difficulties have been found with these type of interfaces.

Fernando

[1]http://dl.acm.org/citation.cfm?id=1062492 [2] http://dl.acm.org/citation.cfm?id=1806866 [3] http://dl.acm.org/citation.cfm?id=1810295.1810331&coll=DL&dl=GUIDE&CFID=8516... [4]http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=6070389

On Thu, Feb 16, 2012 at 10:07 AM, S Krish <krishnamachari.sudhakar@gmail.com> wrote:

...

GroupWindowMorph is quite capable.. and nice..

#configureForEmbedding needs to be implemented to get it right though across all windows to remove the topLabel, and any other change reqd.

Also a System Setting for the default: Open the window in this Tabbed Pane only.. else explicitly open it in World.

TabbedPane needs to then behave like an IDE , everything opens as a tab ( optionally right click detach to World ).. also a File Browser on left optionally for external file access with default viewer tabs for each type recognized..

As others comment this is only an optional package.. not imposed for those who are accustomed to the current multiple window paradigm.

Ofcourse the eclipse IDE is a complicated hunk with stuff we do not require in Pharo including refactoring which is per browser if OB based.. or another with RB integration.. as also the long list of menu options, right click options..can be pared to the minimum.

On Thu, Feb 16, 2012 at 2:06 PM, laurent laffont < laurent.laffont@gmail.com<mailto:laurent.laffont@gmail.com>> wrote: Hi,

In TWM, Pharo 1.4, there's GroupWindowMorph that can embed any kind of window as tab.

Take a look at http://magaloma.blogspot.com/2011/07/twm-docking-windows.html , 0'56

Find attached the changeset for GroupWindowMorph. File in using last Pharo 1.4 and:

(GroupWindowMorph new openInWindowLabeled: 'Window organizer') extent: 400@400.

Cheers,

Laurent

On Thu, Feb 16, 2012 at 7:15 AM, S Krish < krishnamachari.sudhakar@gmail.com<mailto:krishnamachari.sudhakar@gmail.com>> wrote:

Just this quick n usable prototype.. ?

Any comments of its utility.. I for one would rather prefer having everything navigable from one Tabbed Pane..

Panes capable of rendering about every window of the basic tools of Pharo.. workspace, Finder, ScriptManager, possibly Transcript as a console collapsible as reqd

Akin to the eclipse but not really that intensively single windowed.. there are uses for spawning separate windows..