Orbeon Forms community mailing list

Warning of unstable nightly builds starting later today

Classic

List

Threaded

27 messages Options

Erik Bruchez

Warning of unstable nightly builds starting later today

Administrator

All,

The new and improved client-side JavaScript code will probably be
checked in later today, but there are still some known issues associated
with it.

Since this code is likely to break your app, we don't recommend getting
nightlies while we work on fixing those issues.

On the other hand committing this will encourage us to fix the remaining
issues quickly!

-Erik

--
Orbeon - XForms Everywhere:
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

Adrian Baker

RE: Warning of unstable nightly builds starting later today

[ops-users] Warning of unstable nightly builds starting later today

Hi Erik,

Does this warning still stand? We're having some bad javascript initialisation issues with a build of OPS which is about a month old now. Ideally we'd upgrade, but obviously if the code isn't yet stable we can't. Perhaps there is a particular CVS version we could move to which would help ?

Adrian

From: Erik Bruchez on behalf of Erik Bruchez
Sent: Tue 25/07/2006 7:17 a.m.
To: [hidden email]
Subject: [ops-users] Warning of unstable nightly builds starting later today

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

Ryan Puddephatt

RE: Warning of unstable nightly builds starting later today

[ops-users] Warning of unstable nightly builds starting later today

Adrian,

I have a build from two days ago (before the warning) if you would like it

Ryan

Ryan Puddephatt
Software Engineer

Teleflex Group - IT UK
1 Michaelson Square
Livingston
West Lothian
Scotland
EH54 7DP

e> [hidden email]
t> +44(0)1506 407 110
f> +44(0)1506 407 108
w> www.teleflex.com

From: Adrian Baker [mailto:[hidden email]]
Sent: 26 July 2006 00:52
To: [hidden email]; [hidden email]
Subject: RE: [ops-users] Warning of unstable nightly builds starting later today

Hi Erik,

Does this warning still stand? We're having some bad javascript initialisation issues with a build of OPS which is about a month old now. Ideally we'd upgrade, but obviously if the code isn't yet stable we can't. Perhaps there is a particular CVS version we could move to which would help ?

Adrian

From: Erik Bruchez on behalf of Erik Bruchez
Sent: Tue 25/07/2006 7:17 a.m.
To: [hidden email]
Subject: [ops-users] Warning of unstable nightly builds starting later today

All,

The new and improved client-side JavaScript code will probably be
checked in later today, but there are still some known issues associated
with it.

Since this code is likely to break your app, we don't recommend getting
nightlies while we work on fixing those issues.

On the other hand committing this will encourage us to fix the remaining
issues quickly!

-Erik

--
Orbeon - XForms Everywhere:
http://www.orbeon.com/blog/

Erik Bruchez

Re: Warning of unstable nightly builds starting later today

Administrator

In reply to this post by Adrian Baker

Adrian,

As of now most basic features work again, but you may still find issues.
If you do, please let us know. Things that won't work for sure are the
more fancy controls, including range, autocomplete, HTML area, tree, and
menu, because we haven't hooked up the new initialization code yet. But
that's coming soon.

The purpose of the new JavaScript code is to make client-side
initialization super-fast. You have to get current builds to get this
benefit. "Pre-warning" builds will have the older JavaScript code.

-Erik

Adrian Baker wrote:

> Hi Erik,
>
> Does this warning still stand? We're having some bad javascript
> initialisation issues with a build of OPS which is about a month old
> now. Ideally we'd upgrade, but obviously if the code isn't yet stable we
> can't. Perhaps there is a particular CVS version we could move to which
> would help ?
>
> Adrian
>
> ------------------------------------------------------------------------
> *From:* Erik Bruchez on behalf of Erik Bruchez
> *Sent:* Tue 25/07/2006 7:17 a.m.
> *To:* [hidden email]
> *Subject:* [ops-users] Warning of unstable nightly builds starting later
> today
>
> All,
>
> The new and improved client-side JavaScript code will probably be
> checked in later today, but there are still some known issues associated
> with it.
>
> Since this code is likely to break your app, we don't recommend getting
> nightlies while we work on fixing those issues.
>
> On the other hand committing this will encourage us to fix the remaining
> issues quickly!
>
> -Erik
>
> --
> Orbeon - XForms Everywhere:
> 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

--
Orbeon - XForms Everywhere:
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: Warning of unstable nightly builds starting later today

Administrator

In reply to this post by Erik Bruchez

All,

I won't try to claim that the new code is absolutely bug-free, but I
think we are back to acceptable level of stability. If you were using
nightly builds before, and still feel adventurous, this is your day to
give a try to a nightly build. If you notice any regression compared
to what we had last week (or of course any annoying bug), please let
us know.

http://forge.objectweb.org/nightlybuilds/ops/ops/

Alex

On 7/24/06, Erik Bruchez <[hidden email]> wrote:

> All,
>
> The new and improved client-side JavaScript code will probably be
> checked in later today, but there are still some known issues associated
> with it.
>
> Since this code is likely to break your app, we don't recommend getting
> nightlies while we work on fixing those issues.
>
> On the other hand committing this will encourage us to fix the remaining
> issues quickly!
>
> -Erik
>
> --
> Orbeon - XForms Everywhere:
> 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
>
>
>

--
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: Warning of unstable nightly builds starting later today

One problem I've noticed is that the calendar pops up for a readonly date input (although I have local changes which could be causing this...).

Looks like the logic in the old xforms-style.js xformsCalendarClick() function needs to be reflected in the new click handler in xforms.js which calls Calendar.setup().

Adrian

Alessandro Vernet wrote:

All,

I won't try to claim that the new code is absolutely bug-free, but I
think we are back to acceptable level of stability. If you were using
nightly builds before, and still feel adventurous, this is your day to
give a try to a nightly build. If you notice any regression compared
to what we had last week (or of course any annoying bug), please let
us know.

http://forge.objectweb.org/nightlybuilds/ops/ops/

Alex

On 7/24/06, Erik Bruchez [hidden email] wrote:

All,

The new and improved client-side JavaScript code will probably be
checked in later today, but there are still some known issues associated
with it.

Since this code is likely to break your app, we don't recommend getting
nightlies while we work on fixing those issues.

On the other hand committing this will encourage us to fix the remaining
issues quickly!

-Erik

--
Orbeon - XForms Everywhere:
http://www.orbeon.com/blog/

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: [hidden email]
For general help: [hidden email]
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: [hidden email]
For general help: [hidden email]
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
  

Adrian Baker-2

Re: Warning of unstable nightly builds starting later today

Another calendar related problem/question: it seems that the hint for a date input can't be activated - should the logic in the ORBEON.xforms.Events.focus() function be invoked when a user clicks on a date input?

Adrian Baker wrote:

One problem I've noticed is that the calendar pops up for a readonly date input (although I have local changes which could be causing this...).

Looks like the logic in the old xforms-style.js xformsCalendarClick() function needs to be reflected in the new click handler in xforms.js which calls Calendar.setup().

Adrian

Alessandro Vernet wrote:
All,

I won't try to claim that the new code is absolutely bug-free, but I
think we are back to acceptable level of stability. If you were using
nightly builds before, and still feel adventurous, this is your day to
give a try to a nightly build. If you notice any regression compared
to what we had last week (or of course any annoying bug), please let
us know.

http://forge.objectweb.org/nightlybuilds/ops/ops/

Alex

On 7/24/06, Erik Bruchez [hidden email] wrote:

All,

The new and improved client-side JavaScript code will probably be
checked in later today, but there are still some known issues associated
with it.

Since this code is likely to break your app, we don't recommend getting
nightlies while we work on fixing those issues.

On the other hand committing this will encourage us to fix the remaining
issues quickly!

-Erik

--
Orbeon - XForms Everywhere:
http://www.orbeon.com/blog/

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: [hidden email]
For general help: [hidden email]
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: [hidden email]
For general help: [hidden email]
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
  
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: [hidden email]
For general help: [hidden email]
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
  

assafn

Re: Re: Warning of unstable nightly builds starting later today

Hi,

I tried the 1/8/06 nightly build. Found a bug: all ! for validation are showing even for fields that are not relevant (the fields are not shown, only the red ! is shown)

assaf

--
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: Warning of unstable nightly builds starting later today

Administrator

Assaf,

I don't see this with the latest code. But yes it is still a little bit
in flux, although more and more issues are getting fixed :-)

-Erik

[hidden email] wrote:

> Hi,
>
> I tried the 1/8/06 nightly build. Found a bug: all ! for validation are showing even for fields that are not relevant (the fields are not shown, only the red ! is shown)
>
> assaf
>
>
>
> ------------------------------------------------------------------------
>
>
> --
> 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

Adrian Baker-2

Re: Warning of unstable nightly builds starting later today

In reply to this post by Alessandro Vernet

A futher issue: the xforms-invalid class correctly appears in the inital generated html, however it does not correctly get added/removed as a form is used (the corresponding alerts show/hide correctly though). Fix is to add this to the ORBEON.xforms.Controls.setValid function:

    if (isValid) {
        ORBEON.util.Dom.removeClass(control, "xforms-invalid");
    } else {
        ORBEON.util.Dom.addClass(control, "xforms-invalid");
    }

Adrian

Alessandro Vernet wrote:

All,

I won't try to claim that the new code is absolutely bug-free, but I
think we are back to acceptable level of stability. If you were using
nightly builds before, and still feel adventurous, this is your day to
give a try to a nightly build. If you notice any regression compared
to what we had last week (or of course any annoying bug), please let
us know.

http://forge.objectweb.org/nightlybuilds/ops/ops/

Alex

On 7/24/06, Erik Bruchez [hidden email] wrote:

All,

The new and improved client-side JavaScript code will probably be
checked in later today, but there are still some known issues associated
with it.

Since this code is likely to break your app, we don't recommend getting
nightlies while we work on fixing those issues.

On the other hand committing this will encourage us to fix the remaining
issues quickly!

-Erik

--
Orbeon - XForms Everywhere:
http://www.orbeon.com/blog/

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: [hidden email]
For general help: [hidden email]
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: [hidden email]
For general help: [hidden email]
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
  

Adrian Baker-2

Re: Warning of unstable nightly builds starting later today

In reply to this post by Adrian Baker-2

Just to confirm - this is a problem in the most recent nightly.

Adrian Baker wrote:

One problem I've noticed is that the calendar pops up for a readonly date input (although I have local changes which could be causing this...).

Looks like the logic in the old xforms-style.js xformsCalendarClick() function needs to be reflected in the new click handler in xforms.js which calls Calendar.setup().

Adrian

Alessandro Vernet wrote:
All,

I won't try to claim that the new code is absolutely bug-free, but I
think we are back to acceptable level of stability. If you were using
nightly builds before, and still feel adventurous, this is your day to
give a try to a nightly build. If you notice any regression compared
to what we had last week (or of course any annoying bug), please let
us know.

http://forge.objectweb.org/nightlybuilds/ops/ops/

Alex

On 7/24/06, Erik Bruchez [hidden email] wrote:

All,

The new and improved client-side JavaScript code will probably be
checked in later today, but there are still some known issues associated
with it.

Since this code is likely to break your app, we don't recommend getting
nightlies while we work on fixing those issues.

On the other hand committing this will encourage us to fix the remaining
issues quickly!

-Erik

--
Orbeon - XForms Everywhere:
http://www.orbeon.com/blog/

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: [hidden email]
For general help: [hidden email]
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: [hidden email]
For general help: [hidden email]
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
  
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: [hidden email]
For general help: [hidden email]
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
  

Alessandro Vernet

Re: Warning of unstable nightly builds starting later today

Administrator

In reply to this post by Adrian Baker-2

On 7/30/06, Adrian Baker <[hidden email]> wrote:
>
> One problem I've noticed is that the calendar pops up for a readonly date
> input (although I have local changes which could be causing this...).

Adrian, this one is fixed. Nice catch.

http://forge.objectweb.org/tracker/index.php?func=detail&aid=305891&group_id=168&atid=350207

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

Alessandro Vernet

Re: Warning of unstable nightly builds starting later today

Administrator

In reply to this post by Adrian Baker-2

On 7/31/06, Adrian Baker <[hidden email]> wrote:
> Another calendar related problem/question: it seems that the hint for a
> date input can't be activated - should the logic in the
> ORBEON.xforms.Events.focus() function be invoked when a user clicks on a
> date input?

Adrian, I don't think this is a regression, but it is now fixed.

http://forge.objectweb.org/tracker/index.php?func=detail&aid=305892&group_id=168&atid=350207

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

Alessandro Vernet

Re: Warning of unstable nightly builds starting later today

Administrator

In reply to this post by Adrian Baker-2

Adrian,

We don't use the class 'xforms-invalid' in our CSS, so we didn't
notice the problem. I have added your code to
ORBEON.xforms.Controls.setValid and checked that in.

Alex

On 8/1/06, Adrian Baker <[hidden email]> wrote:

>
> A futher issue: the xforms-invalid class correctly appears in the inital
> generated html, however it does not correctly get added/removed as a form is
> used (the corresponding alerts show/hide correctly though). Fix is to add
> this to the ORBEON.xforms.Controls.setValid function:
>
> if (isValid) {
> ORBEON.util.Dom.removeClass(control, "xforms-invalid");
> } else {
> ORBEON.util.Dom.addClass(control, "xforms-invalid");
> }
>
> Adrian
>
> Alessandro Vernet wrote:
> All,
>
> I won't try to claim that the new code is absolutely bug-free, but I
> think we are back to acceptable level of stability. If you were using
> nightly builds before, and still feel adventurous, this is your day to
> give a try to a nightly build. If you notice any regression compared
> to what we had last week (or of course any annoying bug), please let
> us know.
>
> http://forge.objectweb.org/nightlybuilds/ops/ops/
>
> Alex
>
> On 7/24/06, Erik Bruchez <[hidden email]> wrote:
>
> All,
>
> The new and improved client-side JavaScript code will probably be
> checked in later today, but there are still some known issues associated
> with it.
>
> Since this code is likely to break your app, we don't recommend getting
> nightlies while we work on fixing those issues.
>
> On the other hand committing this will encourage us to fix the remaining
> issues quickly!
>
> -Erik
>
> --
> Orbeon - XForms Everywhere:
> 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
>
>
>
>
>
>
> ________________________________
>
> -- 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
>
>
>

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

Adrian Baker-2

Re: Warning of unstable nightly builds starting later today

In reply to this post by Alessandro Vernet

Labels for hidden (non-relevant) dropdowns are displayed.

I guess this comes back to the old problem of xforms:select/select1 not having a wrapping span the way xforms:input does...

Adrian

Alessandro Vernet wrote:

All,

I won't try to claim that the new code is absolutely bug-free, but I
think we are back to acceptable level of stability. If you were using
nightly builds before, and still feel adventurous, this is your day to
give a try to a nightly build. If you notice any regression compared
to what we had last week (or of course any annoying bug), please let
us know.

http://forge.objectweb.org/nightlybuilds/ops/ops/

Alex

On 7/24/06, Erik Bruchez [hidden email] wrote:

All,

The new and improved client-side JavaScript code will probably be
checked in later today, but there are still some known issues associated
with it.

Since this code is likely to break your app, we don't recommend getting
nightlies while we work on fixing those issues.

On the other hand committing this will encourage us to fix the remaining
issues quickly!

-Erik

--
Orbeon - XForms Everywhere:
http://www.orbeon.com/blog/

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: [hidden email]
For general help: [hidden email]
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: [hidden email]
For general help: [hidden email]
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
  

Adrian Baker-2

Re: Warning of unstable nightly builds starting later today

In reply to this post by Alessandro Vernet

Javascript integration (http://www.orbeon.com/ops/doc/reference-xforms-ng#d2501990e4731) seems broken - setting the value of a control doesn't seem to result in the engine being notified of the new value.

Alessandro Vernet wrote:

All,

I won't try to claim that the new code is absolutely bug-free, but I
think we are back to acceptable level of stability. If you were using
nightly builds before, and still feel adventurous, this is your day to
give a try to a nightly build. If you notice any regression compared
to what we had last week (or of course any annoying bug), please let
us know.

http://forge.objectweb.org/nightlybuilds/ops/ops/

Alex

On 7/24/06, Erik Bruchez [hidden email] wrote:

All,

The new and improved client-side JavaScript code will probably be
checked in later today, but there are still some known issues associated
with it.

Since this code is likely to break your app, we don't recommend getting
nightlies while we work on fixing those issues.

On the other hand committing this will encourage us to fix the remaining
issues quickly!

-Erik

--
Orbeon - XForms Everywhere:
http://www.orbeon.com/blog/

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: [hidden email]
For general help: [hidden email]
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: [hidden email]
For general help: [hidden email]
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
  

Alessandro Vernet

Re: Warning of unstable nightly builds starting later today

Administrator

Adrian,

Yes, it is broken. And we are quite evil, because we did it on purpose
:). Before, the JavaScript code was notified by the browser that the
'value' property was changed because we were registering an event
handler on every input. This is quite expensive, so we don't do that
anymore. In the future you will need to call an API provided in
xforms.js to set the value. It could be:

ORBEON.xforms.Controls.setValue("control-id", newValue);

Any better suggestion?

Alex

On 8/6/06, Adrian Baker <[hidden email]> wrote:

>
> Javascript integration
> (http://www.orbeon.com/ops/doc/reference-xforms-ng#d2501990e4731)
> seems broken - setting the value of a control doesn't seem to result in the
> engine being notified of the new value.
>
> Alessandro Vernet wrote:
> All,
>
> I won't try to claim that the new code is absolutely bug-free, but I
> think we are back to acceptable level of stability. If you were using
> nightly builds before, and still feel adventurous, this is your day to
> give a try to a nightly build. If you notice any regression compared
> to what we had last week (or of course any annoying bug), please let
> us know.
>
> http://forge.objectweb.org/nightlybuilds/ops/ops/
>
> Alex
>
> On 7/24/06, Erik Bruchez <[hidden email]> wrote:
>
> All,
>
> The new and improved client-side JavaScript code will probably be
> checked in later today, but there are still some known issues associated
> with it.
>
> Since this code is likely to break your app, we don't recommend getting
> nightlies while we work on fixing those issues.
>
> On the other hand committing this will encourage us to fix the remaining
> issues quickly!
>
> -Erik
>
> --
> Orbeon - XForms Everywhere:
> 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
>
>
>
>
>
>
> ________________________________
>
> -- 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
>
>
>

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

Adrian Baker-2

Re: Warning of unstable nightly builds starting later today

Nope, using a function like this seems perfectly ok.

Alessandro Vernet wrote:

Adrian,

Yes, it is broken. And we are quite evil, because we did it on purpose
:). Before, the JavaScript code was notified by the browser that the
'value' property was changed because we were registering an event
handler on every input. This is quite expensive, so we don't do that
anymore. In the future you will need to call an API provided in
xforms.js to set the value. It could be:

ORBEON.xforms.Controls.setValue("control-id", newValue);

Any better suggestion?

Alex

On 8/6/06, Adrian Baker [hidden email] wrote:

Javascript integration
(http://www.orbeon.com/ops/doc/reference-xforms-ng#d2501990e4731)
seems broken - setting the value of a control doesn't seem to result in the
engine being notified of the new value.

Alessandro Vernet wrote:
All,

I won't try to claim that the new code is absolutely bug-free, but I
think we are back to acceptable level of stability. If you were using
nightly builds before, and still feel adventurous, this is your day to
give a try to a nightly build. If you notice any regression compared
to what we had last week (or of course any annoying bug), please let
us know.

http://forge.objectweb.org/nightlybuilds/ops/ops/

Alex

On 7/24/06, Erik Bruchez [hidden email] wrote:

All,

The new and improved client-side JavaScript code will probably be
checked in later today, but there are still some known issues associated
with it.

Since this code is likely to break your app, we don't recommend getting
nightlies while we work on fixing those issues.

On the other hand committing this will encourage us to fix the remaining
issues quickly!

-Erik

--
Orbeon - XForms Everywhere:
http://www.orbeon.com/blog/

--
You receive this message as a subscriber of the [hidden email]
mailing list.
To unsubscribe: [hidden email]
For general help: [hidden email]
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:
[hidden email] For general
help: [hidden email] 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: [hidden email]
For general help: [hidden email]
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: [hidden email]
For general help: [hidden email]
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
  

David McIntyre

setting a value and sending a submission

I'm trying to arrange for a trigger to perform an <xforms:setvalue>
action and then, provided the instance data is valid as a result of this
setvalue, send a submission.

With our previous version of OPS it was possible to do this using

<xforms:trigger id="mytrigger">
<xforms:label>Click me</xforms:label>
<xforms:setvalue ref="foo" value="../bar" ev:event="DOMActivate"/>
<xforms:send submission="mysubmission" ev:event="DOMActivate"/>
</xforms:trigger>

and setting validate="true" in the <xforms:submission>. However, this
approach is no longer working. It seems that the validation is always
based on the state of the instance data before the trigger was
activated, even though the data that is sent is the updated version.
I've tried various approaches, such as wrapping the setvalue and the
send in a single action and putting an explicit <xforms:revalidate/>
between the two:

<xforms:trigger id="mytrigger">
<xforms:label>Click me</xforms:label>
<xforms:action ev:event="DOMActivate">
<xforms:setvalue ref="foo" value="../bar"/>
<xforms:revalidate/>
<xforms:send submission="mysubmission"/>
</xforms:action>
</xforms:trigger>

However, if I leave validate="true" in the submission, then the
submission will not be sent (unless the instance data was valid before
the setvalue) and if I use validate="false" then the submission will be
sent even if the data is not valid after the setvalue.

Is there still a way to perform this double action?

Cheers,
Dave McIntyre

--
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: setting a value and sending a submission

Administrator

Hi Dave,

Doing a <xforms:refresh/> instead of <xforms:revalidate/> should work
for you. At least it worked for me in a small example I create trying
to reproduce this:

<xforms:action ev:event="DOMActivate">
<xforms:setvalue ref="/data">2</xforms:setvalue>
<xforms:refresh/>
<xforms:send submission="submission"/>
</xforms:action>

But I would have thought that <xforms:revalidate/> would have done the
trick as well. I'll let Erik confirm this.

Alex

On 8/9/06, Dave McIntyre <[hidden email]> wrote:

> I'm trying to arrange for a trigger to perform an <xforms:setvalue>
> action and then, provided the instance data is valid as a result of this
> setvalue, send a submission.
>
> With our previous version of OPS it was possible to do this using
>
> <xforms:trigger id="mytrigger">
> <xforms:label>Click me</xforms:label>
> <xforms:setvalue ref="foo" value="../bar" ev:event="DOMActivate"/>
> <xforms:send submission="mysubmission" ev:event="DOMActivate"/>
> </xforms:trigger>
>
> and setting validate="true" in the <xforms:submission>. However, this
> approach is no longer working. It seems that the validation is always
> based on the state of the instance data before the trigger was
> activated, even though the data that is sent is the updated version.
> I've tried various approaches, such as wrapping the setvalue and the
> send in a single action and putting an explicit <xforms:revalidate/>
> between the two:
>
> <xforms:trigger id="mytrigger">
> <xforms:label>Click me</xforms:label>
> <xforms:action ev:event="DOMActivate">
> <xforms:setvalue ref="foo" value="../bar"/>
> <xforms:revalidate/>
> <xforms:send submission="mysubmission"/>
> </xforms:action>
> </xforms:trigger>
>
> However, if I leave validate="true" in the submission, then the
> submission will not be sent (unless the instance data was valid before
> the setvalue) and if I use validate="false" then the submission will be
> sent even if the data is not valid after the setvalue.
>
> Is there still a way to perform this double action?
>
> Cheers,
> Dave McIntyre
>
>
>
>
>
>
> --
> 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