You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Barzilai Spinak <ba...@internet.com.uy> on 2003/09/10 07:28:57 UTC
JXForms and selectBoolean
Hello Christopher.
A couple of days ago I posted a question related to JXForms and nobody
answered.
By looking into the CVS submissions, I think you may be one of the
programmers related to that block.
Am I right? Can you help me with my question?
Another programmer seems to be cziegeler but I think he's on vacation
or something.
Who would be the right person to ask?
Here's a reference to it.
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=106309010927746&w=2
Thanks for your help
BarZ
ADSL para estar en internet las 24 horas a máxima velocidad
y sin ocupar el teléfono.
-----------------------------------------------------------
http://www.internet.com.uy Tel. 707.42.52
Re: What are you using for form handling?
Posted by Sylvain Wallez <sy...@anyware-tech.com>.
Barzilai Spinak wrote:
> "On how to hit a moving target" by Barcho
>
> Hi, I'd like to know what people are really using for form handling.
>
> Abstract:
> We were in the middle of a project using XMLForms and it was killed,
> so we started porting to JXForms which was still-born (see below).
> Woody is in a fetal state and a port to Woody is not so trivial as
> XMLForms --> JXForms.
> What should real people with real projects do?
I use Woody on a real project. But this should be considered as a
particular case, as I add new features to Woody as part of this project,
which helps it maturing quickly.
<snip/>
> And then we have Woody which seems to be the loved child at the
> moment. But how usable is it? I haven't looked at it. I may give it a
> chance if someone tells me "XMLForms is dead, long live JXForms is
> dead, long live Woody!!"
I tell you that XMLForm is dead, JXForms is nearly dead (it's basically
the same as XMLForm except that the transformer has been rewritten), and
long live Woody!! Now you can go ahead and look at the samples ;-)
Read more about the reasons for this at
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=105881304808076&w=2
> We should have *at least one* forms framework that works.
This is and will be Woody.
It is already more featured than XMLForm/JXForms, except that it
currently doesn't support wizards, and that some changes are likely to
occur in its API. Not radical changes, but changes that require some
minor work in existing code. You should be clearly warned of this before
making a choice, but it's definitely the Cocoon from framework that will
last.
Sylvain
--
Sylvain Wallez Anyware Technologies
http://www.apache.org/~sylvain http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
Orixo, the opensource XML business alliance - http://www.orixo.com
What are you using for form handling?
Posted by Barzilai Spinak <ba...@internet.com.uy>.
"On how to hit a moving target" by Barcho
Hi, I'd like to know what people are really using for form handling.
Abstract:
We were in the middle of a project using XMLForms and it was killed, so
we started porting to JXForms which was
still-born (see below). Woody is in a fetal state and a port to Woody is
not so trivial as XMLForms --> JXForms.
What should real people with real projects do?
We had an (apparently) working framework which was XMLForms and a couple
of months ago it was deprecated in favor
of JXForms. All this happened with minor discussion (at least on the dev
list for which I've been reading all messages).
All this would be very fine if JXForms actually worked. Lately there
have been a few messages by me and others
concerning problems with JXforms: (for example)
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23452
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=106309010927746&w=2
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=105794535504709&w=2
It all started with the lack of an equivalent to xf:selectBoolean but
now I've realized that -- at least -- chekcbox handling
is *broken* when all the related checkboxes in a form are unchecked.
Go ahead and try it!! Go to the /cocoon/samples/jxforms/wizard/ and
try to uncheck ALL "hobbies", or ALL "professional roles"
Now go back with the "Prev" button and you'll see them still checked.
This is not a problem with the wizard sample, but rather
a problem in JXForms not handling "expected" but "not submitted"
parameters like XMLForms used to do.
So far I have found a "we-dont-talk-about-that-in-here" attitude with
respect to the whole subject.
And then we have Woody which seems to be theloved child at the moment.
But how usable is it? I haven't looked at it.
I may give it a chance if someone tells me "XMLForms is dead, long live
JXForms is dead, long live Woody!!"
We should have *at least one* forms framework that works.
BarZ
http://www.internet.com.uy Tel. 707.42.52
---------------------------------------------------
TODAS LAS FORMAS DE ACCESO TODOS LOS SERVICIOS
* ADSL/ADSL Plus/ADSL Class - Todas las velocidades
* Accesos por Modem 56K - Tarifa Plana o por minuto
* Desarrollo - Web - Redes - Intra/Extranets - VPNs
* E-mail - Antivirus - Forwards - Alias - Roaming
Re: JXForms and selectBoolean
Posted by Christopher Oliver <re...@verizon.net>.
Barzilai Spinak wrote:
> Christopher Oliver wrote:
> > BarZ,
> >
> > Feel free to submit patches to JXForms, for example for
> "selectBoolean". Nobody is "responsible" for JXForms or other Cocoon
> development per se. It's voluntary.
>
> Well, thanks for your confidence hehe.
> I may do just that when I feel more compfortable with the code. In
> fact I have a few ideas.
> But before doing that I wanted to know for example what the philosphy
> behind the JXForms project is, or if
> someone is already planning to do something about it.
> Sometimes, when I find problems in other people's code/API's, I fear
> that it may be me who "just don't get it".
There's only one way to find out - by showing them your code.
>
> Also, although it's an open source project and anyone can contribute,
> there's generally one or
> two people who do most of the work on a certain part (JXForms in this
> case). They are usually
> the ones who started the subproject, with some idea and vision in
> mind, and generally have the final word
> on whether a new submitted patch is going to be implemented.
Not so, IMO. There should be no code or idea ownership in open source.
Once you've contributed your ideas or code it belongs to the community
and others can change it..
> At least they have CVS permission
> to do it which is not my case!! :-)
You can submit patches to Cocoon via bugzilla even if you're not a
committer.
>
> If I start adding my <xf:BarZRules> tags and you add <xf:OliverRocks>
> tags and so on, pretty soon the
> project becomes a mess.
>
> So are you this special JXForms someone?
No. For JXForms (or any project) to be truly successful, there should be
no such person.
> And what did you think about my questions?
> Am I on the right path or did I just "not get the whole idea"? :-)
Your assessment of the need for selectBoolean sounds right on track to me.
Regards,
Chris
Re: JXForms and selectBoolean
Posted by Christopher Oliver <re...@verizon.net>.
BarZ,
Feel free to submit patches to JXForms, for example for "selectBoolean".
Nobody is "responsible" for JXForms or other Cocoon development per se.
It's voluntary.
Regards,
Chris
Barzilai Spinak wrote:
> Hello Christopher.
> A couple of days ago I posted a question related to JXForms and nobody
> answered.
> By looking into the CVS submissions, I think you may be one of the
> programmers related to that block.
> Am I right? Can you help me with my question?
> Another programmer seems to be cziegeler but I think he's on vacation
> or something.
> Who would be the right person to ask?
>
> Here's a reference to it.
>
>
> http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=106309010927746&w=2
>
>
> Thanks for your help
>
> BarZ
>
>
> ADSL para estar en internet las 24 horas a máxima velocidad
> y sin ocupar el teléfono.
> -----------------------------------------------------------
> http://www.internet.com.uy Tel. 707.42.52
>
>