Orbeon Forms community mailing list

DMV Forms Example

Classic

List

Threaded

81 messages Options

12345

Greg Jones-2

RE: Does Xforms bind foce ajax

Hi Richard,

There is nothing particularly wrong with having a different class for each
input, except for the need to maintain them. You are doing this anyway with
your individual input fields, so it's really not that much more work (if
any).

In fact, knowing that you are placing the fields in specific locations on
the page to match pre-printed forms (which may change), I assume you are
storing the form and field definitions independently of the view and using a
transform to generate the fields and their location attributes on the fly.
If that is the case, it's just as easy to generate the view and the matching
CSS as required.

Just a thought.

Regards,

Greg Jones

-----Original Message-----
From: Richard Braman [mailto:[hidden email]]
Sent: Friday, 10 February 2006 12:17 PM
To: [hidden email]
Subject: RE: [ops-users] Does Xforms bind foce ajax

In your solution I would need a different class for each input. Each
input has a different height, width, font size.
I also speficied the input as type="text", which is not a date picker,
but rather a text box. It is just as arbitrary to move
my style to a span tag. If this were being done in XML, no problem to
fix, but now its stuffed in with the native code.

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of
Alessandro Vernet
Sent: Thursday, February 09, 2006 8:20 PM
To: [hidden email]
Subject: Re: [ops-users] Does Xforms bind foce ajax

Hi Richard,

Since there is not a one to one mapping between XForms controls and HTML
elements, XForms control are often rendered by putting together a number
of HTML elements. This is the case for <xforms:input>, which appearance
can change as runtime from an input field to a date picker, and vice
versa. For instance, an <xforms:input> input is rendered as a span that
contains an input form element, a span that contains the date selected
with the date picker, and a span that contains an image you can click on
to show the date picker. If in the XForms code we find a class or style
attribute, on which one of those HTML elements should this attribute be
copied? The answer is always going to be arbitrary because we don't know
what you are trying to style. Should it be on the input form element,
the image? We chose to consistently copy the style and class attributes
on the container, in this case the span element.

What about using a class on the input? E.g. <xforms:input
class="large-input">. Then in CSS you do:

.large-input input { my CSS that applies to the HTML input form element
}

Alex

On 2/9/06, Richard Braman <[hidden email]> wrote:

> What if the height,width,and font-size of each input tag are
> different. I don't understand why the attributes of the <input> are
> being moved to the <span> by OPS. I don't understand the assumption
> that it is OK to move someones attributes from one tag to another. I
> also really don't understand what is accomplished by moving them. How
> can I fix this in theme.xsl? I rellay don't want to move them back
> because I never wanted them to move to begin with.
>
>
> -----Original Message-----
> From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik
> Bruchez
> Sent: Thursday, February 09, 2006 6:57 PM
> To: [hidden email]
> Subject: Re: [ops-users] Does Xforms bind foce ajax
>
>
> According to the HTML DTD:
>
> <!ELEMENT (SUB|SUP) - - (%inline;)* -- subscript, superscript -->
>
> <!ENTITY % inline "#PCDATA | %fontstyle; | %phrase; | %special; |
> %formctrl;">
>
> <!ENTITY % formctrl "INPUT | SELECT | TEXTAREA | LABEL | BUTTON">
>
> So it is perfectly legal to have an <input> inside a <span>. Of course

> styling the <span> is not equivalent to styling the <input>.
>
> Now back to your problem. Two things:
>
> 1. If most of your controls share styling attributes, you can use
> "class" as discussed earlier.
>
> 2. If you are looking to do absolute positioning, then positioning the

> <span> should work as well as positioning the <input>.
>
> 3. If really you want to move back the style to the <input>, you can
> do this with XSLT in theme.xsl.
>
> -Erik
>
> Richard Braman wrote:
> > Span tags are meant to format text, not inputs.
> > please review the following code in IE and tell me what works:
> >
> > <html>
> > <body>
> > <form>
> > <span style="font-size:11px;font-weight:bold">
> > <input type="text" name="doesnotwork">
> > </span>
> > <input type="text" name="styley"
> > style="font-size:11px;font-weight:bold">
> > </form>
> > </body>
> > </html>
> >
> > Putting this code in the native java is a buzkill.
> >
> > -----Original Message-----
> > From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik
> > Bruchez
> > Sent: Thursday, February 09, 2006 3:59 PM
> > To: [hidden email]
> > Subject: Re: [ops-users] Does Xforms bind foce ajax
> >
> >
> > Richard Braman wrote:
> > > It seems when I switched to using x forms:bid, it sent tverything

> > into > ajax.
> >
> > Not sure what you mean here.
> >
> > > I see at least one issue with ajax. The code below seems to puts

> > a
> >> span tag around the xforms input, which doesn't work on IE.
> >
> > Note that xforms-to-ajax-xhtml.xsl is no longer used: we should take

> > it out of the code base (just did that in the CVS). The translation
> > to
>
> > HTML is now done natively in Java.
> >
> > This said, we do put <span> around <input>. But all the OPS examples

> > do work with IE, and they too have <span> around <input>. What is
> > the specific problem you are seeing?
> >
> > > What if I don't want to use AJAX?
> >
> > The only way for now is to use XForms Classic, but then you don't
> > get any of the XForms improvements in OPS 3.0. In other words, you
> > get fairly limited XForms support with Classic.
> >
> > -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
>
>
>
>
>
>
>
> --
> 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
>
>
>

--
Blog (XML, Web apps, Open Source):
http://www.orbeon.com/blog/

--
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

Richard Braman

RE: Checkbox problem

In reply to this post by Erik Bruchez

How do you make a html checkbox then in xforms? I understand there is a
translation, but often times things get lost in translation, which is
also a movie starring Bill Murray. The extra irrelevant code makes the
pages larger in size.

-----Original Message-----
From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik Bruchez
Sent: Thursday, February 09, 2006 9:07 PM
To: [hidden email]
Subject: Re: [ops-users] Checkbox problem

You have to understand that there is a translation from XForms to XHTML
which is taking place here. Each XForms control generates "a bunch" of
XHTML elements that are useful to render the control and that also allow

client-side code to discover the controls. The generated HTML may or may

not match your expectations, but in general, there is a good rationale.
For example, the type of an input field can change at runtime, from
xs:string to xs:date for example, and from an input field become a date
picker. The server-side code currently places placeholders in place for
that this scenario. This could certainly be optimized, but for now it
works and in general the extra elements are of no consequence.

-Erik

Richard Braman wrote:
> Aside form my styling problem the other thing I don't get is how:
>
> <div style="position:absolute; left:615px; top:218px;
width:13px;

> height:14px;">
> <xforms:input pdf:x-position="707"
> pdf:y-position="891" xhtml:type="checkbox" bind="c1-1"
> xhtml:style="height:14px;width:13px;margin:0px;font-size:10px"/>
> </div>
>
> Becomes:
> <div style="position:absolute; left:615px; top:218px; width:13px;
> height:14px;"> <span id="xforms-element-93" class="xforms-control
> xforms-input" type="checkbox"
> style="height:14px;width:13px;margin:0px;font-size:10px"><span
> class="xforms-date-display"></span>
> <input type="text" name="xforms-element-93" value=""
> class="xforms-input-input xforms-type-string">
> <span class="xforms-showcalendar xforms-type-string"></span></span>
> <label class="xforms-alert xforms-alert-inactive"
> for="xforms-element-93"></label></div>
>
> Also , why is there this code, which I don't want or need. I am not
> tring to show a calendar. <span class="xforms-showcalendar
> xforms-type-string"></span> <span class="xforms-date-display"></span>

--
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

Richard Braman

RE: Does Xforms bind foce ajax

In reply to this post by Greg Jones-2

Wouldn't I have to worry about the styles being overwritten? I have
already seen this OPS.

For Example,

In Orbeon.css

input {border: 1px solid white;BACKGROUND-COLOR: #000000}

Write overs

In xforms.css
.xforms-input input {
border: 1px solid #7f9db9;
padding-bottom: 3px;
padding-left: 1px;
padding-right: 1px;
}

And

In theme.css
input, textarea, select {
color : #000000;
font: normal 11px Verdana, Arial, Helvetica, sans-serif;
}

This made my inputs all black, which was cool and daring but not user
friendly
I mean there are already three input styles in 3 different places. This
is confusing to me, but I am admittedly a simple person.

I can do anything, because yes I do "generate the views", allbeit not on
the fly.

-----Original Message-----
From: Greg Jones [mailto:[hidden email]]
Sent: Thursday, February 09, 2006 9:14 PM
To: [hidden email]
Subject: RE: [ops-users] Does Xforms bind foce ajax

Hi Richard,

There is nothing particularly wrong with having a different class for
each input, except for the need to maintain them. You are doing this
anyway with your individual input fields, so it's really not that much
more work (if any).

In fact, knowing that you are placing the fields in specific locations
on the page to match pre-printed forms (which may change), I assume you
are storing the form and field definitions independently of the view and
using a transform to generate the fields and their location attributes
on the fly. If that is the case, it's just as easy to generate the view
and the matching CSS as required.

Just a thought.

Regards,

Greg Jones

-----Original Message-----
From: Richard Braman [mailto:[hidden email]]
Sent: Friday, 10 February 2006 12:17 PM
To: [hidden email]
Subject: RE: [ops-users] Does Xforms bind foce ajax

In your solution I would need a different class for each input. Each
input has a different height, width, font size.
I also speficied the input as type="text", which is not a date picker,
but rather a text box. It is just as arbitrary to move my style to a
span tag. If this were being done in XML, no problem to fix, but now
its stuffed in with the native code.

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of
Alessandro Vernet
Sent: Thursday, February 09, 2006 8:20 PM
To: [hidden email]
Subject: Re: [ops-users] Does Xforms bind foce ajax

Hi Richard,

Since there is not a one to one mapping between XForms controls and HTML
elements, XForms control are often rendered by putting together a number
of HTML elements. This is the case for <xforms:input>, which appearance
can change as runtime from an input field to a date picker, and vice
versa. For instance, an <xforms:input> input is rendered as a span that
contains an input form element, a span that contains the date selected
with the date picker, and a span that contains an image you can click on
to show the date picker. If in the XForms code we find a class or style
attribute, on which one of those HTML elements should this attribute be
copied? The answer is always going to be arbitrary because we don't know
what you are trying to style. Should it be on the input form element,
the image? We chose to consistently copy the style and class attributes
on the container, in this case the span element.

What about using a class on the input? E.g. <xforms:input
class="large-input">. Then in CSS you do:

.large-input input { my CSS that applies to the HTML input form element
}

Alex

On 2/9/06, Richard Braman <[hidden email]> wrote:

> > into > ajax.
> >
> > Not sure what you mean here.
> >
> > > I see at least one issue with ajax. The code below seems to puts

http://www.objectweb.org/wws
>
>
>

Richard Braman

RE: Does Xforms bind foce ajax

In reply to this post by Greg Jones-2

Also,

Why is there is
<span class="xforms-date-display"></span>
I know its part of the translation, but I think it is dangerous.
You have to be carefull in translation because if you add thing to that
the original speaker didn't say you can cause large problems.
I happens in world politics every day.

I will consider the CSS idea as development progresses.

-----Original Message-----
From: Greg Jones [mailto:[hidden email]]
Sent: Thursday, February 09, 2006 9:14 PM
To: [hidden email]
Subject: RE: [ops-users] Does Xforms bind foce ajax

Hi Richard,

There is nothing particularly wrong with having a different class for
each input, except for the need to maintain them. You are doing this
anyway with your individual input fields, so it's really not that much
more work (if any).

In fact, knowing that you are placing the fields in specific locations
on the page to match pre-printed forms (which may change), I assume you
are storing the form and field definitions independently of the view and
using a transform to generate the fields and their location attributes
on the fly. If that is the case, it's just as easy to generate the view
and the matching CSS as required.

Just a thought.

Regards,

Greg Jones

-----Original Message-----
From: Richard Braman [mailto:[hidden email]]
Sent: Friday, 10 February 2006 12:17 PM
To: [hidden email]
Subject: RE: [ops-users] Does Xforms bind foce ajax

In your solution I would need a different class for each input. Each
input has a different height, width, font size.
I also speficied the input as type="text", which is not a date picker,
but rather a text box. It is just as arbitrary to move my style to a
span tag. If this were being done in XML, no problem to fix, but now
its stuffed in with the native code.

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of
Alessandro Vernet
Sent: Thursday, February 09, 2006 8:20 PM
To: [hidden email]
Subject: Re: [ops-users] Does Xforms bind foce ajax

Hi Richard,

Since there is not a one to one mapping between XForms controls and HTML
elements, XForms control are often rendered by putting together a number
of HTML elements. This is the case for <xforms:input>, which appearance
can change as runtime from an input field to a date picker, and vice
versa. For instance, an <xforms:input> input is rendered as a span that
contains an input form element, a span that contains the date selected
with the date picker, and a span that contains an image you can click on
to show the date picker. If in the XForms code we find a class or style
attribute, on which one of those HTML elements should this attribute be
copied? The answer is always going to be arbitrary because we don't know
what you are trying to style. Should it be on the input form element,
the image? We chose to consistently copy the style and class attributes
on the container, in this case the span element.

What about using a class on the input? E.g. <xforms:input
class="large-input">. Then in CSS you do:

.large-input input { my CSS that applies to the HTML input form element
}

Alex

On 2/9/06, Richard Braman <[hidden email]> wrote:

> > into > ajax.
> >
> > Not sure what you mean here.
> >
> > > I see at least one issue with ajax. The code below seems to puts

http://www.objectweb.org/wws
>
>
>

Alessandro Vernet

Re: Checkbox problem

Administrator

In reply to this post by Richard Braman

Hi Richard,

On 2/9/06, Richard Braman <[hidden email]> wrote:
> How do you make a html checkbox then in xforms?

An <xforms:select appearance="full"> will be rendered with check
boxes. The XForms Controls example may help, as it shows the different
appearances that can be used on select and select1 (result in the
attached screenshot).

Alex
--
Blog (XML, Web apps, Open Source):
http://www.orbeon.com/blog/

--
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

select.png (15K) Download Attachment

--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet

Alessandro Vernet

Re: Does Xforms bind foce ajax

Administrator

In reply to this post by Richard Braman

On 2/9/06, Richard Braman <[hidden email]> wrote:
> I mean there are already three input styles in 3 different places.

Hi Richard,

In OPS 3, there are 3 CSS files: orbeon.css, xforms.css, and calendar-blue.css.

1) orbeon.css is really just used for the examples. So I recommend you
remove the reference to this file in your application (see
config/theme/theme.xsl).
2) xforms.css is used by the XForms controls. All the class names in
this CSS file start with "xforms-", so you shouldn't have clashes with
your own names.
3) calendar-blue.css is used by the jscalender component, which will
come into play if you have a input control bound to a node of type
xs:date.

I hope this helps,

Alex
--
Blog (XML, Web apps, Open Source):
http://www.orbeon.com/blog/

--
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

--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet

Richard Braman

RE: Does Xforms bind foce ajax

There is also theme.css. Should I remove this too?

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of
Alessandro Vernet
Sent: Thursday, February 09, 2006 9:59 PM
To: [hidden email]
Subject: Re: [ops-users] Does Xforms bind foce ajax

On 2/9/06, Richard Braman <[hidden email]> wrote:
> I mean there are already three input styles in 3 different places.

Hi Richard,

In OPS 3, there are 3 CSS files: orbeon.css, xforms.css, and
calendar-blue.css.

1) orbeon.css is really just used for the examples. So I recommend you
remove the reference to this file in your application (see
config/theme/theme.xsl).
2) xforms.css is used by the XForms controls. All the class names in
this CSS file start with "xforms-", so you shouldn't have clashes with
your own names.
3) calendar-blue.css is used by the jscalender component, which will
come into play if you have a input control bound to a node of type
xs:date.

I hope this helps,

Alex
--
Blog (XML, Web apps, Open Source):
http://www.orbeon.com/blog/

--
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

Richard Braman

RE: Checkbox problem

In reply to this post by Alessandro Vernet

Alex,
Xforms:select renders nothing in the way of html checkboxes on my OPS
3.01:

<div style="position:absolute; left:132px; top:409px; width:14px;
height:14px;">
<xforms:select appearance="full" pdf:x-position="224"
pdf:y-position="699" bind="c1-3"
xhtml:style="height:14px;width:14px;margin:0px;font-size:10px"/>
</div>

Produces:
<div style="position:absolute; left:132px; top:409px; width:14px;
height:14px;"><span id="xforms-element-101" class="xforms-control
xforms-select-full"
style="height:14px;width:14px;margin:0px;font-size:10px"></span><label
class="xforms-alert xforms-alert-inactive"
for="xforms-element-101"></label></div>

Rich

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of
Alessandro Vernet
Sent: Thursday, February 09, 2006 9:50 PM
To: [hidden email]
Subject: Re: [ops-users] Checkbox problem

Hi Richard,

On 2/9/06, Richard Braman <[hidden email]> wrote:
> How do you make a html checkbox then in xforms?

An <xforms:select appearance="full"> will be rendered with check boxes.
The XForms Controls example may help, as it shows the different
appearances that can be used on select and select1 (result in the
attached screenshot).

Alex
--
Blog (XML, Web apps, Open Source):
http://www.orbeon.com/blog/

--
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

Alessandro Vernet

Re: Does Xforms bind foce ajax

Administrator

In reply to this post by Richard Braman

On 2/9/06, Richard Braman <[hidden email]> wrote:
> There is also theme.css. Should I remove this too?

Hi Richard,

The theme.css is added by config/xforms-to-xhtml.xsl. So if you see
this, it would mean that you are using XForms classic, which I don't
think is the case, right? In any case, I don't see anything you would
need to have in theme.css. So yes, you should be able to get rid of it
(and remove the reference in xforms-to-xhtml.xsl).

Alex
--
Blog (XML, Web apps, Open Source):
http://www.orbeon.com/blog/

--
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

--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet

Adrian Baker-2

Re: Checkbox problem

In reply to this post by Richard Braman

Does your select have an itemset (a list of possible items to select
from)? It doesn't appear so from the snippet you've pasted.

Try looking at the example at
http://www.orbeon.com/ops/goto-example/xforms-controls, under the
'Selection controls' tab.

Adrian

Richard Braman wrote:

> Alex,
> Xforms:select renders nothing in the way of html checkboxes on my OPS
> 3.01:
>
> <div style="position:absolute; left:132px; top:409px; width:14px;
> height:14px;">
> <xforms:select appearance="full" pdf:x-position="224"
> pdf:y-position="699" bind="c1-3"
> xhtml:style="height:14px;width:14px;margin:0px;font-size:10px"/>
> </div>
>
> Produces:
> <div style="position:absolute; left:132px; top:409px; width:14px;
> height:14px;"><span id="xforms-element-101" class="xforms-control
> xforms-select-full"
> style="height:14px;width:14px;margin:0px;font-size:10px"></span><label
> class="xforms-alert xforms-alert-inactive"
> for="xforms-element-101"></label></div>
>
> Rich
>

Richard Braman

RE: Checkbox problem/node splitting

OK, suppose I have a node in my instance
<boolean_node> which can have either the value 'X' or be empty
If it is X I want my checkbox to be checked if it is empty I want
nothing. The checkbox doesn't have any label or anything else, it is
either checked or unchecked.

This is my first crack , but I know I am missing something

<xforms:model>
<xforms:instance>
<form>
<SEQ0010>X</SEQ0010>
</form>
</xforms:instance>

</xforms:model>
<xforms:bind id="chk1" nodeset="/form/SEQ0010">
<xforms:select bind="ck-1">
<items>
<true value="X"/>
<false value=""/>
</items>
</xforms:select>

-----Original Message-----
From: Adrian Baker [mailto:[hidden email]]
Sent: Thursday, February 09, 2006 11:20 PM
To: [hidden email]
Subject: Re: [ops-users] Checkbox problem

Does your select have an itemset (a list of possible items to select
from)? It doesn't appear so from the snippet you've pasted.

Try looking at the example at
http://www.orbeon.com/ops/goto-example/xforms-controls, under the
'Selection controls' tab.

Adrian

Richard Braman wrote:

Richard Braman
mailto:[hidden email]
561.748.4002 (voice)

http://www.taxcodesoftware.org
Free Open Source Tax Software

--
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 Bruchez

Re: Checkbox problem/node splitting

Administrator

Richard Braman wrote:

> OK, suppose I have a node in my instance
> <boolean_node> which can have either the value 'X' or be empty
> If it is X I want my checkbox to be checked if it is empty I want
> nothing. The checkbox doesn't have any label or anything else, it is
> either checked or unchecked.
>
> This is my first crack , but I know I am missing something
>
> <xforms:model>
> <xforms:instance>
> <form>
> <SEQ0010>X</SEQ0010>
> </form>
> </xforms:instance>
>
>
> </xforms:model>
> <xforms:bind id="chk1" nodeset="/form/SEQ0010">
> <xforms:select bind="ck-1">
> <items>
> <true value="X"/>
> <false value=""/>
> </items>
> </xforms:select>

Try:

<xforms:select bind="ck-1" appearance="full">
<xforms:label/>
<xforms:item>
<xforms:name/>
<xforms:value>X</xforms:value>
</xforms:item>
</xforms:select>

-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

Richard Braman

RE: Checkbox problem/node splitting

Erik, That worked, but suppose there are two checkboxes and the
checkboes must be mutually exclusive, so that if one is checked then the
other cannot be. How does that change the syntax?

-----Original Message-----
From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik Bruchez
Sent: Monday, February 13, 2006 9:35 AM
To: [hidden email]
Subject: Re: [ops-users] Checkbox problem/node splitting

Richard Braman wrote:

> OK, suppose I have a node in my instance
> <boolean_node> which can have either the value 'X' or be empty If it
> is X I want my checkbox to be checked if it is empty I want nothing.
> The checkbox doesn't have any label or anything else, it is either
> checked or unchecked.
>
> This is my first crack , but I know I am missing something
>
> <xforms:model>
> <xforms:instance>
> <form>
> <SEQ0010>X</SEQ0010>
> </form>
> </xforms:instance>
>
>
> </xforms:model>
> <xforms:bind id="chk1" nodeset="/form/SEQ0010"> <xforms:select
> bind="ck-1">
> <items>
> <true value="X"/>
> <false value=""/>
> </items>
> </xforms:select>

Adrian Baker-2

Re: Checkbox problem/node splitting

That sounds like a select1 - replace your select with a select1.

Richard Braman wrote:

Erik,  That worked, but suppose there are two checkboxes and the
checkboes must be mutually exclusive, so that if one is checked then the
other cannot be.  How does that change the syntax?

-----Original Message-----
From: Erik Bruchez [[hidden email]] On Behalf Of Erik Bruchez
Sent: Monday, February 13, 2006 9:35 AM
To: [hidden email]
Subject: Re: [ops-users] Checkbox problem/node splitting

Richard Braman wrote:

OK, suppose I have a node in my instance
<boolean_node> which can have either the value 'X' or be empty If it 
is X I want my checkbox to be checked if it is empty I want nothing.  
The checkbox doesn't have any label or anything else, it is either 
checked or unchecked.

This is my first crack , but I know I am missing something

<xforms:model>
<xforms:instance>
<form>
<SEQ0010>X</SEQ0010>
</form>
</xforms:instance>


</xforms:model>
<xforms:bind id="chk1" nodeset="/form/SEQ0010"> <xforms:select 
bind="ck-1">
	<items>
      	<true value="X"/>
		<false value=""/>
	</items>
</xforms:select>


Try:

<xforms:select bind="ck-1" appearance="full">
   <xforms:label/>
   <xforms:item>
     <xforms:name/>
     <xforms:value>X</xforms:value>
   </xforms:item>
</xforms:select>

-Erik

Richard Braman

RE: Checkbox problem/node splitting

In reply to this post by Richard Braman

ON that last question, assume the controls are bound to 2 separate
nodes.

-----Original Message-----
From: Richard Braman [mailto:[hidden email]]
Sent: Monday, February 13, 2006 6:51 PM
To: [hidden email]
Subject: RE: [ops-users] Checkbox problem/node splitting

Erik, That worked, but suppose there are two checkboxes and the
checkboes must be mutually exclusive, so that if one is checked then the
other cannot be. How does that change the syntax?

-----Original Message-----
From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik Bruchez
Sent: Monday, February 13, 2006 9:35 AM
To: [hidden email]
Subject: Re: [ops-users] Checkbox problem/node splitting

Richard Braman wrote:

Erik Bruchez

Re: Checkbox problem/node splitting

Administrator

So, two checkboxes, each bound to a different node, and exclusive. Can
they both be unchecked?

-Erik

Richard Braman wrote:

> ON that last question, assume the controls are bound to 2 separate
> nodes.
>
> -----Original Message-----
> From: Richard Braman [mailto:[hidden email]]
> Sent: Monday, February 13, 2006 6:51 PM
> To: [hidden email]
> Subject: RE: [ops-users] Checkbox problem/node splitting
>
>
> Erik, That worked, but suppose there are two checkboxes and the
> checkboes must be mutually exclusive, so that if one is checked then the
> other cannot be. How does that change the syntax?
>
> -----Original Message-----
> From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik Bruchez
> Sent: Monday, February 13, 2006 9:35 AM
> To: [hidden email]
> Subject: Re: [ops-users] Checkbox problem/node splitting
>
>
> Richard Braman wrote:
>> OK, suppose I have a node in my instance
>> <boolean_node> which can have either the value 'X' or be empty If it
>> is X I want my checkbox to be checked if it is empty I want nothing.
>> The checkbox doesn't have any label or anything else, it is either
>> checked or unchecked.
>>
>> This is my first crack , but I know I am missing something
>>
>> <xforms:model>
>> <xforms:instance>
>> <form>
>> <SEQ0010>X</SEQ0010>
>> </form>
>> </xforms:instance>
>>
>>
>> </xforms:model>
>> <xforms:bind id="chk1" nodeset="/form/SEQ0010"> <xforms:select
>> bind="ck-1">
>> <items>
>> <true value="X"/>
>> <false value=""/>
>> </items>
>> </xforms:select>
>
> Try:
>
> <xforms:select bind="ck-1" appearance="full">
> <xforms:label/>
> <xforms:item>
> <xforms:name/>
> <xforms:value>X</xforms:value>
> </xforms:item>
> </xforms:select>
>
> -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

Richard Braman

RE: Checkbox problem/node splitting

They could both be unchecked yes.

-----Original Message-----
From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik Bruchez
Sent: Monday, February 13, 2006 7:37 PM
To: [hidden email]
Subject: Re: [ops-users] Checkbox problem/node splitting

So, two checkboxes, each bound to a different node, and exclusive. Can
they both be unchecked?

-Erik

Richard Braman wrote:

> ON that last question, assume the controls are bound to 2 separate
> nodes.
>
> -----Original Message-----
> From: Richard Braman [mailto:[hidden email]]
> Sent: Monday, February 13, 2006 6:51 PM
> To: [hidden email]
> Subject: RE: [ops-users] Checkbox problem/node splitting
>
>
> Erik, That worked, but suppose there are two checkboxes and the
> checkboes must be mutually exclusive, so that if one is checked then
> the other cannot be. How does that change the syntax?
>
> -----Original Message-----
> From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik
> Bruchez
> Sent: Monday, February 13, 2006 9:35 AM
> To: [hidden email]
> Subject: Re: [ops-users] Checkbox problem/node splitting
>
>
> Richard Braman wrote:
>> OK, suppose I have a node in my instance
>> <boolean_node> which can have either the value 'X' or be empty If it
>> is X I want my checkbox to be checked if it is empty I want nothing.
>> The checkbox doesn't have any label or anything else, it is either
>> checked or unchecked.
>>
>> This is my first crack , but I know I am missing something
>>
>> <xforms:model>
>> <xforms:instance>
>> <form>
>> <SEQ0010>X</SEQ0010>
>> </form>
>> </xforms:instance>
>>
>>
>> </xforms:model>
>> <xforms:bind id="chk1" nodeset="/form/SEQ0010"> <xforms:select
>> bind="ck-1">
>> <items>
>> <true value="X"/>
>> <false value=""/>
>> </items>
>> </xforms:select>
>
> Try:
>
> <xforms:select bind="ck-1" appearance="full">
> <xforms:label/>
> <xforms:item>
> <xforms:name/>
> <xforms:value>X</xforms:value>
> </xforms:item>
> </xforms:select>
>
> -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

Erik Bruchez

Re: Checkbox problem/node splitting

Administrator

Something like this should do:

<xforms:select1 ref="/path/to/my-node-1" ...>
<xforms:setvalue ev:event="xforms-value-changed"
ref="/path/to/my-node-2"
value="''"/>

</xforms:select1>

<xforms:select1 ref="/path/to/my-node-2" ...>
<xforms:setvalue ev:event="xforms-value-changed"
ref="/path/to/my-node-1"
value="''"/>

</xforms:select1>

I.e. each time you change the value of one of the checkboxes, that
clears the other one.

-Erik

Richard Braman wrote:

> They could both be unchecked yes.
>
> -----Original Message-----
> From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik Bruchez
> Sent: Monday, February 13, 2006 7:37 PM
> To: [hidden email]
> Subject: Re: [ops-users] Checkbox problem/node splitting
>
>
> So, two checkboxes, each bound to a different node, and exclusive. Can
> they both be unchecked?
>
> -Erik
>
> Richard Braman wrote:
>> ON that last question, assume the controls are bound to 2 separate
>> nodes.
>>
>> -----Original Message-----
>> From: Richard Braman [mailto:[hidden email]]
>> Sent: Monday, February 13, 2006 6:51 PM
>> To: [hidden email]
>> Subject: RE: [ops-users] Checkbox problem/node splitting
>>
>>
>> Erik, That worked, but suppose there are two checkboxes and the
>> checkboes must be mutually exclusive, so that if one is checked then
>> the other cannot be. How does that change the syntax?
>>
>> -----Original Message-----
>> From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik
>> Bruchez
>> Sent: Monday, February 13, 2006 9:35 AM
>> To: [hidden email]
>> Subject: Re: [ops-users] Checkbox problem/node splitting
>>
>>
>> Richard Braman wrote:
>>> OK, suppose I have a node in my instance
>>> <boolean_node> which can have either the value 'X' or be empty If it
>>> is X I want my checkbox to be checked if it is empty I want nothing.
>>> The checkbox doesn't have any label or anything else, it is either
>>> checked or unchecked.
>>>
>>> This is my first crack , but I know I am missing something
>>>
>>> <xforms:model>
>>> <xforms:instance>
>>> <form>
>>> <SEQ0010>X</SEQ0010>
>>> </form>
>>> </xforms:instance>
>>>
>>>
>>> </xforms:model>
>>> <xforms:bind id="chk1" nodeset="/form/SEQ0010"> <xforms:select
>>> bind="ck-1">
>>> <items>
>>> <true value="X"/>
>>> <false value=""/>
>>> </items>
>>> </xforms:select>
>> Try:
>>
>> <xforms:select bind="ck-1" appearance="full">
>> <xforms:label/>
>> <xforms:item>
>> <xforms:name/>
>> <xforms:value>X</xforms:value>
>> </xforms:item>
>> </xforms:select>
>>
>> -Erik

Richard Braman

RE: Checkbox problem/node splitting

Erik,

Both of the selects I have use bind instead of ref. Also select1 seems
to produce a radio button instead of a checkbox.
I tried this code instead:
<xforms:select appearance="full" bind="c1-1" >
<xforms:setvalue
ev:event="xforms-value-changed" ref="/form/f1040ez/SEQ0110" value="''"/>
<xforms:label/>
<xforms:item>
<xforms:name/>
<xforms:value>X</xforms:value>
</xforms:item>
</xforms:select>
<xforms:select appearance="full" bind="c1-2" >
<xforms:setvalue ev:event="xforms-value-changed"
ref="/form/f1040ez/SEQ0100" value="''"/>
<xforms:label/>
<xforms:item>
<xforms:name/>
<xforms:value>X</xforms:value>
</xforms:item>
</xforms:select>

Which is close, but when you check one (while the other one is already
checked) it unchecks the other checkbox and itself. The same thing
happens if I do select1 (but with radio button instead of checkboxes).
I think it must have something to do with binding.

See the presidential election campaign fund checkboxes on the form:
http://24.75.221.234:8080/taxcode/1040ez

-----Original Message-----
From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik Bruchez
Sent: Tuesday, February 14, 2006 2:12 PM
To: [hidden email]
Subject: Re: [ops-users] Checkbox problem/node splitting

Something like this should do:

<xforms:select1 ref="/path/to/my-node-1" ...>
<xforms:setvalue ev:event="xforms-value-changed"
ref="/path/to/my-node-2"
value="''"/>

</xforms:select1>

<xforms:select1 ref="/path/to/my-node-2" ...>
<xforms:setvalue ev:event="xforms-value-changed"
ref="/path/to/my-node-1"
value="''"/>

</xforms:select1>

I.e. each time you change the value of one of the checkboxes, that
clears the other one.

-Erik

Richard Braman wrote:

> They could both be unchecked yes.
>
> -----Original Message-----
> From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik
> Bruchez
> Sent: Monday, February 13, 2006 7:37 PM
> To: [hidden email]
> Subject: Re: [ops-users] Checkbox problem/node splitting
>
>
> So, two checkboxes, each bound to a different node, and exclusive. Can
> they both be unchecked?
>
> -Erik
>
> Richard Braman wrote:
>> ON that last question, assume the controls are bound to 2 separate
>> nodes.
>>
>> -----Original Message-----
>> From: Richard Braman [mailto:[hidden email]]
>> Sent: Monday, February 13, 2006 6:51 PM
>> To: [hidden email]
>> Subject: RE: [ops-users] Checkbox problem/node splitting
>>
>>
>> Erik, That worked, but suppose there are two checkboxes and the
>> checkboes must be mutually exclusive, so that if one is checked then
>> the other cannot be. How does that change the syntax?
>>
>> -----Original Message-----
>> From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik
>> Bruchez
>> Sent: Monday, February 13, 2006 9:35 AM
>> To: [hidden email]
>> Subject: Re: [ops-users] Checkbox problem/node splitting
>>
>>
>> Richard Braman wrote:
>>> OK, suppose I have a node in my instance
>>> <boolean_node> which can have either the value 'X' or be empty If it
>>> is X I want my checkbox to be checked if it is empty I want nothing.
>>> The checkbox doesn't have any label or anything else, it is either
>>> checked or unchecked.
>>>
>>> This is my first crack , but I know I am missing something
>>>
>>> <xforms:model>
>>> <xforms:instance>
>>> <form>
>>> <SEQ0010>X</SEQ0010>
>>> </form>
>>> </xforms:instance>
>>>
>>>
>>> </xforms:model>
>>> <xforms:bind id="chk1" nodeset="/form/SEQ0010"> <xforms:select
>>> bind="ck-1">
>>> <items>
>>> <true value="X"/>
>>> <false value=""/>
>>> </items>
>>> </xforms:select>
>> Try:
>>
>> <xforms:select bind="ck-1" appearance="full">
>> <xforms:label/>
>> <xforms:item>
>> <xforms:name/>
>> <xforms:value>X</xforms:value>
>> </xforms:item>
>> </xforms:select>
>>
>> -Erik

Ryan Puddephatt

RE: Checkbox problem/node splitting

Richard,
Use select1 instead of select

Ryan Puddephatt
Software Engineer
TFX Group - IT UK
1 Michaelson Square
Livingston
West Lothian
Scotand
EH54 7DP

* [hidden email]
( 01506 407 110
7 01506 407 108

>-----Original Message-----
>From: Richard Braman [mailto:[hidden email]]
>Sent: 14 February 2006 20:05
>To: [hidden email]
>Subject: RE: [ops-users] Checkbox problem/node splitting
>
>Erik,
>
>Both of the selects I have use bind instead of ref. Also select1 seems
>to produce a radio button instead of a checkbox.
>I tried this code instead:
> <xforms:select appearance="full" bind="c1-1" >
> <xforms:setvalue
>ev:event="xforms-value-changed" ref="/form/f1040ez/SEQ0110" value="''"/>
> <xforms:label/>
> <xforms:item>
> <xforms:name/>
> <xforms:value>X</xforms:value>
> </xforms:item>
> </xforms:select>
> <xforms:select appearance="full" bind="c1-2" >
> <xforms:setvalue ev:event="xforms-value-changed"
>ref="/form/f1040ez/SEQ0100" value="''"/>
> <xforms:label/>
> <xforms:item>
> <xforms:name/>
> <xforms:value>X</xforms:value>
> </xforms:item>
> </xforms:select>
>
>Which is close, but when you check one (while the other one is already
>checked) it unchecks the other checkbox and itself. The same thing
>happens if I do select1 (but with radio button instead of checkboxes).
>I think it must have something to do with binding.
>
>See the presidential election campaign fund checkboxes on the form:
>http://24.75.221.234:8080/taxcode/1040ez
>
>
>
>-----Original Message-----
>From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik Bruchez
>Sent: Tuesday, February 14, 2006 2:12 PM
>To: [hidden email]
>Subject: Re: [ops-users] Checkbox problem/node splitting
>
>
>Something like this should do:
>
><xforms:select1 ref="/path/to/my-node-1" ...>
> <xforms:setvalue ev:event="xforms-value-changed"
> ref="/path/to/my-node-2"
> value="''"/>
>
></xforms:select1>
>
><xforms:select1 ref="/path/to/my-node-2" ...>
> <xforms:setvalue ev:event="xforms-value-changed"
> ref="/path/to/my-node-1"
> value="''"/>
>
></xforms:select1>
>
>I.e. each time you change the value of one of the checkboxes, that
>clears the other one.
>
>-Erik
>
>Richard Braman wrote:
>> They could both be unchecked yes.
>>
>> -----Original Message-----
>> From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik
>> Bruchez
>> Sent: Monday, February 13, 2006 7:37 PM
>> To: [hidden email]
>> Subject: Re: [ops-users] Checkbox problem/node splitting
>>
>>
>> So, two checkboxes, each bound to a different node, and exclusive. Can
>> they both be unchecked?
>>
>> -Erik
>>
>> Richard Braman wrote:
>>> ON that last question, assume the controls are bound to 2 separate
>>> nodes.
>>>
>>> -----Original Message-----
>>> From: Richard Braman [mailto:[hidden email]]
>>> Sent: Monday, February 13, 2006 6:51 PM
>>> To: [hidden email]
>>> Subject: RE: [ops-users] Checkbox problem/node splitting
>>>
>>>
>>> Erik, That worked, but suppose there are two checkboxes and the
>>> checkboes must be mutually exclusive, so that if one is checked then
>>> the other cannot be. How does that change the syntax?
>>>
>>> -----Original Message-----
>>> From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik
>>> Bruchez
>>> Sent: Monday, February 13, 2006 9:35 AM
>>> To: [hidden email]
>>> Subject: Re: [ops-users] Checkbox problem/node splitting
>>>
>>>
>>> Richard Braman wrote:
>>>> OK, suppose I have a node in my instance
>>>> <boolean_node> which can have either the value 'X' or be empty If it
>>>> is X I want my checkbox to be checked if it is empty I want nothing.
>>>> The checkbox doesn't have any label or anything else, it is either
>>>> checked or unchecked.
>>>>
>>>> This is my first crack , but I know I am missing something
>>>>
>>>> <xforms:model>
>>>> <xforms:instance>
>>>> <form>
>>>> <SEQ0010>X</SEQ0010>
>>>> </form>
>>>> </xforms:instance>
>>>>
>>>>
>>>> </xforms:model>
>>>> <xforms:bind id="chk1" nodeset="/form/SEQ0010"> <xforms:select
>>>> bind="ck-1">
>>>> <items>
>>>> <true value="X"/>
>>>> <false value=""/>
>>>> </items>
>>>> </xforms:select>
>>> Try:
>>>
>>> <xforms:select bind="ck-1" appearance="full">
>>> <xforms:label/>
>>> <xforms:item>
>>> <xforms:name/>
>>> <xforms:value>X</xforms:value>
>>> </xforms:item>
>>> </xforms:select>
>>>
>>> -Erik
>
>
>

12345