any tips on building mobile xforms?

I've been searching for an orbeon tutorial on how to build mobile <--> orbeon server interface.

e.g. ...

- does Form Builder have different templates/tools allowing xforms to be defined within canvas constraints of mobile devices?

- can a mobile device emulator be used to test the interaction?

I've looked at some mobile implementations here ..

http://www.w3.org/community/xformsusers/wiki/XForms_Implementations#Active_Implementations

but would like to understand the orbeon approach for gathering xform data from mobile users.

DL,

> - does Form Builder have different templates/tools allowing xforms to be
> defined within canvas constraints of mobile devices?

Not yet, and at this point you have to roll your own theme to get
there. Forms produced by Form Builder already run on mobile. They just
don't run in an optimal way from a layout perspective.

> - can a mobile device emulator be used to test the interaction?

Sure. You can use the iOS Simulator to view the forms, for example.

> I've looked at some mobile implementations here ..
>
> http://www.w3.org/community/xformsusers/wiki/XForms_Implementations#Active_Implementations
>
> but would like to understand the orbeon approach for gathering xform data
> from mobile users.

We have already started doing a bit of work to support Twitter
Bootstrap (http://twitter.github.com/bootstrap/). That is a step that
should certainly help. We definitely intend to work more on mobile
support.

-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

Good Morning,

just to share some tips.

> - does Form Builder have different templates/tools allowing xforms to be
> defined within canvas constraints of mobile devices?

We run our forms on desktop and on mobile (or smart) devices.
We decided to create a separate set of forms within a new app-folder.
Right now our FilterServlet detects the kind of the device and in case
of a smart device it redirects the request to the smart device forms if
the user is allowed to use them.

But we think to switch the decision of smart device or not from the
servlet to a Java-Processor to have it completely in the gui. (and avoid
the redirection of the request)

The smart device forms differ completely in layout from the desktop
forms due to the restricted space (and user requirements, in our
environment mobile user have different needs then desktop users).

There is a difference in rendering some widgets (i.e. buttons) on
different smart devices or tablets.

> - can a mobile device emulator be used to test the interaction?

Using operamobile as emulator helps a lot.
And changing the property 'general.useragent.override' in firefox to a
smart device string helped to develop and test the forms very well,
using firebug for detail checking is very helpful as well .....

Cheers

Heinrich


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