The datatable doesn't work under tabview using Orbeon 4.10

Hi, Alex,

I found a bug when upgrading my orbeon form from 3.9 to 4.10 version. In the attachment sample case, I made two tabs and two datatables, the datable can be loaded in tab 1 but did't show in tab 2 under 4.10 version (the datatable just can be loaded in either of two tabs)while everything works well in the Orbeon 3.9.
controller.xhtml

Hoi Henry821,

we probably had similar problems copying datatable from 4.4 to 4.5 last
summer.

It may be the case, that the table is not rendering correctly after
tab-switch, try to resize the client after selecting tab2, does it make
a difference?

Finally, take a look at :

http://stackoverflow.com/questions/23022098/recommended-alternative-for-frdatatable-in-orbeon-xforms-version-4-5

All the best, cheers

Heinrich

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

Hoi Henry821,

we probably had similar problems copying datatable from 4.4 to 4.5 last
summer.

It may be the case, that the table is not rendering correctly after
tab-switch, try to resize the client after selecting tab2, does it make
a difference?

Finally, take a look at :

http://stackoverflow.com/questions/23022098/recommended-alternative-for-frdatatable-in-orbeon-xforms-version-4-5

All the best, cheers

Heinrich

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

Hello,Heinrich,


Resizing the client indeed works.However, Do you have any better solution to fix this bug?


Regards,
Henry

Hoi Henry,

well, resizing the client is more a workaround then a fix IMHO ;) But it
shows where and how the problem might be solved.

Our solution is still not the best, but works more or less. Actually
it's very sad and I'm still not very happy with it. Probably we need a
complete redesign of our solution or a replacement, but haven't found
any yet. We need sorting and paging and so the opportunities are rare.

We put the datatable in own xbl-components since we use them in almost
every form and want a simple interface for all the stuff in and around
this table.

Basically we dispatch an event on DOMActivate to trigger the resize and
repaint algorithm of all visible YAHOO tables. And we register these
resize-methods on window.onresize and on document.body.onload.
This works more or less. We still bothering with changing of the
column-width and sometimes it's not so looking good after a tab-switch.
There we get a remaining Loading-Indicator sometimes which I couldn't
kill yet. And it's different in all clients.


I hope this helps a bit, let me know which way you're choosing.


Cheers

Heinrich

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

Hoi Henry,

well, resizing the client is more a workaround then a fix IMHO ;) But it
shows where and how the problem might be solved.

Our solution is still not the best, but works more or less. Actually
it's very sad and I'm still not very happy with it. Probably we need a
complete redesign of our solution or a replacement, but haven't found
any yet. We need sorting and paging and so the opportunities are rare.

We put the datatable in own xbl-components since we use them in almost
every form and want a simple interface for all the stuff in and around
this table.

Basically we dispatch an event on DOMActivate to trigger the resize and
repaint algorithm of all visible YAHOO tables. And we register these
resize-methods on window.onresize and on document.body.onload.
This works more or less. We still bothering with changing of the
column-width and sometimes it's not so looking good after a tab-switch.
There we get a remaining Loading-Indicator sometimes which I couldn't
kill yet. And it's different in all clients.


I hope this helps a bit, let me know which way you're choosing.


Cheers

Heinrich

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

Henry,

The datatable is no longer supported. I realize that this is to several users' chagrin, but we couldn't afford to maintain it. In fact, we say that it is entirely removed from Orbeon Forms 4.5, so I am not sure how it can work even a little in 4.10! See the release notes here:

    http://blog.orbeon.com/2014/04/orbeon-forms-45.html

-Erik

The datatable works perfectly in 4.10 in all our cases, except when in a
tabview - and even then, the first tab is always ok - problem stems from
switching tabs.

I think the problem is actually related to a bug in tabview with
fr-toggle, which I posted to this list about on Nov 27th.

-Bob

On 12/09/2015 01:20 PM, Erik Bruchez wrote:
--
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].

To clarify: this is by re-adding the datatable component to 4.10, is this right?

Regards,

-Erik

Hi, Erik,

That's right. We used the first solution from http://stackoverflow.com/questions/23022098/recommended-alternative-for-frdatatable-in-orbeon-xforms-version-4-5. The datatable work perfectly in our case.

Regards,
Henry

Thanks for confirming! -Erik

Hi,Eric,


So,Do you have any solution to solve this bug?  


Regards,
Henry

Henry,

No, we don't, I am sorry to say.

I am pretty sure it's possible to figure it out, but it's a completely unsupported feature at this point and my guess is that it would take us many hours to dig back into it and get somewhere. You can look into it, of course, and if you have any questions/issues feel free to ask them here.

-Erik