Hi guys,
Is it possible to use add a calendar input in the XForm editor because those in the Absence Demo are cool.

Thanks.

Hi,

The calendar widget should appear automatically when you set a type to be xs:date. However there is a bug currently that will be fixed down the road.
The workaround is to add the following in the xform generated:

Code: :

type="xs:date"

on the xforms:bind element.

For instance:

Code: :

<xforms:bind nodeset="instance('taskoutput')/fe:request/fe:details/fe:request/fe:from" type="xs:date"/>

I hope this helps,

Arnaud

The difficulty is, as soon as you add this in the code, other changes using form editor regen the form and you lose the code changes. So, forget using form editor after that point.

We could add a check box in the Form Editor when a textinput control has its type property set to Date, so that we would put the date picker automatically (by adding the xforms code mentionned by Arnaud).
If you think this would be a nice feature, please add this feature request on our Demand Driven Development page.

The Form Editor is meant to help building a UI in XForms. It cannot read all types of XForms one can build, so indeed, if you change the generated code, most likely the Form Editor will not be able to reopen it. The Form Editor covers more and more of what one can do with XForms, but still far from everything. IF you need to do more than what it can generate, you can start from the code it generates, but you have to know XForms and can't use the Form Editor from there. It still saves a lot of work compared to writing XForms from scratch for every form, doesn't it?

We fixed that last week, and it will be included in the next release.

Antoine

Here's the difficulty - the forms editor is VERY primitive. If we want to realize the benefits of using the Intalio modeler/designer as advertised - that is, being able to model business process and go through to bpel generation and executiion without having to be a coder - and we really, really want to - then the form editor will need significant enhancement.

Right now I'm wrestling with a PIPA form and it looks like I can't do things such as the following without becoming an xforms coder and - at the same time - forgoing use of the forms editor:

- Button functionality to start processes
- Setting fonts and sizes, colors
- Real-time data validation against databases
- Populating pick-lists, drop-downs, and such from database tables BEFORE the form is served up in a PIPA process
- Setting select and text field default values
- Calendar pop-ups, including with control over how the resulting date is inserted back on form
- Control over Tab key sequence through the form
- Populating tables, grids

I could go on.

Please understand, I DO see how some of these can be forced through steps in an active process that can precede sending the form to the user via a create/complete cycle.

But if you had the capability to handle these in a PIPA cycle initiating a process, and the ability to set these up via the form editor, what a tremendous improvement this would be!

The magic of your product is the potential it holds to NOT have to be a code jockey!

You can model a process and go to BPEL generation without any coding. This has nothing to do with writing UI.

You don't have to use the form editor if you don't like it. You can use any other tool and write code for the UI, and then integrate it with your processes. The Form Editor may be used if you want to go beyond process modeling and process execution to cover the UI as well. But you can still use other technologies (PHP, JSP, .NET, etc), and we provide several examples that show how to do this. If you want to use XForms and you don't want to code too much XForms by hand, maybe the Form Editor can help. That's its purpose. Nothing more. Of course, we want to extend the XForms coverage, as we have been doing since the first release of the Form Editor.

It would great if you could submit new feature requests on the Demand Driven Development page (for each of the topics you listed here, and more, as you will). This is what the Demand Driven Development page is for. And that is how we improve the product so that you have less and less code to write, for business processes and beyond.

Hi Arnaud
I try this in my XForms but there is no calendar widget to be seen! I add xs:date but no result!!

Anything else that I not think about! Your help is appreciated

Works for me! (Version 5.0.0 Beta of Designer)
I just added an input control to the people activity form and set the type to xs:date in the validation, schema type property.Here is the project
By default, the result is a small calendar icon initially with an exclamation point to the left indicating that the control value has not been initialised. Click on the calendar icon and you will see the date picker where you can select a date which will replace the exclamation point , formatted as Tuesday December 11, 2007

Note that the presentation form of the date widget/picker is defined by the Orbeon implementation of the XFORMS standard. Orbeon describes how to customise this here

This should no longer be a problem.
Would you please attach your project ?
Regards
Ihab

I could see calendar widget on my own effort but this is what I am able to see:

A calendar widget with no input control by side of it. And when some date is select from widget result is like: Wednesday, December 13, 2007.

Default behaviour I might like to see is atleast that value pasted into the input control.

Are you guys able to see an input control with value of date pasted into it?

thanks in advance
Muhilan

Hi guys ,

xs:date how can we put it in french*.



THANKS