Announcing Oryx XForms Editor

I wanted to announce the Oryx XForms Editor – a web-based tool for  
creating XForms. You can visually edit forms, export and import them  
in XForms format. The editor runs in your web browser (Firefox), zero  
software installation required.

The editor is still in an early stage and is currently available for  
testing and feedback. For more information and demo visit:

http://www.xforms-editor.org/Oryx/XForms

Oryx is an open platform for web-based modeling developed by the  
Business Process Technology research group at the Hasso Plattner  
Institute of IT Systems Engineering at the University of Potsdam.  
Besides XForms, Oryx supports various modeling languages, like BPMN,  
EPC and Petri nets.

Everyone is invited to contribute new features and knowledge to Oryx.  
The project is hosted as a Google Code project ( http://code.google.com/p/oryx-editor/ 
  ) under MIT license.

Regards,
Felix

--
Jan-Felix Schwarz
jan-felix.schwarz <at> student.hpi.uni-potsdam.de

orbeon X-forms

Hi 

        This is Ramesh.I am implementing orbeon x-forms in my application. I
am displaying all nodes on one page getting these from eXist xml data base 
       I am trying to edit particular record and displaying into another
x-form 
I am new to  x-forms. i am not understanding how to edit record

if any  one know about it can you please give me suggestion

Thanks & Regards
Ramesh K

         
--

-- 
View this message in context: http://www.nabble.com/orbeon-X-forms-tp20475802p20475802.html
Sent from the w3.org - www-forms mailing list archive at Nabble.com.

Re: orbeon X-forms

Ramesh,

I recommend you try the Orbeon Forms users list, ops-users. It is easy  
to subscribe with the instructions here:

   http://www.orbeon.com/ops/doc/home-faq#mailing-list

Alternatively, you can use the Nabble web interface:

   http://www.nabble.com/ObjectWeb-OPS---Users-f2537.html

See also how best to report an issue or ask a question in order to  
maximize your chances of getting an answer:

   http://www.orbeon.com/ops/doc/home-faq#reporting-issues

If you ask your question in the mailing-list, you will also get more  
eyes potentially looking at the issue.

-Erik

On Nov 18, 2008, at 5:41 AM, rameshkancherla wrote:

>
> Hi
>
>        This is Ramesh.I am implementing orbeon x-forms in my  
> application. I
> am displaying all nodes on one page getting these from eXist xml  

Simple Toolkit Abstraction project idea

Hello,

I am the author of the colour management system Oyranos.
In this system I want to expose plug-in settings to users whithout knowing 
about the actual toolkit a application is runing inside.
Currently I think the system can build upon a small subset of XFORMS 
elements and extent in other parts.
The idea to (re-)use XFORMS syntax was born in a discussion with Jon Cruz 
from Inkscape, which does a lot with W3C XML.

The goal is to create a convention, which abstracts content logic from UI 
representation and from the data model:
http://www.oyranos.org/wiki/index.php?title=XML_Plug-in_options

This project is still in the design phase. It was as well suggested for a 
Google summer of code project, but several sides mentioned it to bee too 
complicated for a 3 months student work:
http://www.freedesktop.org/wiki/OpenIccForGoogleSoC2008#head-07e05f69f1b4e331ba0d3741dc06ba53ae728459

Here a question:
XFORMS documents can be displayed through FF with the xforms plug-in 
installed.
Are there other smaller footprint projects known to display XFORMS on a 
local host?

Any ideas and suggestions are welcome 

kind regards
Kai-Uwe Behrmann

Spec examples probably incorrect

Hi,

I mentioned this to Leigh and Keith, but I figured I'd bring this up to 
the whole group, too.

One of our users said that the spec has an example of event() being used 
with xf:output in a  <at> ref and he was right -> 
http://www.w3.org/TR/xforms11/#submit-evt-submit-error which I believe 
is incorrect.  I also think that the xf:message with event() being used 
in a  <at> ref example under http://www.w3.org/TR/xforms11/#structure-model 
is incorrect, too.

Leigh mentioned that perhaps allowing  <at> value on a xf:message might not 
be a bad idea, especially for reporting errors and I think he is right. 
  It would be pretty useful.  Embedding a xf:output inside the 
xf:message isn't exactly difficult, but it might not be quickly thought 
of by an author.  If we don't go with  <at> value on a xf:message, how about 
putting an example of embedding a xf:output inside a xf:message inside 
the message section of the spec?

--Aaron

Re: Spec examples probably incorrect

RE: Problems with xf:copy and xf:delete...

Aaron,

The reason I believe that there is a problem is that in section 9.3.7
The copy Element, the spec says:

The element node associated with the item, selected by the binding
attributes on copy, is deep copied as a child of the target node as if
an insert action had occurred.

It is possible to argue that because the observed behaviour is not
explicitly ruled-out in the definition of xf:copy I don't believe either
that it is possible to argue that the observed behaviour is acceptable.

I guess this would never have been an issue if the atom:category element
was the child of a atom:categories element.

Due to the lack of detail in the spec I'm gowing to throw this over to
the www-forms <at> w3.org list to see if anyone else has an opinion either
way on the subject.

Regards

Philip Fennell
>XML Developer (The Forge)
>
>BBC Future Media & Technology
>Media Village, 201 Wood Lane London W12 7TP 
>BC4 C4, Broadcast Centre
>
>T:	0208 0085318
>

-----Original Message-----
From: dev-tech-xforms-bounces+philip.fennell=bbc.co.uk <at> lists.mozilla.org
[mailto:dev-tech-xforms-bounces+philip.fennell=bbc.co.uk <at> lists.mozilla.o
rg] On Behalf Of Aaron Reed
Sent: 19 November 2008 19:11
To: dev-tech-xforms <at> lists.mozilla.org
Subject: Re: Problems with xf:copy and xf:delete...

Hi Philip,

I believe that xf:copy is working correctly.  Think of it like a normal
xf:select with items.  When you bind a xf:select to a node and then
change the selected item, the value associated with that item replaces
the contents of the node that xf:select is bound to, right?  In this
case, since it is a xf:select and not a xf:select1, you should be able
to select multiple items and they should all be able to exist under the
bound node together.  If that isn't happening then THAT would be a bug.

--Aaron

Philip Fennell wrote:
> As a follow-up, I've noticed that the bind expression for 'entry.tags'
> might be causing the delete problems I was having. That expression 
> points to an attribute node.
> 
> I've re-jigged the form so that the [+] buttons are on one repeat for 
> the 'available' categories and the [-] buttons are on another repeat 
> for the 'selected' categories. Not exactly elegant but it'll do for
now.
> 
> 
> Regards
> 
> Philip Fennell
>> XML Developer (The Forge)
>>
>> BBC Future Media & Technology
>> Media Village, 201 Wood Lane London W12 7TP
>> BC4 C4, Broadcast Centre
>>
>> T:	0208 0085318
>>
> 
> -----Original Message-----
> From: 
> dev-tech-xforms-bounces+philip.fennell=bbc.co.uk <at> lists.mozilla.org
> [mailto:dev-tech-xforms-bounces+philip.fennell=bbc.co.uk <at> lists.mozilla
> .o
> rg] On Behalf Of Philip Fennell
> Sent: 19 November 2008 13:35
> To: dev-tech-xforms <at> lists.mozilla.org
> Subject: Problems with xf:copy and xf:delete...
> 
> Hello,
> 
> I have been working on an XForms enable Atom Publishing Protocol (APP)

> client application for the publication of new Atom entries and I've 
> run into a few problems with the XForms plug-in.
> 
> I'm using:
> 
> Firefox 3.0.4 and Mozilla XForms 0.8.6ff3 on Windows XP SP2
> 
> 
> And here are the problems:
> 
> 1) I use xf:itemset and xf:copy, bound to the categories of the feed 
> (see example below) to control the 'tags' the user can select for 
> their entry via an xf:select. The xf:select is bound to the entry 
> element of the entry instance data. When I select a tag from the list 
> the correct category element is created but the side-effect is that 
> all the other children of the entry (title, link, id, update and 
> content) are deleted and the controls bound to them disappear from the

> view (not surprisingly). If you open the example XForm below you will 
> be able to see the behaviour I've described. There is nothing that I 
> can see in the XForms 1.1 spec that suggests this is the correct 
> behaviour. Note, I tried the same form in FormsPlayer and it didn't 
> delete the other children.
> 
> 2) In order to get around this immediate problem I recreated, rather 
> crudely, the same functionality (see example) by using xf:repeat, some

> xf:trigger elements and some xf:insert and xf:delete actions. This 
> appears to work fine. But, if you comment-out the xf:select, refresh 
> the browser, add a tag with the [+] button then delete it with the 
> corresponding [-] Firefox crashes big-time!
> 
> 
> If anyone else can recreate these then please let me know and I'll 
> raise some bugs in Bugzilla.
> 
> 
> 
> 
> Example XForm:
> ==============
> 
> <?xml version="1.0" encoding="utf-8"?>
> <!-- <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
>     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> --> <html 
> xmlns="http://www.w3.org/1999/xhtml"
>     xmlns:app="http://www.w3.org/2007/app"
>     xmlns:atom="http://www.w3.org/2005/Atom"
>     xmlns:ev="http://www.w3.org/2001/xml-events"
>     xmlns:xf="http://www.w3.org/2002/xforms"
>     xmlns:xs="ttp://www.w3.org/2001/XMLSchema"
>     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>     xml:lang="en"
>     lang="en">
>   <head>
>     <meta name="generator" content="jEdit" />
>     <meta name="author" content="Philip A. R. Fennell" />
>     <meta name="CVS-Id" content="$Id: $" />
>     <!-- <link rel="stylesheet" type="text/css" href="" media="screen"
> /> -->
>     <!-- <script type="text/javascript" src=""></script> -->
>     
>     <xf:model>
>        <!--
>        <xf:action ev:event="xforms-ready">
>         <xf:send submission="getService"/>
>       </xf:action>
>        -->
>       
>       <!-- APP Service Document. -->
>       <xf:submission id="getService"
>           action="/app/service"
>           method="get"
>           replace="instance"
>           instance="service">
>         <xf:header>
>           <xf:name>Accept</xf:name>
>           <xf:value>application/atomsvc+xml</xf:value>
>         </xf:header>
>         <xf:action ev:event="xforms-submit-done">
>           <xf:send submission="getCategories"/>
>         </xf:action>
>       </xf:submission>
>       
>       <xf:instance id="service" xmlns="http://www.w3.org/2007/app">
>         <service xmlns="http://www.w3.org/2007/app" 
>           xmlns:atom="http://www.w3.org/2005/Atom">
>           <workspace>
>             <atom:title>Trees</atom:title>
>             <collection href="/app/entries">
>               <atom:title>Pictures</atom:title>
>               <categories href="/app/tags"/>
>               <accept>application/atom+xml</accept>
>             </collection>
>           </workspace>
>         </service>
>       </xf:instance>
>       
>       <xf:bind id="siteTitle"
> nodeset="instance('service')/app:workspace/atom:title"/>
>       <xf:bind id="siteSubtitle"
>
nodeset="instance('service')/app:workspace/app:collection/atom:title"/>
>       <xf:bind id="acceptsMediaTypes"
> nodeset="instance('service')/app:workspace/app:collection/app:accept"/
> >
>       
>       
>       
>       
>       <!-- Atom Syndication Feed. -->
>       <!-- <xf:submission id="getFeed"
>           resource="../content/feed.atom"
>           method="get"
>           replace="instance"
>           instance="service"/>
>       <xf:instance id="feed" xmlns="http://www.w3.org/2005/Atom"/> -->
>       
>       
>       
>       
>       <!-- Atom Feed Entry. -->
>       <xf:submission id="createResource"
>           method="post"
>           replace="all"
>           instance="entry"
>           ref="instance('entry')">
>         <xf:resource
> value="instance('service')/app:workspace/app:collection/ <at> href"/>
>         <xf:header>
>           <xf:name>Slug</xf:name>
>           <xf:value value="instance('entry')/atom:title"/>
>         </xf:header>
>       </xf:submission>
>       <xf:instance id="entry">
>         <entry xmlns="http://www.w3.org/2005/Atom">
>           <title/>
>           <link href=""/>
>           <id/>
>           <updated/>
>           <content type="text"/>
>         </entry>
>       </xf:instance>
>       
>       <xf:bind id="entry.title"
nodeset="instance('entry')/atom:title"/>
>       <xf:bind id="entry.content"
> nodeset="instance('entry')/atom:content"/>
>       <xf:bind id="entry.categories" nodeset="instance('entry')"/>
>       <xf:bind id="entry.tags"
> nodeset="instance('entry')/atom:category/ <at> term"/>
>       
>       
>       
>       <!-- APP Categories Document. -->
>       <xf:submission id="getCategories"
>           method="get"
>           replace="instance"
>           instance="categories">
>         <xf:header>
>           <xf:name>Accept</xf:name>
>           <xf:value>application/atomcat+xml</xf:value>
>         </xf:header>
>         <xf:resource
> value="instance('service')/app:workspace/app:collection/app:categories
> / <at> 
> href"/>
>       </xf:submission>
>       
>       <xf:instance id="categories" xmlns="http://www.w3.org/2007/app">
>         <app:categories
>           xmlns:app="http://www.w3.org/2007/app"
>           xmlns:atom="http://www.w3.org/2005/Atom"
>           fixed="yes"
>           scheme="http://trees.co.uk/tags">
>           <atom:category term="ash" />
>           <atom:category term="beech" />
>           <atom:category term="birch" />
>           <atom:category term="chestnut" />
>           <atom:category term="hazel" />
>           <atom:category term="oak" />
>         </app:categories>
>       </xf:instance>
>       
>       <xf:bind id="tags"
> nodeset="instance('categories')/atom:category"/>
>     </xf:model>
>     
>     <title>Atom Publishing Protocol Client</title>
>   </head>
>   <body>
>     <h1>XForms Enabled <acronym title="Atom Publishing 
> Protocol">APP</acronym> Client</h1>
>     <div>
>       <h2><xf:output bind="siteTitle"/> &gt; Upload &gt; <xf:output 
> bind="siteSubtitle"/></h2>
>       <xf:group>
>         
>         <xf:group>
>           <xf:input bind="entry.title">
>             <xf:label>Title</xf:label>
>           </xf:input>
>           
>           <xf:group>
>             <xf:textarea bind="entry.content">
>               <xf:label>Content</xf:label>
>             </xf:textarea>
>           </xf:group>
>         </xf:group>
>         
>         <xf:group>
>           <xf:label>Tags</xf:label>
>           <xf:repeat bind="entry.tags">
>             <xf:output ref="."/>
>           </xf:repeat>
>         </xf:group>
>         
>         <xf:group>
>           <xf:select bind="entry.categories" appearance="full">
>             <xf:label>Select</xf:label>
>             <xf:itemset bind="tags">
>               <xf:label ref=" <at> term"/>
>               <xf:copy ref="."/>
>             </xf:itemset>
>           </xf:select>
>         </xf:group>
>         
>         <xf:group>
>           <ul>
>             <xf:repeat id="selector.tags" bind="tags">
>               <li>
>                 <xf:trigger>
>                   <xf:label>+</xf:label>
>                   <xf:action ev:event="DOMActivate">
>                     <xf:insert context="instance('entry')"
> nodeset="atom:category"
>
origin="instance('categories')/atom:category[index('selector.tags')]"/>
>                   </xf:action>
>                 </xf:trigger>
>                 <xf:trigger>
>                   <xf:label>-</xf:label>
>                   <xf:action ev:event="DOMActivate">
>                     <xf:delete context="instance('entry')"
> nodeset="atom:category" at="index('selector.tags')"/>
>                   </xf:action>
>                 </xf:trigger>
>                 <xf:output ref=" <at> term"/>
>               </li>
>             </xf:repeat>
>           </ul>
>         </xf:group>
>         
>         <!--<xf:group>
>           <xf:submit submission="createResource">
>             <xf:label>Publish</xf:label>
>             <xf:hint>Publish you new entry</xf:hint>
>           </xf:submit>
>         </xf:group>-->
>       </xf:group>
>       
>     </div>
>   </body>
> </html>
> 
> 
> 
> 
> 
> Regards
> 
> Philip Fennell
>> XML Developer (The Forge)
>>
>> BBC Future Media & Technology
>> Media Village, 201 Wood Lane London W12 7TP
>> BC4 C4, Broadcast Centre
>>
>> T:	0208 0085318
>>
> 
> http://www.bbc.co.uk/
> This e-mail (and any attachments) is confidential and may contain 
> personal views which are not the views of the BBC unless specifically 
> stated.
> If you have received it in error, please delete it from your system.
> Do not use, copy or disclose the information in any way nor act in 
> reliance on it and notify the sender immediately.
> Please note that the BBC monitors e-mails sent or received.
> Further communication will signify your consent to this.
> 					
> _______________________________________________
> dev-tech-xforms mailing list
> dev-tech-xforms <at> lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-tech-xforms
> 
> http://www.bbc.co.uk/
> This e-mail (and any attachments) is confidential and may contain
personal views which are not the views of the BBC unless specifically
stated.
> If you have received it in error, please delete it from your system.
> Do not use, copy or disclose the information in any way nor act in
reliance on it and notify the sender immediately.
> Please note that the BBC monitors e-mails sent or received.
> Further communication will signify your consent to this.
> 					
_______________________________________________
dev-tech-xforms mailing list
dev-tech-xforms <at> lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-xforms

http://www.bbc.co.uk/
This e-mail (and any attachments) is confidential and may contain personal views which are not the views of
the BBC unless specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.
					

Follow-up: XForms 1.1 implementation report for the Firefox XForms extension

A new submit method for implementing replace="all" with Javascript ?

Hello,

Reading XForms 1.0 Recommendation and XForms 1.1 Candidate 
Recommendation, I think it might be useful to add another way of 
serialization as application/x-www-form-urlencoded with just one input 
field containing the serialized XML.

The problem I'm encountering is about implementing ' replace="all" ' in 
Javascript. I am re-engineering AJAXForms 
(http://www.agencexml.com/xsltforms) and, after replacing Java parts 
with an XSL transformation so it can be client-side, I have to modify 
Javascripts submit parts. AJAXForms, which was not designed for XHTML, 
is using XMLHttpRequest and "document.write()".

First, I replaced "document.write(req.responseText)" with

"document.documentElement.parentNode.replaceChild(req.responseXML.documentElement,document.documentElement)" 
for XHTML response and "document.documentElement.innerHTML = 
req.responseText" for non XHTML response (I should actually process all 
childNodes of document.documentElement.parentNode...) . But, even so, it 
doesn't work perfectly for FF3 (title not updated !) and Opera (display 
not fully cleared !), and the previous URI is, of course, still the 
current one : reload and backward buttons do not act as if it were a new 
page...

I would prefer browsers to completely replace the page the way they 
usually do for HTML form submit or for HTML anchor : XSL transformation 
if mentioned, CSS import, Javascript execution,... It would prevent 
memory leak and every kind of problems resulting from a unique page been 
modified, and modified, and modified...

So, instead of XMLHttpRequest, HTML form submit would do the trick but, 
at least, one input field is required. Just one input field, named 
"postdata" for example, would be good to contain the serialized XML. 
This new submit method could be named "xml-urlencoded-post".

I would appreciate to have your points of view.

Thank you in advance.

Alain COUTHURES
<agenceXML>
http://www.agencexml.com
Bordeaux, France

validating an xform

Hi,

I'm new to the list. I'd like to ask your help to clarify some things
because I don't know what is the best practice for my issues. The
problem is the following: I have an xform where input widgets can have
some constraints (e.g. a field can only accept integers from an
interval, or some fields are required, etc.). How to check if the form
satisfies these constraints?
(1) Should it be done on the client side with JavaScript? or
(2) Should it be checked on the server side with a servlet for instance?

I'm using the Mozilla XForms add-on, and I made a test with the 2nd
case. The servlet can tell if the form is correct or not, but if it's
not correct, the user should be able to correct it. However, if I
click on "back", the xform is re-initialized, i.e. it's empty again :(
I'm just thinking: if the form is incorrect, should the servlet show
it again and simply replace the empty XML model part with the one that
was sent by the user? In addition, it should print some info for the
user. Thus, the user can advance incrementally. Is there an easy way
for this?

If case (1) is the preferred way, could someone please send me an
example? I'm not a JavaScript magician.

Thanks,

Laszlo