incubator-odf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kejia Ye (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ODFTOOLKIT-340) Propose to add new API to insert form controls into document
Date Thu, 15 Nov 2012 10:08:12 GMT

     [ https://issues.apache.org/jira/browse/ODFTOOLKIT-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kejia Ye updated ODFTOOLKIT-340:
--------------------------------

    Attachment: createFormIntextDocument_v2.patch

Call for review.  update a new version to fix some issue.
                
> Propose to add new API to insert form controls into document
> ------------------------------------------------------------
>
>                 Key: ODFTOOLKIT-340
>                 URL: https://issues.apache.org/jira/browse/ODFTOOLKIT-340
>             Project: ODF Toolkit
>          Issue Type: New Feature
>          Components: simple api
>    Affects Versions: 0.7
>            Reporter: Kejia Ye
>             Fix For: 0.8
>
>         Attachments: createFormInTextDocument.patch, createFormIntextDocument_v2.patch
>
>
> Here's a customer requirement that new APIs are needed to insert standard from controls
into document, like Radio buttons, Checkboxes and InputFields. Additionally, it is required
to assign appropriate labels and values to the inserted controls.
> To support this feature, a problem came up first.  A form control is implementation-dependent
and it may have self-defined attributes that cannot be ignored and auto-generated by editors.
Besides, not all the forms defined in the ODF specs are fully supported by common ODF editors.For
example, AOO use <form:formatted-text> to implement date field and time field.
> I think one way to resolve this can be separating the implementation-dependent details
from other contents. Define a provider class which implements Form interface and provide methods
to create controls, like provider.createTextArea(initValues). For now we can only use OOFormProvider
as the default one and use its implementation methods to initiate the controls, but user can
also define customized providers by themselves.
> Besides, how to define the style of a shape and set anchor type of a control to char
may be also complex. I'll try to figure them out as I dig into the details.
> Any one have comments or ideas with this proposal? Thanks!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message