Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Nebula » CompositeTable and item groups...
CompositeTable and item groups... [message #31660] Tue, 13 March 2007 10:18 Go to next message
Roland Tepp is currently offline Roland TeppFriend
Messages: 336
Registered: July 2009
Senior Member
Hello,

I have a scenario where I have to show two (rather long) listings above
one another.

These lists (as drawn by our UI designer) would be perfect fit for using
CompositeTable, but I would really like to avoid having more than one
scrollbar on the screen and maximize the vertical visible count of the
listed items as I have to work with rather limited screen-estate
(touch-screen with 800x600).

I was wandering if CompositeTable can have some sort of grouping of
table items with group headers and possibly an option to collapse those
groups?

--
Roland Tepp
Re: CompositeTable and item groups... [message #31765 is a reply to message #31660] Wed, 14 March 2007 17:02 Go to previous messageGo to next message
Roland Tepp is currently offline Roland TeppFriend
Messages: 336
Registered: July 2009
Senior Member
Ok... Looked more thoroughly into the CompositeTable and it looks like a
rather stupid question :-\

Composite table does not support row/item groups, and by design is not
supposed to. Looks like I'm bound to go back to the drawing board...

Roland Tepp kirjutas mulle midagi seesugust:
> Hello,
>
> I have a scenario where I have to show two (rather long) listings above
> one another.
>
> These lists (as drawn by our UI designer) would be perfect fit for using
> CompositeTable, but I would really like to avoid having more than one
> scrollbar on the screen and maximize the vertical visible count of the
> listed items as I have to work with rather limited screen-estate
> (touch-screen with 800x600).
>
> I was wandering if CompositeTable can have some sort of grouping of
> table items with group headers and possibly an option to collapse those
> groups?
>

--
Roland Tepp
Re: CompositeTable and item groups... [message #31832 is a reply to message #31660] Fri, 16 March 2007 16:05 Go to previous messageGo to next message
Dave Orme is currently offline Dave OrmeFriend
Messages: 424
Registered: July 2009
Senior Member
Roland Tepp wrote:
> I was wandering if CompositeTable can have some sort of grouping of
> table items with group headers and possibly an option to collapse those
> groups?

You would have to nest CompositeTables inside each other. In order to
do that, CompositeTable would have to permit row objects to be differing
heights, something it does not permit right now, but would be possible
to implement. Your second request would require CompositeTable to
permit rows to have dynamic heights, which would be yet another feature
request.

Patches are welcome. :-)

Regards,

Dave Orme
--
Senior Consultant, Trainer
Coconut Palm Software, Inc.
http://www.coconut-palm-software.com
Re: CompositeTable and item groups... [message #31904 is a reply to message #31765] Sat, 17 March 2007 10:45 Go to previous messageGo to next message
Jeremy Dowdall is currently offline Jeremy DowdallFriend
Messages: 181
Registered: July 2009
Senior Member
on which platform does (or will) your app run?

Roland Tepp wrote:
> Ok... Looked more thoroughly into the CompositeTable and it looks like a
> rather stupid question :-\
>
> Composite table does not support row/item groups, and by design is not
> supposed to. Looks like I'm bound to go back to the drawing board...
>
> Roland Tepp kirjutas mulle midagi seesugust:
>> Hello,
>>
>> I have a scenario where I have to show two (rather long) listings
>> above one another.
>>
>> These lists (as drawn by our UI designer) would be perfect fit for
>> using CompositeTable, but I would really like to avoid having more
>> than one scrollbar on the screen and maximize the vertical visible
>> count of the listed items as I have to work with rather limited
>> screen-estate (touch-screen with 800x600).
>>
>> I was wandering if CompositeTable can have some sort of grouping of
>> table items with group headers and possibly an option to collapse
>> those groups?
>>
>
Re: CompositeTable and item groups... [message #32120 is a reply to message #31904] Tue, 27 March 2007 08:57 Go to previous messageGo to next message
Roland Tepp is currently offline Roland TeppFriend
Messages: 336
Registered: July 2009
Senior Member
For now - Windows only

Jeremy Dowdall kirjutas mulle midagi seesugust:
> on which platform does (or will) your app run?
>
> Roland Tepp wrote:
>> Ok... Looked more thoroughly into the CompositeTable and it looks like
>> a rather stupid question :-\
>>
>> Composite table does not support row/item groups, and by design is not
>> supposed to. Looks like I'm bound to go back to the drawing board...
>>
>> Roland Tepp kirjutas mulle midagi seesugust:
>>> Hello,
>>>
>>> I have a scenario where I have to show two (rather long) listings
>>> above one another.
>>>
>>> These lists (as drawn by our UI designer) would be perfect fit for
>>> using CompositeTable, but I would really like to avoid having more
>>> than one scrollbar on the screen and maximize the vertical visible
>>> count of the listed items as I have to work with rather limited
>>> screen-estate (touch-screen with 800x600).
>>>
>>> I was wandering if CompositeTable can have some sort of grouping of
>>> table items with group headers and possibly an option to collapse
>>> those groups?
>>>
>>

--
Roland Tepp
Re: CompositeTable and item groups... [message #34200 is a reply to message #31832] Sat, 05 May 2007 19:23 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: h3.miegel.org

To solve Roland Tepp's problem, I would have some other UI component to
control the two lists (a sash, a tab control with two tabs, a pair of
controls each with an expand/collapse button, or perhaps the Nebula Shelf
control), and embed two CompositeTable controls in that. That way it is
easy to find, say, the top item in the lower list.

However, Roland does not like that approach but wants a single scroll bar to
scroll through a combined list. To do that, I think you would really have
to create a single CompositeTable with the combined set of rows. You would
probably want to create a separator row. Until variable height rows are
supported, you will have to make the separator row the same height as the
other rows, and because CompositeTable (currently) requires the same control
class to be used for all rows, that row control must use something like
StackLayout to allow it to be both a separator row or a regular row.

I do not think nesting CompositeTables will work well. Either the rows
containing the nested tables are high enough to contain the entire nested
table (in which case why use CompositeTable at all, you may as well use some
other control such as a Table or a Composite with vertical row layout), or
the nested composite tables have nested scroll bars, which would be rather
confusing.

You might think that you would need to use a CompositeTable (even if it has
only two rows) in order to get the support that forces the row layouts to
line up with the header layout. However, that functionality could easily be
moved into a layout manager that can be used on a nested table or on a
composite control.

BTW, I am using a patched version of CompositeTable that supports variable
height rows. However, it needs a bit more work before I am ready to submit
the patch. Basically, a lot of the scolling methods and fields in
InternalCompositeTable don't have any meaning when the rows have different
heights. In order to get it to work in a consistent manner according to
well-defined rules, a complete re-write of these methods was needed.

- Nigel

"David J. Orme" <djo@coconut-palm-software.com> wrote in message
news:etef84$v4e$1@utils.eclipse.org...
> Roland Tepp wrote:
>> I was wandering if CompositeTable can have some sort of grouping of table
>> items with group headers and possibly an option to collapse those groups?
>
> You would have to nest CompositeTables inside each other. In order to do
> that, CompositeTable would have to permit row objects to be differing
> heights, something it does not permit right now, but would be possible to
> implement. Your second request would require CompositeTable to permit
> rows to have dynamic heights, which would be yet another feature request.
>
> Patches are welcome. :-)
>
> Regards,
>
> Dave Orme
> --
> Senior Consultant, Trainer
> Coconut Palm Software, Inc.
> http://www.coconut-palm-software.com
Re: CompositeTable and item groups... [message #34963 is a reply to message #34200] Wed, 16 May 2007 09:11 Go to previous message
Roland Tepp is currently offline Roland TeppFriend
Messages: 336
Registered: July 2009
Senior Member
Thanks Nigel,

I already chose PShelf as a solution to my problem.

Changing CompositeTable to support collapsible/variable height items
seems to cause much of the current CompositeTable design to become much
more complicated than it's original goals need it to be. No to mention
that this would also most likely cause considerable performance hit with
huge datasets.


Nigel kirjutas mulle midagi seesugust:
> BTW, I am using a patched version of CompositeTable that supports variable
> height rows. However, it needs a bit more work before I am ready to submit
> the patch. Basically, a lot of the scolling methods and fields in
> InternalCompositeTable don't have any meaning when the rows have different
> heights. In order to get it to work in a consistent manner according to
> well-defined rules, a complete re-write of these methods was needed.
>
Whoa - you definitely have lots of free time on your hands :)

--
Roland Tepp
Re: CompositeTable and item groups... [message #580170 is a reply to message #31660] Wed, 14 March 2007 17:02 Go to previous message
Roland Tepp is currently offline Roland TeppFriend
Messages: 336
Registered: July 2009
Senior Member
Ok... Looked more thoroughly into the CompositeTable and it looks like a
rather stupid question :-\

Composite table does not support row/item groups, and by design is not
supposed to. Looks like I'm bound to go back to the drawing board...

Roland Tepp kirjutas mulle midagi seesugust:
> Hello,
>
> I have a scenario where I have to show two (rather long) listings above
> one another.
>
> These lists (as drawn by our UI designer) would be perfect fit for using
> CompositeTable, but I would really like to avoid having more than one
> scrollbar on the screen and maximize the vertical visible count of the
> listed items as I have to work with rather limited screen-estate
> (touch-screen with 800x600).
>
> I was wandering if CompositeTable can have some sort of grouping of
> table items with group headers and possibly an option to collapse those
> groups?
>

--
Roland Tepp
Re: CompositeTable and item groups... [message #580217 is a reply to message #31660] Fri, 16 March 2007 16:05 Go to previous message
Dave Orme is currently offline Dave OrmeFriend
Messages: 424
Registered: July 2009
Senior Member
Roland Tepp wrote:
> I was wandering if CompositeTable can have some sort of grouping of
> table items with group headers and possibly an option to collapse those
> groups?

You would have to nest CompositeTables inside each other. In order to
do that, CompositeTable would have to permit row objects to be differing
heights, something it does not permit right now, but would be possible
to implement. Your second request would require CompositeTable to
permit rows to have dynamic heights, which would be yet another feature
request.

Patches are welcome. :-)

Regards,

Dave Orme
--
Senior Consultant, Trainer
Coconut Palm Software, Inc.
http://www.coconut-palm-software.com
Re: CompositeTable and item groups... [message #580257 is a reply to message #31765] Sat, 17 March 2007 10:45 Go to previous message
Jeremy Dowdall is currently offline Jeremy DowdallFriend
Messages: 181
Registered: July 2009
Senior Member
on which platform does (or will) your app run?

Roland Tepp wrote:
> Ok... Looked more thoroughly into the CompositeTable and it looks like a
> rather stupid question :-\
>
> Composite table does not support row/item groups, and by design is not
> supposed to. Looks like I'm bound to go back to the drawing board...
>
> Roland Tepp kirjutas mulle midagi seesugust:
>> Hello,
>>
>> I have a scenario where I have to show two (rather long) listings
>> above one another.
>>
>> These lists (as drawn by our UI designer) would be perfect fit for
>> using CompositeTable, but I would really like to avoid having more
>> than one scrollbar on the screen and maximize the vertical visible
>> count of the listed items as I have to work with rather limited
>> screen-estate (touch-screen with 800x600).
>>
>> I was wandering if CompositeTable can have some sort of grouping of
>> table items with group headers and possibly an option to collapse
>> those groups?
>>
>
Re: CompositeTable and item groups... [message #580407 is a reply to message #31904] Tue, 27 March 2007 08:57 Go to previous message
Roland Tepp is currently offline Roland TeppFriend
Messages: 336
Registered: July 2009
Senior Member
For now - Windows only

Jeremy Dowdall kirjutas mulle midagi seesugust:
> on which platform does (or will) your app run?
>
> Roland Tepp wrote:
>> Ok... Looked more thoroughly into the CompositeTable and it looks like
>> a rather stupid question :-\
>>
>> Composite table does not support row/item groups, and by design is not
>> supposed to. Looks like I'm bound to go back to the drawing board...
>>
>> Roland Tepp kirjutas mulle midagi seesugust:
>>> Hello,
>>>
>>> I have a scenario where I have to show two (rather long) listings
>>> above one another.
>>>
>>> These lists (as drawn by our UI designer) would be perfect fit for
>>> using CompositeTable, but I would really like to avoid having more
>>> than one scrollbar on the screen and maximize the vertical visible
>>> count of the listed items as I have to work with rather limited
>>> screen-estate (touch-screen with 800x600).
>>>
>>> I was wandering if CompositeTable can have some sort of grouping of
>>> table items with group headers and possibly an option to collapse
>>> those groups?
>>>
>>

--
Roland Tepp
Re: CompositeTable and item groups... [message #581937 is a reply to message #31832] Sat, 05 May 2007 19:23 Go to previous message
Nigel is currently offline NigelFriend
Messages: 12
Registered: July 2009
Junior Member
To solve Roland Tepp's problem, I would have some other UI component to
control the two lists (a sash, a tab control with two tabs, a pair of
controls each with an expand/collapse button, or perhaps the Nebula Shelf
control), and embed two CompositeTable controls in that. That way it is
easy to find, say, the top item in the lower list.

However, Roland does not like that approach but wants a single scroll bar to
scroll through a combined list. To do that, I think you would really have
to create a single CompositeTable with the combined set of rows. You would
probably want to create a separator row. Until variable height rows are
supported, you will have to make the separator row the same height as the
other rows, and because CompositeTable (currently) requires the same control
class to be used for all rows, that row control must use something like
StackLayout to allow it to be both a separator row or a regular row.

I do not think nesting CompositeTables will work well. Either the rows
containing the nested tables are high enough to contain the entire nested
table (in which case why use CompositeTable at all, you may as well use some
other control such as a Table or a Composite with vertical row layout), or
the nested composite tables have nested scroll bars, which would be rather
confusing.

You might think that you would need to use a CompositeTable (even if it has
only two rows) in order to get the support that forces the row layouts to
line up with the header layout. However, that functionality could easily be
moved into a layout manager that can be used on a nested table or on a
composite control.

BTW, I am using a patched version of CompositeTable that supports variable
height rows. However, it needs a bit more work before I am ready to submit
the patch. Basically, a lot of the scolling methods and fields in
InternalCompositeTable don't have any meaning when the rows have different
heights. In order to get it to work in a consistent manner according to
well-defined rules, a complete re-write of these methods was needed.

- Nigel

"David J. Orme" <djo@coconut-palm-software.com> wrote in message
news:etef84$v4e$1@utils.eclipse.org...
> Roland Tepp wrote:
>> I was wandering if CompositeTable can have some sort of grouping of table
>> items with group headers and possibly an option to collapse those groups?
>
> You would have to nest CompositeTables inside each other. In order to do
> that, CompositeTable would have to permit row objects to be differing
> heights, something it does not permit right now, but would be possible to
> implement. Your second request would require CompositeTable to permit
> rows to have dynamic heights, which would be yet another feature request.
>
> Patches are welcome. :-)
>
> Regards,
>
> Dave Orme
> --
> Senior Consultant, Trainer
> Coconut Palm Software, Inc.
> http://www.coconut-palm-software.com
Re: CompositeTable and item groups... [message #582397 is a reply to message #34200] Wed, 16 May 2007 09:11 Go to previous message
Roland Tepp is currently offline Roland TeppFriend
Messages: 336
Registered: July 2009
Senior Member
Thanks Nigel,

I already chose PShelf as a solution to my problem.

Changing CompositeTable to support collapsible/variable height items
seems to cause much of the current CompositeTable design to become much
more complicated than it's original goals need it to be. No to mention
that this would also most likely cause considerable performance hit with
huge datasets.


Nigel kirjutas mulle midagi seesugust:
> BTW, I am using a patched version of CompositeTable that supports variable
> height rows. However, it needs a bit more work before I am ready to submit
> the patch. Basically, a lot of the scolling methods and fields in
> InternalCompositeTable don't have any meaning when the rows have different
> heights. In order to get it to work in a consistent manner according to
> well-defined rules, a complete re-write of these methods was needed.
>
Whoa - you definitely have lots of free time on your hands :)

--
Roland Tepp
Previous Topic:dynamic number of columns in CompositeTable
Next Topic:[CompositeTable] UI and design questions
Goto Forum:
  


Current Time: Mon Oct 26 14:38:23 GMT 2020

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

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

Back to the top