Re: [framework-dev] Google Summer of Code 2005 - Tabbed Document Windows

[Andrzej Wytyczak-Partyka]

On 8/15/05, Andreas Schlüns <[EMAIL PROTECTED]> wrote:

But .-)
there are 2-1/2 weeks left .. so we can start the optional part.
It would be nice if you can implement the support for multiple tab
controls. Here the idea:

a)
Your service can be triggered within two methods
- createInstance() and
- createInstanceWithArguments().

createInstance() should open the new frame inside the TabControl, which
is currently the active one. createInstanceWithArguments() should
support a new parameter (name it e.g. "[bool] NewTabControl=true"),
which force creation of a new TabControl before it creates a new frame.
createInstanceWithArguments() without this new parameter has to do the
same then createInstance().

b)
The decision if this new property is used or not has to be done inside
OOo. I will take over this part. Currently it's easy to workround this
missing functionality  inside OOo. You can trigger a
createInstanceWithArguments(NewTabControl) call e.g. from basic
manually. For testing purposes it should be enough.

Your component has now to handle more then one TabControl/ more the one
ParentWindow/ more then one TopWindow.

Hopefully you can implement this feature too (after you got the missing
sleep you mentioned) .-)

Hi Andreas !

I have some ideas on this, but I would like to clarify something.
Since I have to use more than 1 control, I have to know which control
I should be currently using, right?

I'd say I need a vector for holding the tab controls and references to
their respective TopWindows, list of ChildWindows, etc.

What would this multiple control feature be used for?

Regards,
Andrzej