Hi Svante
The two basic scenarios - creating/editing and using OO files with
XForms - unfold into several less abstract use cases for both cases. I
see its strength in creating Custom XML functionalities OOo is currently
lacking, besides the development of application profiles from the ODF specs.
Because of the use of XML instances and XML Schema, OOo forms can be
used to create several solutions in the corporate sector using a
middleware or web service to exchange data.
Most users have their main knowledge in office applications. In recent
years, more and more browser-based applications have evolved to equip
companies with software in addition to already used enterprise
solutions. In the process of EAI, it might be useful to streamline those
applications "back" into a office suite. Also, a lot of work is still
done in classic office applications where the important information is
isolated into a single file. That's the point where the Xforms
implementation can reveal its true capabilities and gives the
opportunity to simplify and rationalise information flow processes.
Well, enough for the prelude, following some simple examples:
- Alternative to PDF Forms - PDF Forms have two major advantages:
structured data entry and visual fidelity as they can be printed and
look like a paper-based form. However, PDF forms can't be saved. OOo
could draw a real benefit by supplying users with an alternative which
has the same features, plus documents can be saved and - if permission
is given - edited. You can think of a OOo browser plugin and usage in
Writer.
- Employee file - Employees can have a form where their current status
(room number, telephone, etc) is saved and can be updated by the
respective employee. Think of service times, anouncements when
out-of-office, changed telephone number, etc. XForms documents might be
stored locally and every change of it could trigger an immediate update
on the web site through the XForms submission function.
- Groupware solutions are also useful and also any other corporate tasks
where the handling of structured data is present but not done within an
ERP or any other specialised software.
Opportunities for XForms in OOo are multifold but unfortunately not
tackled to the extent of which is possible.
Cheers
Robert
Svante Schubert wrote:
Changed the topic and some comments..
Marcin Miłkowski wrote:
Alexandro Colorado pisze:
I think that XForms really need a community makeover. This feature is
highly ignored in the OOo component space.
First we would need more templates to show the power of Xforms. Also
some more documentation on the wiki and even codesnippets (OOoBasic
snippets?, Java).
Yes, same templates to be shown, even better larger scenarios would be
helpful, that's why I asked Jonathon about details of his interests in
XForms.
Well, if you're composing anything than a trivial data entry form,
XForms implementation in OOo is seriously crippled due to the lack of
xforms:repeat as you cannot really edit any XML document that contains
recursive structures. Otherwise, you could, for example, implement an
xforms-based editor of ODF files - a kind of WordPerfect Reveal Codes
on steroids ;)
;-)
We have two basic scenarios:
1) Form editing (lacking of usability)
2) Form usage
We might start even earlier in asking ourselves, why do we need forms
(and as implementation detail XForms).
What I am asking you (with an answer in my mind), what is the great
benefit of XForms, why should we go further with it with OOo?
So it's not only about awareness - many xforms examples from a nice
wikibook on xforms simply won't work in OOo as nicely as they do in
Firefox. We need better compliance as well.
Regards,
Marcin
This will hopefully increase the awareness of the tool and then we
could have some real techncial features request.
On Wed, 09 Jul 2008 08:00:32 -0500, Svante Schubert
<[EMAIL PROTECTED]> wrote:
Jonathon Coombes wrote:
On 08/07/2008, at 6:40 PM, Svante Schubert wrote:
...
Hi Svante,
I am glad to see that more development is happening with the
associated XML technologies here. I understand that much more
capabilities will be possible with the newer specifications and
better processor in Saxon. My main question is will these new
capabilities be implemented in the XForm part of OpenOffice.org? My
main interest is having not just the xform backend, but other
features such as the xforms:repeat capabilities and other more
advanced operations. Is this something that will be coming with the
new Saxon processor?
Hi Jonathon,
I am a big fan of XForms, but AFAIK for OOo 3.0 there will be no
update on the OOo XForms implementation.
Only the XSLT filter will profit from the new specifications.
But may I ask what you plan to use XForms for, what features you
desire in detail?
Aside of being curious, I would like to have some feedback and as
well some evidence/proof that it is worth to move resources from
other areas of OOo development to XForms.
Kind regards,
Svante
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
