Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Remote Application Platform (RAP) » Upgrading to qooxdoo 8.2 anytime soon?
Upgrading to qooxdoo 8.2 anytime soon? [message #127853] Mon, 13 April 2009 23:29 Go to next message
Howard is currently offline HowardFriend
Messages: 29
Registered: July 2009
Junior Member
Any time frames on this?
Getting ticket 215015 resolved would be awesome.

Keep up the awesome work!
Howard
Re: Upgrading to qooxdoo 8.2 anytime soon? [message #127879 is a reply to message #127853] Tue, 14 April 2009 08:40 Go to previous messageGo to next message
Ralf Sternberg is currently offline Ralf SternbergFriend
Messages: 1313
Registered: July 2009
Senior Member

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 #127901 is a reply to message #127879] Tue, 14 April 2009 09:02 Go to previous messageGo to next message
Rüdiger Herrmann is currently offline Rüdiger HerrmannFriend
Messages: 581
Registered: July 2009
Senior Member
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 #127954 is a reply to message #127901] Tue, 14 April 2009 17:44 Go to previous messageGo to next message
Howard is currently offline HowardFriend
Messages: 29
Registered: July 2009
Junior Member
Yup, didn't think that was happening...thought I'd ask though. :)

Unfortunately CTabFolder allows changing the order of tabs, which is an
undesired behavior for my app. But maybe I can convince the PM on the
quick fix.

I may have to go with the custom tab built with buttons style...which is
what I would prefer to do but it'll probably take longer than I can
afford. Curious though, is there a way to lazy load/build the non-selected
tab instead of having to build them all at the same time?

Thanks for the suggestions.
Re: Upgrading to qooxdoo 8.2 anytime soon? [message #127977 is a reply to message #127954] Tue, 14 April 2009 20:31 Go to previous messageGo to next message
Ralf Sternberg is currently offline Ralf SternbergFriend
Messages: 1313
Registered: July 2009
Senior Member

Hi,

Howard wrote:
> Yup, didn't think that was happening...thought I'd ask though. :)
>
> Unfortunately CTabFolder allows changing the order of tabs, which is an
> undesired behavior for my app. But maybe I can convince the PM on the
> quick fix.

Did you try to set CTabFolder#setMRUVisible() -> false? In this mode,
the order of the items is not changed.

> I may have to go with the custom tab built with buttons style...which is
> what I would prefer to do but it'll probably take longer than I can
> afford. Curious though, is there a way to lazy load/build the
> non-selected tab instead of having to build them all at the same time?

You can create the item's contents lazily in a SelectionListener on the
CTabFolder. Actually, this is what we do in our ControlsDemo:

topFolder.addSelectionListener( new SelectionAdapter() {
public void widgetSelected( final SelectionEvent evt ) {
int index = topFolder.getSelectionIndex();
tabs[ index ].createContents();
}
} );

The createContents() method creates the item contents if they aren't yet
created.


Hope this helps,
Ralf
Re: Upgrading to qooxdoo 8.2 anytime soon? [message #128047 is a reply to message #127977] Wed, 15 April 2009 16:42 Go to previous messageGo to next message
Stefan Hansel is currently offline Stefan HanselFriend
Messages: 103
Registered: July 2009
Senior Member
>> You can create the item's contents lazily in a SelectionListener on the
>> CTabFolder.

We even use this to lazily unload contents of unselected tabs to safe
quite a lot of memory on the serverside.
Re: Upgrading to qooxdoo 8.2 anytime soon? [message #128288 is a reply to message #128047] Thu, 16 April 2009 17:34 Go to previous messageGo to next message
Howard is currently offline HowardFriend
Messages: 29
Registered: July 2009
Junior Member
Duh, the selectionListener on the TabFolder, not the tabs!

Good stuff...I definitely need to look into this when I get the time. Is
the lazy unloading also part of the Controls Demo?
Re: Upgrading to qooxdoo 8.2 anytime soon? [message #128366 is a reply to message #128288] Thu, 16 April 2009 20:28 Go to previous messageGo to next message
Ralf Sternberg is currently offline Ralf SternbergFriend
Messages: 1313
Registered: July 2009
Senior Member

Howard wrote:
> Duh, the selectionListener on the TabFolder, not the tabs!
>
> Good stuff...I definitely need to look into this when I get the time.
> Is the lazy unloading also part of the Controls Demo?

No. The controls demo does not unload contents.

Ralf
Re: Upgrading to qooxdoo 8.2 anytime soon? [message #128575 is a reply to message #128288] Mon, 20 April 2009 07:54 Go to previous message
Stefan Hansel is currently offline Stefan HanselFriend
Messages: 103
Registered: July 2009
Senior Member
>> 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.
Previous Topic:extension point org.eclipse.core.runtime.preferences not excution.
Next Topic:How to restart a rap-session?
Goto Forum:
  


Current Time: Sun Nov 28 03:37:18 GMT 2021

Powered by FUDForum. Page generated in 0.02452 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top