Jürgen Schmidt wrote:
[EMAIL PROTECTED] wrote:
Hi Joachim,
Quoting Joachim Lingner <[EMAIL PROTECTED]>:
Unfortunately I cannot integrate it right away. We still have to figure
out some special cases. For example, what happens if the office was
started by OOoBean and then a user starts OOo. Both are using the same
office. If now the OOoBean wants to terminate the office, what is the
correct way to do.
Or the user wants to terminate the office and is not aware of the
OOoBean which prevents that. Is there a user notification required?
I the patch I sent, I tested this case: the bean connection is simply
stopped: I
found very stupid to terminate the whole office if the user has
another document
opened on the desktop.
The whole problem is not trivial because the relation between an office
instance and an application using the OOBean is not necessarily known to
the user. One of the question is if it really make sense to use the same
user configuration for a normal UI office (the office the user normally
use) and an application using the OOBean? Should two beans use two
different user configurations also? And a lot of more questions should
be answered.
But of course your patch (slightly modified) can be used to fix the
terminate problem for the moment.
And in the same step we should disable some commands in menus and
toolbars (e.g. File->Exit, Window->Close Window) or should disable
complete menus, toolbars which can't work proper in the bean context.
The function or better the behaviour of the bean isn't exactly specified
for all use cases and that is one major problem. There is too much
space for things that work per chance, people count on it and exactly
this solutions get broken if something changed for the UI office change
the bean behaviour as well.
Juergen
A bean application have influence to the UI office as well. For example
if the bean application is running you can't use File->Exit in the UI
office which of course can be really confusing for the user when the
relation between office and bean application is not known.
Using a terminate listener is probably not the best solution here,
better is a close listener at the frame. In this case all UI windows get
closed when File->Exit is called but the office process would be still
running because of the bean (implementation detail ;-), it's not
guaranteed).
But i am sure that it is very simple to find other constraints where the
current implementation is not exactly that what the user expect and
which of course is not exactly specified.
So the patch from Cedric is not enough here and we have to do a little
bit more.
Juergen
So there are still a few open question. If I know more I'll write it in
the issue, so you will be notified.
I don't have enought time right now, but I would like to know which
questions
are still opened: to my mind there isn't so many cases to study.
Cedric
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
