xforms:select1
Locked
 
|
Erik,
I am trying without success to display a selection list (full/compact/minimal) under OPS. Wonder what I am doing wrong! I would like to render a list as a TREE (e.g., Windows explorer). The examples of select1 do not render a Tree view as far as I know. The following, when viewed under XFORMS Player in IE shows a TREE listing. (FORMS PLAYER in IE) <xforms:select1 ref="greeting" appearance="compact"> <xforms:label>Choose a Greeting</xforms:label> <xforms:choices> <xforms:label>Veggie choices</xforms:label> <xforms:item> <xforms:label>Fried</xforms:label> <xforms:value>Potato</xforms:value> </xforms:item> <xforms:item> <xforms:label>Greens</xforms:label> <xforms:value>Beans</xforms:value> </xforms:item> </xfroms:choices> <xforms:item> <xforms:label>Hello</xforms:label> <xforms:value>Hello</xforms:value> </xforms:item> </xforms:select1> ------------------------------------------------------ Thanks, Chary -- 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 ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
|
Administrator
|
Chary,
The XForms specification does not specify how, or even whether, a select1 can be rendered as a tree. OPS for the moment does not support that kind of rendering. It supports radio buttons, dropdown menus, and lists. This explains why your tree is not working. It would be nice to have this feature in OPS as well, of course. Any taker to implement it? -Erik chary wrote: > Erik, > > I am trying without success to display a selection list > (full/compact/minimal) under OPS. Wonder what I am doing wrong! > I would like to render a list as a TREE (e.g., Windows explorer). The > examples of select1 do not render a Tree view as far as I know. > > The following, when viewed under XFORMS Player in IE shows a TREE listing. > > (FORMS PLAYER in IE) > <xforms:select1 ref="greeting" appearance="compact"> > <xforms:label>Choose a Greeting</xforms:label> > <xforms:choices> > <xforms:label>Veggie choices</xforms:label> > <xforms:item> > <xforms:label>Fried</xforms:label> > <xforms:value>Potato</xforms:value> > </xforms:item> > <xforms:item> > <xforms:label>Greens</xforms:label> > <xforms:value>Beans</xforms:value> > > </xforms:item> > </xfroms:choices> > <xforms:item> > <xforms:label>Hello</xforms:label> > <xforms:value>Hello</xforms:value> > > </xforms:item> > > </xforms:select1> > ------------------------------------------------------ > Thanks, > Chary -- 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 ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
|
|
Erik, I think, from application development view point, it is important to have a rich UI component set. I understand why "select1" is not rendered as a Tree view as the XForms spec does not say so (but XForms Processor does - and it is in my view, an important user interface). Perhaps XForms UI may not be your main focus, but, is there an attempt at making the XForms rendering as rich as possible? Are there any plugin 3rd party components in OPS? If not, is there a defined and documented process on how to create these components/extensions in OPS so that others interested in it can develop? Regards, Chary Erik Bruchez wrote: > Chary, > > The XForms specification does not specify how, or even whether, a > select1 can be rendered as a tree. OPS for the moment does not support > that kind of rendering. It supports radio buttons, dropdown menus, and > lists. This explains why your tree is not working. It would be nice to > have this feature in OPS as well, of course. Any taker to implement it? > > -Erik > > chary wrote: > >> Erik, >> >> I am trying without success to display a selection list >> (full/compact/minimal) under OPS. Wonder what I am doing wrong! >> I would like to render a list as a TREE (e.g., Windows explorer). >> The examples of select1 do not render a Tree view as far as I know. >> >> The following, when viewed under XFORMS Player in IE shows a TREE >> listing. >> >> (FORMS PLAYER in IE) >> <xforms:select1 ref="greeting" appearance="compact"> >> <xforms:label>Choose a Greeting</xforms:label> >> <xforms:choices> >> <xforms:label>Veggie choices</xforms:label> >> <xforms:item> >> <xforms:label>Fried</xforms:label> >> <xforms:value>Potato</xforms:value> >> </xforms:item> >> <xforms:item> >> <xforms:label>Greens</xforms:label> >> <xforms:value>Beans</xforms:value> >> >> </xforms:item> >> </xfroms:choices> >> <xforms:item> >> <xforms:label>Hello</xforms:label> >> <xforms:value>Hello</xforms:value> >> >> </xforms:item> >> >> </xforms:select1> >> ------------------------------------------------------ >> Thanks, >> Chary > > >------------------------------------------------------------------------ > > >-- >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 >ObjectWeb mailing lists service home page: http://www.objectweb.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 ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
|
Administrator
|
Chary,
Absolutely. We agree, and we do plan to enhance the OPS XForms engine with better and richer components and yes, an extension API would be great. But because we have limited resources, the main focus remains over the next month to get an rock-solid and XForms-compliant implementation out of the door. Remember that OPS is an open source project. We encourage developers out there to participate by downloading the source code and contributing to it. We are happy to answer questions and accept patches, and in general to integrate contributors in the development of OPS. Additionally, it is always possible to sponsor features. We typically implement them for a fixed price. -Erik chary wrote: > > Erik, > > I think, from application development view point, it is important to > have a rich UI component set. I understand why "select1" is not rendered > as a Tree view as the XForms spec does not say so (but XForms Processor > does - and it is in my view, an important user interface). > > Perhaps XForms UI may not be your main focus, but, is there an attempt > at making the XForms rendering as rich as possible? Are there any plugin > 3rd party components in OPS? If not, is there a defined and documented > process on how to create these components/extensions in OPS so that > others interested in it can develop? > Regards, > Chary > > > Erik Bruchez wrote: > >> Chary, >> >> The XForms specification does not specify how, or even whether, a >> select1 can be rendered as a tree. OPS for the moment does not support >> that kind of rendering. It supports radio buttons, dropdown menus, and >> lists. This explains why your tree is not working. It would be nice to >> have this feature in OPS as well, of course. Any taker to implement it? >> >> -Erik >> >> chary wrote: >> >>> Erik, >>> >>> I am trying without success to display a selection list >>> (full/compact/minimal) under OPS. Wonder what I am doing wrong! >>> I would like to render a list as a TREE (e.g., Windows explorer). >>> The examples of select1 do not render a Tree view as far as I know. >>> >>> The following, when viewed under XFORMS Player in IE shows a TREE >>> listing. >>> >>> (FORMS PLAYER in IE) >>> <xforms:select1 ref="greeting" appearance="compact"> >>> <xforms:label>Choose a Greeting</xforms:label> >>> <xforms:choices> >>> <xforms:label>Veggie choices</xforms:label> >>> <xforms:item> >>> <xforms:label>Fried</xforms:label> >>> <xforms:value>Potato</xforms:value> >>> </xforms:item> >>> <xforms:item> >>> <xforms:label>Greens</xforms:label> >>> <xforms:value>Beans</xforms:value> >>> >>> </xforms:item> >>> </xfroms:choices> >>> <xforms:item> >>> <xforms:label>Hello</xforms:label> >>> <xforms:value>Hello</xforms:value> >>> >>> </xforms:item> >>> >>> </xforms:select1> >>> ------------------------------------------------------ >>> Thanks, >>> Chary >> >> >> >> ------------------------------------------------------------------------ >> >> >> -- >> 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 >> ObjectWeb mailing lists service home page: http://www.objectweb.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 > ObjectWeb mailing lists service home page: http://www.objectweb.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 ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
|
|
Erik,
Let's focus on the Tree rendering of xforms:select1. I would like to know, in your estimation, what it costs to have this feature implemented in terms of time and dollars. Is there a well documented approach to take? Perhaps existing implementation can be the model. Thanks, Chary Erik Bruchez wrote: > Chary, > > Absolutely. We agree, and we do plan to enhance the OPS XForms engine > with better and richer components and yes, an extension API would be > great. But because we have limited resources, the main focus remains > over the next month to get an rock-solid and XForms-compliant > implementation out of the door. > > Remember that OPS is an open source project. We encourage developers > out there to participate by downloading the source code and > contributing to it. We are happy to answer questions and accept > patches, and in general to integrate contributors in the development > of OPS. > > Additionally, it is always possible to sponsor features. We typically > implement them for a fixed price. > > -Erik > > chary wrote: > >> >> Erik, >> >> I think, from application development view point, it is important to >> have a rich UI component set. I understand why "select1" is not >> rendered as a Tree view as the XForms spec does not say so (but >> XForms Processor does - and it is in my view, an important user >> interface). >> >> Perhaps XForms UI may not be your main focus, but, is there an >> attempt at making the XForms rendering as rich as possible? Are there >> any plugin 3rd party components in OPS? If not, is there a defined >> and documented process on how to create these components/extensions >> in OPS so that others interested in it can develop? >> Regards, >> Chary >> >> >> Erik Bruchez wrote: >> >>> Chary, >>> >>> The XForms specification does not specify how, or even whether, a >>> select1 can be rendered as a tree. OPS for the moment does not >>> support that kind of rendering. It supports radio buttons, dropdown >>> menus, and lists. This explains why your tree is not working. It >>> would be nice to have this feature in OPS as well, of course. Any >>> taker to implement it? >>> >>> -Erik >>> >>> chary wrote: >>> >>>> Erik, >>>> >>>> I am trying without success to display a selection list >>>> (full/compact/minimal) under OPS. Wonder what I am doing wrong! >>>> I would like to render a list as a TREE (e.g., Windows explorer). >>>> The examples of select1 do not render a Tree view as far as I know. >>>> >>>> The following, when viewed under XFORMS Player in IE shows a TREE >>>> listing. >>>> >>>> (FORMS PLAYER in IE) >>>> <xforms:select1 ref="greeting" appearance="compact"> >>>> <xforms:label>Choose a Greeting</xforms:label> >>>> <xforms:choices> >>>> <xforms:label>Veggie choices</xforms:label> >>>> <xforms:item> >>>> <xforms:label>Fried</xforms:label> >>>> <xforms:value>Potato</xforms:value> >>>> </xforms:item> >>>> <xforms:item> >>>> <xforms:label>Greens</xforms:label> >>>> <xforms:value>Beans</xforms:value> >>>> >>>> </xforms:item> >>>> </xfroms:choices> >>>> <xforms:item> >>>> <xforms:label>Hello</xforms:label> >>>> <xforms:value>Hello</xforms:value> >>>> >>>> </xforms:item> >>>> >>>> </xforms:select1> >>>> ------------------------------------------------------ >>>> Thanks, >>>> Chary >>> >>> >>> >>> >>> ------------------------------------------------------------------------ >>> >>> >>> >>> -- >>> 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 >>> ObjectWeb mailing lists service home page: http://www.objectweb.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 >> ObjectWeb mailing lists service home page: http://www.objectweb.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 >ObjectWeb mailing lists service home page: http://www.objectweb.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 ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
|
Administrator
|
Chary,
Is the result you are looking for something like this (you need FormsPlayer to see this): http://www.formsplayer.com/content/demo/1.0/choices.html In other words, showing a selection tree based on the hierarchy of <xforms:choice> in <xforms:select> and <xforms:select1>. <xforms:choice> may have embedded <xforms:itemset>, which means that it is possible to change the content of branches, but you cannot change the actual hierarchy of branches at runtime. I just want to make sure that we are not talking about a completely generic tree component here. I would think that implementing something like this, with the client-side and server-side code, would take about 2 man-days, i.e. 16 hours, and based on our hourly rate you get the actual cost ;-) Can you elaborate on what you mean by "documented approach"? -Erik chary wrote: > Erik, > > Let's focus on the Tree rendering of xforms:select1. I would like to > know, in your estimation, what it costs to have this feature implemented > in terms of time and dollars. Is there a well documented approach to > take? Perhaps existing implementation can be the model. > > Thanks, > Chary -- 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 ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
|
|
Erik, My answers are given below. Sorry for the delay. Erik Bruchez wrote: > Chary, > > Is the result you are looking for something like this (you need > FormsPlayer to see this): > > http://www.formsplayer.com/content/demo/1.0/choices.html > Yes. > In other words, showing a selection tree based on the hierarchy of > <xforms:choice> in <xforms:select> and <xforms:select1>. > > <xforms:choice> may have embedded <xforms:itemset>, which means that > it is possible to change the content of branches, but you cannot > change the actual hierarchy of branches at runtime. I just want to > make sure that we are not talking about a completely generic tree > component here. > Yes. > I would think that implementing something like this, with the > client-side and server-side code, would take about 2 man-days, i.e. 16 > hours, and based on our hourly rate you get the actual cost ;-) OK. > Can you elaborate on what you mean by "documented approach"? Here is what I meant by documented approach: the XForms controls(components) need to be implemented in full and in a way that provides rich user interaction and style. It is not sufficient to provide a minimalist solution in this regard. As you have suggested, other interested folks can provide implementations. Being new to this, I wanted to find out if there is a specific way to implement components such as select1. > -Erik > > chary wrote: > > Erik, > > Cheers, Chary > > Let's focus on the Tree rendering of xforms:select1. I would like to > > know, in your estimation, what it costs to have this feature > implemented > > in terms of time and dollars. Is there a well documented approach to > > take? Perhaps existing implementation can be the model. > > > > Thanks, > > Chary > > >------------------------------------------------------------------------ > > >-- >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 >ObjectWeb mailing lists service home page: http://www.objectweb.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 ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
|
Administrator
|
chary wrote:
>> Can you elaborate on what you mean by "documented approach"? > > > Here is what I meant by documented approach: the XForms > controls(components) need to be implemented in full and in a way > that provides rich user interaction and style. It is not sufficient > to provide a minimalist solution in this regard. As you have > suggested, other interested folks can provide implementations. Being > new to this, I wanted to find out if there is a specific way to > implement components such as select1. We absolutely agree that OPS needs to provide rich(er) components. BTW XForms does give implementors leeway. In particular, the hierarchial xforms:select1 your described is nowhere to be found in the spec. A particular implementor inferred that this was a good thing to do and just went ahead. Existing XForms controls can be this way enhanced to be richer than strictly what the specification is proposing. And then, you can create an XForms implementation which proposes new appearances for existing controls (which should allow those controls to work on compliant implementations, but likely with a difference of look and feel), or to create new components. However once you do this, you can no longer ensure that your XForms-based page will work on other implementations. -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 ObjectWeb mailing lists service home page: http://www.objectweb.org/wws |
«
Return to Orbeon Forms community mailing list
|
1 view|%1 views
| Free forum by Nabble | Edit this page |