Congratulation Andrzej !
You finished the non optional steps A, B and C. So we can say: you
reached the goal to implement a "Tabbed Document Windows" environment
for OOo.
There are some small cosmetic changes needed before this component will
be realy useable inside OOo as product - but these changes requires some
redesigns of the feature set of the office itself.
I would say you can provide this component as AddOn to your group of
"beta tester" (you mentioned some mails before).
=======================================================================
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) .-)
Best Regards
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
