Re: Loading & saving documents

Hi,
 I built something similar a while back (I think), and it works fine. I
didn't use a schema directly, but I suppose I could have. I built a
definition instance which could be "round tripped" if you will. I then
built an xform to manipulate, list, load and save these files. As the
instance is saved it is processed via a servlet with xsl into an XForm.
The initial instance data remains still part of the resulting xform. when
the "builder xform" reloads a built form to edit it, it just loads the
instance part of the form. modifies it and saves it back via the xsl
again. There were some other very simple servlet based interfaces for the
xform builder to use, that provide listings of existing forms and page
urls on which the given forms might be published in the Manifest CMS I
used.

its proved a very serviceable Xforms builder. There were a few 
gotchas but nothing that couldn't be overcome. Mostly they were to do with
incorrect or wrong implementations of the Xforms spec.



Date sent:      	Tue, 4 Oct 2005 14:52:03 +0100
From:           	"Flinton Adam" <Adam.Flinton@cfh.nhs.uk>
To:             	<www-forms@w3.org>
Subject:        	Loading & saving documents
Forwarded by:   	www-forms@w3.org
Date forwarded: 	Tue, 04 Oct 2005 13:51:01 +0000

> 
> Dear All,
> 
> I am looking to create a document editor for XML documents based on a
> single schema using Xforms.
> 
> I have a host of questions but I'll fire them off one by one.
> 
> I would like to create a standalone editor if possible & I'd like to be
> able to have an "open file" & then save/save as functionality.
> 
> i.e. use IE + Novell plugin or possibly mozilla/firefox when it's ready
> (or even OpenOffice possibly) to open an Xforms document & then use it
> to populate it's model by opening another xml file of the requisite
> structure/followng the correct schema & then after editing the XML
> through the Xform UI to do a save/save as.
> 
> Any ideas?
> 
> I can start off hosting the page/form itself within a jsp but the files
> to be opened would always be on the user's local disk & would need to be
> persisted back to that disk.
> 
> TIA
> 
> Adam
> 
> 
> This e-mail is confidential and privileged. If you are not the intended
> recipient please accept our apologies; please do not disclose, copy or
> distribute information in this e-mail or take any action in reliance on
> its contents: to do so is strictly prohibited and may be unlawful.
> Please inform 
us that this message has gone astray before deleting it. Thank you for
your co-operation. > > >

Received on Wednesday, 5 October 2005 02:49:19 UTC