Apache OpenOffice (AOO) Bugzilla – Issue 3029
WW: Import form fields as input fields to get better layout
Last modified: 2013-08-07 14:43:23 UTC
Apparently the creator of the MS Word doc used some kind of text boxes that OpenOffice's import filters can't interpret? Send me an email at hroush@largo.com requesting the MS Word file and I will send it to you.
JA->MRU: reassigned to you
MRU->CMC: there´s a FormField which contains a lot of text. The filter converts it to a very big Control which is wider than the page in StarWriter. My questions/suggestions for this are: 1. Limit the width of such a control to page width or text area width on import 2. enable the "line break" feature for such controls on import What do you think about it?
added CC
It sounds like a reasonable idea to set the max width to the max available width and to turn on multiline seeing as line breaks are allowed in these word textfields. But there would still probably be a lot of problems because we would still not know the correct height to use for a multiline textfield. Figuring out how many word fit on a line etc to get the number of lines and then guessing the fontsize to calculate the controls true height would really require laying out the document first. All these layout problems with these textfields is because our controls are of fixed size, while those word fields are flexible in length. I wonder what would happen if we used our input fields for these instead ? Our controls are really like word's other form controls, the vba controls, while our input field looks more like these type of fields. An input field is flexible in width as well so the layout would be good. And all those problems of ugliness and hard to format issues would then go away. On the minus we would loose being able to support some of the "help" options, but on the plus side I think we would be able to use some of the "Type" information because we can make out input fields fill in variables and allow only date/time/number etc, just like word. Would there be any problems in changing the import of textform fields from uno controls to input fields that I haven't thought of. I'd prefer to attempt to import them as input fields that keep hacking around the problems of the uno form controls.
'I think, we should invoke Falko into this "discussion".
I think, we should try out Caolan's proposal. I think, using our "Inputfield" for import on Word's FormFields. This would better keep the formatting of the document and does not affect the Document layout so strong.
Reassigned to Falko for decision.
Retitle to make sense.
*** Issue 4851 has been marked as a duplicate of this issue. ***
*** Issue 4427 has been marked as a duplicate of this issue. ***
*** Issue 6469 has been marked as a duplicate of this issue. ***
*** Issue 5379 has been marked as a duplicate of this issue. ***
Added Scott Carr to CC (because of his closed issue #5379.
*** Issue 5654 has been marked as a duplicate of this issue. ***
What's the status on this issue? No pressure, just curious.
*** Issue 5978 has been marked as a duplicate of this issue. ***
If you consider this to be a feasible solution go ahaed :o)
(Evil laugh). The layout should improve using a flexible field which is the no 1 complaint.
Fix checked in. Will work in SRX644l
cmc->mru: For consideration in SRX644l. Superior layout with input fields.
Yes, in 644L the new implemtation works fine. input fields are now used for depicting "flexible" Formfields from Word. Fix will be available with OpenOffice build 644.
*** Issue 9019 has been marked as a duplicate of this issue. ***
The change will take place in OpenOffice 1.1 Beta.
*** Issue 9779 has been marked as a duplicate of this issue. ***
*** Issue 10355 has been marked as a duplicate of this issue. ***