orbeon migration problems

Hello guys,

I'm pretty new about orbeon because before I was using betterform, but I'm not happy about their product so I would like to understand if it's easy for me migrate or not
It's a decision that I should take the next week so if you are so kind to support me I' ll thank you. Here my main questions regarding my migration:

1) Rich Components.

In betterform I was using DOJO both to translate the xform component and to put some graphic future to my UI. Now what I have understood with xform you use YUI, so for the translation of the component it's not important if I use DOJO or YUI, but to improve the UI putting Tabs or collapse elements for example How can I do that? . I saw that in Orbeon are automatically imported the fr components and I have used it to build my tabview structure, but for example to collapse some part of the forms (divided in section) I didnt' find any solution, I have tried to use the fr accordion but without success. So I want to ask in general if I can use just the fr component or there are other component that can help me??


2) SUBMISSION

I have a form with list elements, imagine that we have a library and a user wants to insert new information regarding a book and save it in a list. Before after that the user filled the book form and click on "save book" I was able to validate just the information relative in the book because in betterform there is a submission with action="echo" that for me it's just a way to trigger the validation on the template of the book before to add this data in the main template that I'm going to submit with the main save of the form.
Is there a similar way in Orbeon that could be useful for me?

3)Switch/case

At first glance it seems that switch  / case structure is not working in orbeon while it was working on betterform you kno why and if there is a workaround for it?


Sorry for the questions but I think that could be a good opportunity also for you to be integrated in our application, I hope to open a sort of collaboration.

Thank you
Frank Mayers


--
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
OW2 mailing lists service home page: http://www.ow2.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
OW2 mailing lists service home page: http://www.ow2.org/wws

Frank,

It seems that we missed your message. We have quite a backlog in the
mailing-list unfortunately, and the US holidays haven't helped :(
Still, I attempt some answer below.
Orbeon Forms includes a set of fairly rich components, see:

http://wiki.orbeon.com/forms/doc/developer-guide/xbl-components

If what you need is not there, you can create your own, see:

http://wiki.orbeon.com/forms/doc/developer-guide/xbl-components-guide
In 3.9 and earlier, there is an undocumented "test:" scheme you can use, e.g.:

action="test:" or resource="test:"

In recent builds this is also called "echo:".

> 3)Switch/case
>
> At first glance it seems that switch  / case structure is not working in
> orbeon while it was working on betterform you kno why and if there is a
> workaround for it?

switch/case should work as expected.

> Sorry for the questions but I think that could be a good opportunity also
> for you to be integrated in our application, I hope to open a sort of
> collaboration.

I hope this helps,

-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
OW2 mailing lists service home page: http://www.ow2.org/wws