Created attachment 70980 [details]
tabbed interface

*** Bug 127149 has been marked as a duplicate of this bug. ***

Created attachment 71482 [details]
Close Confirmation Dialog

the screenshot shows a close confirmation dialog, when closing multiple projects.

Created attachment 73061 [details]
new glade ui sneak peak

Here's a patch that implements embedded toplevels, with the behaviour and user interface that we expect the final patch to provide.

Some data structures and code will change in the final patch, as I created this implementation in much haste. I am still thinking of how to tie everything together.

note: I have also removed the tabbed interface. I think it was a bit premature to implement it, since the main goal in this development cycle is just to get the embedding of toplevels working.

couple of random thoughts/comments that I had at the moment

  o the property editor pane should have more space allocated by default
    so that when a widget is initially selected we can see the whole
    editor

  o should have a method to expand all/collapse all in the project-view

I noticed that when using this new UI that when I type a handler in the signal list for a widget, hitting delete doesn't delete text, but the entire widget itself. 

Other than that though I love the new UI and I hope it'll be incorporated in a release some day :)

Notes:
  One thing we should be able to easily support with the embedded windows
  and overlayed input GdkWindow - is tabbed/arrow keyboard navigation for
  widget selection in the workspace.

  We can probably also take a whole new simplified aproach to drawing
  selection on widgets (we can also easily make a different visual effect
  for "focus" and for "selected" - to give the user access to multiple
  selection w/ keynav).

In our integrated ui so far, the placement of the selector button leads to some wasted space [see screenshot posted below] and visual inconsistency. Placing the button on the main toolbar instead would improve the user interface somewhat.

Created attachment 74749 [details]
screenshot of selector button placement

nod, 
    the palette should still have at least an option to show
the selector or not (maybe a "show-selector" property), so that
the palette still makes sence as a stand-alone component 
(from the libgladeui api point of view)

if we ever have a dockable palette in the glade frontend - I think
the selector would have to appear when the palette is detatched.

Created attachment 75138 [details]
another screenshot (with detached selector button)

I am closing this bug since it's a bit vague and doesn't describe specific problems. We should report specific UI bugs instead.