Getting closer to XForms (was: extending XMLForms for different kinds of models...opinions?)

[Konstantin Piroumian <kp...@apache.org>]

Hi!

Just to add my <i18n:currency value="0.02"/>.

Having the model declaration in the sitemap is not a very good idea IMHO. In
a real application there are a lot of forms and each one has its own model.
Having all these declared in the sitemap would make a hybrid monster from
it.

What would be more natural (all IMHO) is to extend the XMLForm markup to
contain a reference to the used model. In XForms you can declare the model
in a form of an XML Schema inline or use 'src' attribute to load it from an
external location. And this is where the 'java:/' or 'javabean:/' prefixed
protocol could be used with no harm.

For more details on the markup please take a look at the W3C XForms page.

Regards,
  Konstantin


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org

Re: Getting closer to XForms (was: extending XMLForms for different kinds of models...opinions?)

[Josema Alonso <jo...@simbiosystems.com>]

Hello, Konstantin.

> ...
> Having the model declaration in the sitemap is not a very good idea IMHO.
In
> a real application there are a lot of forms and each one has its own
model.
> Having all these declared in the sitemap would make a hybrid monster from
> it.
> ...
I agree. The solution proposed was just to extending the functionality
quickly and for a limited period of time.
I discussed with Ivelin about having lots of forms and we agreed on solving
this first and start a thread abut the other problem later. Unfortunately I
had no time and did not do it as I should. I'm sorry.

Someone pointed a while back about coding a ActionDispatcher. So you would
only called that Action and it would return the apropriate Action for the
requested form. Since that was a hard task for me not knwing Avalon that
much I didn't try.
Now I see I don't like much, because that would not solve the problem with
the model either.


> What would be more natural (all IMHO) is to extend the XMLForm markup to
> contain a reference to the used model. In XForms you can declare the model
> in a form of an XML Schema inline or use 'src' attribute to load it from
an
> external location. And this is where the 'java:/' or 'javabean:/' prefixed
> protocol could be used with no harm.
Maybe...
But I think we're touching a different subject here than the extension I
proposed, but I feel it's better and more powerful.
I'm really impressed with the Flow approach in:
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=104561050902361&w=2
I should really look into this feature. Any docs about it?

> For more details on the markup please take a look at the W3C XForms page.
I'll do. In fact, I only read it briefly. I hope I'll have some time to read
it carefully.

Thanks.



---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org