Hi Peter, Christoph,
I've followed this thread with interest, because it's a use-case when
supporting conversions from the old (MsO) to the new (OOo).
Some comments in-line:
Peter Eberlein wrote:
Hi Christoph,
After balancing pros and cons:
Agreed to solution (2).
+1
With the rich text control you have formatting options, with TextFields
you don't have (for a part of the inserted text, and IIRC Microsoft Word
doesn't have it too).
That is correct.
With other fields (date and numerical types) you have formatting
options, which you will miss with TextFields in the current
implementation, and the Word textfield has some of this options too.
Correct.
But how to jump with the tab key? The checkboxes (or radiobuttons) will
then be a foreign matter in this context.
Using the alternative 2, the TAB-navigation should be easily be
implemented with a new eventListener that listens for Key-Events and a
special handling for the TAB-key.
Don't know if this would be easy, because the listener has to know which
type of "jump-to object" (may be a checkbox control or a field) is the
next one to focus...
What I didn't read in this thread (or just missed it) is that in MsWord
the tabbing from one field to another works if the document (or section)
is protected and restricted for filling in forms.
And don't forget: Word has for example two types of CheckBox objects,
one for filling forms and with the look and feel of text fields (form
bar), and one similar to the OpenOffice one (in the controls toolbar).
May be doing this way in OpenOffice too would be the best to fit the
needs of the user.
That means:
1. Reworking the behavior of the input field (no popup, formatting
options, standard size)
In some cases, the current popup behaviour is very useful. Thus I would
like to make both possible. However with conversion of MsO, the no-popup
would be best.
2. Implementing a new field type "checkbox" (a type "radiobutton group"
would be a nice to have feature), binding the state of the field to
variables like input fields do.
The latter is important, because if you have a form with 30 paragraphs
(each with a checkbox) and only two are checked and should be printed,
you can achieve this easy with fields (hidden paragraphs). Until now you
have to realize this with macro programming.
Yes, both radiobuttons and checkboxes will be necessary to make
conversion work.
3. Binding the selected value of the list field to variables, popup
necessary?
Can't remember I've seen that in MsO.
It is important to have the protected-tab-and-fill-in-forms work in OOo.
However, bulding too much intelligence, possibilities in it, might be
overdone. Because then business logic would point towards database apps
and the apropriate (X-)forms.
4. Implementing the tab key behavior for all those fields
5. Extending the service com.sun.star.document. It has a boolean
property "AutomaticControlFocus". Here we need a similar option for fields.
As you added later: com.sun.star.Officedocument.
Regards,
Cor
--
Cor Nouws
Arnhem - Netherlands
www.nouenoff.nl
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
