Orbeon Forms community mailing list

Future of Orbeon datatable

Classic

List

Threaded

3 messages Options

Heinrich Götzger

Future of Orbeon datatable

Salute,

as described in:
http://wiki.orbeon.com/forms/doc/developer-guide/xbl-components/datatable

the orbeon-datatable are an expiring function from now on.

Unfortunately we use them in quite many forms(35-40, and more to come)
and they fill approx. 50% of our needs.
We like i.e. the ability to sort or the paging, and last but not least,
they look pretty good.

Since they weren't supported in form-builder, we did not use any
form-builder function at all. Because our forms get delivered to several
sites, and form-builder is not able to save forms in the file system at
all, this wasn't a problem. All our forms are handmade :-)

In these days we start planning the migration from 3.9 to 4.x. Therefore
this is a serious issue for us.

So will there be any replacement?
What's your recommendation?

Thank you for sharing your plans and thought.

Cheers

Heinrich

--
Before printing this e-mail, think about our environmental responsibility.

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].

JeffL

Re: Future of Orbeon datatable

We also use the orbeon-datatable in a large amount of forms.

In 4.x we found some issues that occurred with the use of Datatables in dialogs and found a workaround. (See

Closing a xxforms:dialog which contains a xbl datatable generates an unknown error on Stackoverflow).

Also there were errors generated which we traced to xforms.js. Below is the mod that we applied which solved the error. It is not elegant, as we trap the error and ignore it.

setHintMessage: function(control, message) {

// Destroy existing tooltip if it was for a control which isn't anymore in the DOM

var tooltips = ORBEON.xforms.Globals.hintTooltipForControl;

if (tooltips[control.id] != null) {

try { // to ignore an error JL 2013

if (tooltips[control.id].cfg.getProperty('context')[0] != control)

tooltips[control.id] = null

} catch (e) {

}

//if (tooltips[control.id].cfg.getProperty('context')[0] != control) // current code

// tooltips[control.id] = null

}

if (YAHOO.util.Dom.hasClass(control, "xforms-trigger") || YAHOO.util.Dom.hasClass(control, "xforms-submit")) {

// For triggers, the value is stored in the title for the control

if (tooltips[control.id] == null) {

// We only update the title if we don't have already a YUI hint widget.

// If we do, updating the value in the YUI widget is enough. The YUI widget empties the content of the

// title attribute to avoid the text in the title from showing. If we set the title, we might have

// both the title shown by the browser and the YUI hint widget.

var formElement = ORBEON.util.Dom.getElementByTagName(control, ["a", "button"]);

formElement.title = message;

}

} else {

ORBEON.xforms.Controls._setMessage(control, "hint", message);

}

// If there is already a YUI hint created for that control, update the message for the YUI widget

ORBEON.xforms.Controls._setTooltipMessage(control, message, tooltips);

Regards

Jeff

On 25/06/2013, at 1:44 AM, Heinrich Götzger wrote:

Salute,

as described in:
http://wiki.orbeon.com/forms/doc/developer-guide/xbl-components/datatable

the orbeon-datatable are an expiring function from now on.

Unfortunately we use them in quite many forms(35-40, and more to come) and they fill approx. 50% of our needs.
We like i.e. the ability to sort or the paging, and last but not least, they look pretty good.

Since they weren't supported in form-builder, we did not use any form-builder function at all. Because our forms get delivered to several sites, and form-builder is not able to save forms in the file system at all, this wasn't a problem. All our forms are handmade :-)

In these days we start planning the migration from 3.9 to 4.x. Therefore this is a serious issue for us.

So will there be any replacement?
What's your recommendation?

Thank you for sharing your plans and thought.

Cheers

Heinrich

--
Before printing this e-mail, think about our environmental responsibility.

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].

--
You received this message because you are subscribed to the Google Groups "Orbeon Forms" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].

Alessandro Vernet

Re: Future of Orbeon datatable

Administrator

In reply to this post by Heinrich Götzger

Hi Heinrich,

The datatable is still there in versions 4.x, and is unchanged. We have no specific plans to remove this code, especially if we know people like you are still using it, but we don't have plans to improve on it either.

A possible evolution path would be to build on the fr:grid (used by Form Builder, and also able to handle repeats at runtime) and combine that with what we have in Form Runner summary pages (paging, integration with a service that returns the data), but again, there are no set plans to do this right now.

So for now, feel free to continue using the datatable, and if you need fixes or improvements, and rare able to do those yourself, I'd encourage you to contribute them. (This is true for every functionality, but even more so for the datatable since are not actively working on it.)

Alex

--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet