custom widget

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

custom widget

jwatts
What is the process for adding a custom widget?  I want to use
collapsible divs rather than tabs to show or hide groups.

--
This email message and any attachments are for the sole use of the intended recipient(s) and may contain information that is proprietary to Ahold and/or its subsidiaries ("Ahold") or otherwise confidential or legally privileged.  If you have received this message in error, please notify the sender by reply, and delete all copies of this message and any attachments.  If you are the intended recipient you may use the information contained in this message and any files attached to this message only as authorized by Ahold.  Files attached to this message may only be transmitted using secure systems and appropriate means of encryption, and must be secured using the same level of password and security protection with which the file was provided to you.  Any unauthorized use, dissemination or disclosure of this message or its attachments is strictly prohibited.



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: custom widget

Erik Bruchez
Administrator
 > What is the process for adding a custom widget?  I want to use
 > collapsible divs rather than tabs to show or hide groups.

There is no documented process at the time. We would like to have a real
component system in the future, but this is not there yet.

So at this point, things like this involve either:

* Digging into the Orbeon Forms code, in particular the
org.orbeon.oxf.xforms.processor.handlers package on one hand, and
xforms.js on the other hand.

* Implementing this with CSS and JavaScript.

Currently, tabs are implemented in XSLT in the xforms-widgets.xsl
stylesheet. The stylesheet transforms elements such as <widgets:tabs>
into XForms groups and triggers. We don't really like this solution
because it has quite an impact on performance and would like to
implement tabs as an appearance of xforms:group instead, and use the YUI
tabs on the client.

So could you precise a little bit what you mean by "collapsible divs"?
And what kind of markup would you expect to write in the XForms document?

-Erik

--
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.com/


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: custom widget

jwatts
Hello Erik,

Thanks for the response.  I have a (potentially) very long form, and the
user has stated that they want to have everything on a single page with
the capability to hide groups of form fields.  The use of tabs (either
on the top or side) was rejected because it was too cluttered.  What I
mean by collapsible divs is really nothing more than JavaScript toggling
the display value of a div between none and block.  It would end up
looking something like the iGoogle page where you can collapse or expand
a single news entry to look a the details. After having looked into it a
little more I can either simply put the JavaScript and divs into my
xforms document or "add" a widget to the xsl file that will create the
html, switch, triggers, and labels for me.

-Joe

Erik Bruchez wrote:

> > What is the process for adding a custom widget?  I want to use
> > collapsible divs rather than tabs to show or hide groups.
>
> There is no documented process at the time. We would like to have a
> real component system in the future, but this is not there yet.
>
> So at this point, things like this involve either:
>
> * Digging into the Orbeon Forms code, in particular the
> org.orbeon.oxf.xforms.processor.handlers package on one hand, and
> xforms.js on the other hand.
>
> * Implementing this with CSS and JavaScript.
>
> Currently, tabs are implemented in XSLT in the xforms-widgets.xsl
> stylesheet. The stylesheet transforms elements such as <widgets:tabs>
> into XForms groups and triggers. We don't really like this solution
> because it has quite an impact on performance and would like to
> implement tabs as an appearance of xforms:group instead, and use the
> YUI tabs on the client.
>
> So could y
>
> -Erik
>
> ------------------------------------------------------------------------
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> OW2 mailing lists service home page: http://www.ow2.org/wws
>  


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: custom widget

Hank Ratzesberger

Hi Jo,

It may be true that the examples use mostly tabbed views and the 
widget: control, but have you made any attempts with "plain vanilla"
<xforms:case> and <xforms:switch> ?  

You can make <xforms:case> elements visible or not and use this,
for example, to make a section with only a caption appear to expand to 
show form elements.  Accomplishing this with the declarative XForms
I find a bit of a challenge, but the framework is there.

Regards,
Hank Ratzesberger
UCSB

On Oct 11, 2007, at 7:24 AM, jwatts wrote:

Hello Erik,

Thanks for the response.  I have a (potentially) very long form, and the user has stated that they want to have everything on a single page with the capability to hide groups of form fields.  The use of tabs (either on the top or side) was rejected because it was too cluttered.  What I mean by collapsible divs is really nothing more than JavaScript toggling the display value of a div between none and block.  It would end up looking something like the iGoogle page where you can collapse or expand a single news entry to look a the details. After having looked into it a little more I can either simply put the JavaScript and divs into my xforms document or "add" a widget to the xsl file that will create the html, switch, triggers, and labels for me.

-Joe

Erik Bruchez wrote:
> What is the process for adding a custom widget?  I want to use
> collapsible divs rather than tabs to show or hide groups.

There is no documented process at the time. We would like to have a real component system in the future, but this is not there yet.

So at this point, things like this involve either:

* Digging into the Orbeon Forms code, in particular the org.orbeon.oxf.xforms.processor.handlers package on one hand, and xforms.js on the other hand.

* Implementing this with CSS and JavaScript.

Currently, tabs are implemented in XSLT in the xforms-widgets.xsl stylesheet. The stylesheet transforms elements such as <widgets:tabs> into XForms groups and triggers. We don't really like this solution because it has quite an impact on performance and would like to implement tabs as an appearance of xforms:group instead, and use the YUI tabs on the client.

So could y

-Erik

------------------------------------------------------------------------


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: [hidden email]
For general help: [hidden email]
OW2 mailing lists service home page: http://www.ow2.org/wws

  


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: [hidden email]
For general help: [hidden email]
OW2 mailing lists service home page: http://www.ow2.org/wws

Hank Ratzesberger
NEES@UCSB
Institute for Crustal Studies,
University of California, Santa Barbara
805-893-8042







--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: custom widget

Erik Bruchez
Administrator
In reply to this post by jwatts
Joe,

The good news is that you don't need a new widget or any JavaScript for
this. XForms already supports this in multiple ways:

* xforms:switch/xforms:case

* xforms:group bound to node of which you control relevance with
   xforms:bind

* xforms:group with UI "switching", e.g.:

     <xforms:group ref=".[insert condition here]">

-Erik

jwatts wrote:

> Hello Erik,
>
> Thanks for the response.  I have a (potentially) very long form, and the
> user has stated that they want to have everything on a single page with
> the capability to hide groups of form fields.  The use of tabs (either
> on the top or side) was rejected because it was too cluttered.  What I
> mean by collapsible divs is really nothing more than JavaScript toggling
> the display value of a div between none and block.  It would end up
> looking something like the iGoogle page where you can collapse or expand
> a single news entry to look a the details. After having looked into it a
> little more I can either simply put the JavaScript and divs into my
> xforms document or "add" a widget to the xsl file that will create the
> html, switch, triggers, and labels for me.
>
> -Joe
>
> Erik Bruchez wrote:
>> > What is the process for adding a custom widget?  I want to use
>> > collapsible divs rather than tabs to show or hide groups.
>>
>> There is no documented process at the time. We would like to have a
>> real component system in the future, but this is not there yet.
>>
>> So at this point, things like this involve either:
>>
>> * Digging into the Orbeon Forms code, in particular the
>> org.orbeon.oxf.xforms.processor.handlers package on one hand, and
>> xforms.js on the other hand.
>>
>> * Implementing this with CSS and JavaScript.
>>
>> Currently, tabs are implemented in XSLT in the xforms-widgets.xsl
>> stylesheet. The stylesheet transforms elements such as <widgets:tabs>
>> into XForms groups and triggers. We don't really like this solution
>> because it has quite an impact on performance and would like to
>> implement tabs as an appearance of xforms:group instead, and use the
>> YUI tabs on the client.
>>
>> So could y
>>
>> -Erik
>>
>> ------------------------------------------------------------------------
>>
>>
>> --
>> You receive this message as a subscriber of the [hidden email]
>> mailing list.
>> To unsubscribe: mailto:[hidden email]
>> For general help: mailto:[hidden email]?subject=help
>> OW2 mailing lists service home page: http://www.ow2.org/wws
>>  

--
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.com/


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws