|
|
Re: Upgrading to qooxdoo 8.2 anytime soon? [message #127901 is a reply to message #127879] |
Tue, 14 April 2009 05:02   |
Eclipse User |
|
|
|
To work around the missing TabFolder overflow, you could consider
using the CTabFolder that has this functionality.
Alternatively, implementing a TabFolder-like widget out of Buttons
and a custom layout shouldn't take too long either.
HTH
Rüdiger
Ralf Sternberg wrote:
> Howard,
>
>> Any time frames on this?
>> Getting ticket 215015 resolved would be awesome.
>
> I'm sorry, but this is impossible before the 1.2 release. After this,
> we'll have to decide how to proceed with qx. However, do to massive API
> changes on the qx side, upgrading to 8.x will take several months.
>
> And as we didn't get many requests for the TabFolder, it's rather low on
> our priority list. Again, sorry.
>
>> Keep up the awesome work!
>
> Thanks! Ralf
|
|
|
|
|
|
|
|
Re: Upgrading to qooxdoo 8.2 anytime soon? [message #128575 is a reply to message #128288] |
Mon, 20 April 2009 03:54  |
Eclipse User |
|
|
|
>> Is the lazy unloading also part of the Controls Demo?
No, it's not.
But basically you are just disposing the content of the CTabItem.
(Control c=unselectedTabItem.getControl();
unselectedTabItem.setControl(null); c.dispose())
What makes this a bit more complicated (and application specific) is, that
you typically should safe the state of the shown widgets.
For instance we have vertical tabs in each view, and we save the selected
vertical tab (and sometimes even the selected rows of a table within the
selected vertical tab).
If we didn't do that, our users would be confused, as for them it would
look like changing contents.
|
|
|
Powered by
FUDForum. Page generated in 0.09149 seconds