[gwt-contrib] Re: gen2 TreeTable demo online

2008-11-26 Thread dflorey

Hi,
try it like this:
1. Collapse the tree (=close all tree nodes with the button in the
left bottom corner)
2. enter value inti iq-filter
3. select operator (=, !=,  ,  etc.)

In tree view the filter applies only to the root elements.

If you want to filter all items switch to table view.

Hope this helps,

Daniel

On 25 Nov., 14:57, ANDRES BRUN [EMAIL PROTECTED] wrote:
 Hi Daniel
 I was testing the filters but, IQ Don't works, I put it on the field, the
 117 number and nothing happened, all fields are blanking.

 how works?

 Please, sorry if don't work like that, and let me know the way.

 Thanks.



 On Tue, Nov 25, 2008 at 8:33 AM, dflorey [EMAIL PROTECTED] wrote:

  Hi Bruce,
  have you seen that you can easily navigate to the parent node by
  clicking on one of the dotted lines (links) on the left hand side of
  the leaf?
  My major issue concerning usability is the filtering... Should we only
  filter top level items (as it is implemented right now) or shall the
  filter be applied to children. And if yes, how to display the result?

  On 25 Nov., 14:10, Bruce Johnson [EMAIL PROTECTED] wrote:
   Looks cool, Daniel. I do have a question about its basic usability,
  though.
   It seems that the combination of tree + paging is a recipe for end-user
   confusion. When you open a tree item with lots of children then advance
  to
   the next page, you see the children, but lose context on what its parents
   are.
   Anyone have thoughts on how we could address that?

   On Mon, Nov 24, 2008 at 7:09 AM, dflorey [EMAIL PROTECTED]
  wrote:

Hi,
I've put together a live demo for the TreeTable stuff in my branch.
You can find the demo link in the wiki page that I've created
containing a minimalistic tutorial:

   http://code.google.com/p/google-web-toolkit-incubator/wiki/TreeTable

As you can see from the demo I've simplified the table creation by
adding header information to the column definitions, providing typed
column definitions with proper filtering, sorting and editing.
The tables can now handle implicit data and header table creation, so
creating a TreeTable is now as simple as can be.
I've migrated the ImageBundles to ImmutableResourceBundle, localized
the strings by using i18n Messages and used CssResource for styling.
I've moved all classes required both on client and server side to the
share subpackage and added an ant task to create the gwt-incubator-
servlet.jar containing these classes.

Any feedback is welcome!

 --
 Un Saludo

 ANDRES BRUN
 -
 WebSite Andres Brunhttp://www.andresbrun.tk
 Blog -http://doyan2007.blogspot.com/
 WebSitehttp://prolinetsystems.tk
--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---



[gwt-contrib] Re: gen2 TreeTable demo online

2008-11-25 Thread Brad Larson

I've been following this patch because the app I'm working on will
really benefit from it.

Ideally, I do not want children to fall off the list to the next
page.  My table will start with all children collapsed.  When the user
opens a node, I would like for new rows to show up on the table.  My
table will already have a vertical scroll bar, so I'd like the nodes
below to just scroll down a bit.  I don't want to move what pages in
the table items appear on because of opening/closing of nodes.

Not all use-cases will be like this, but that is what would be best
for my app.  Maybe a setting could be added to define the paging
behavior when nodes are opened?

Daniel - great work on this patch.  I'm very excited to pull it into
my project!

Thanks!
-Brad

On Nov 25, 7:10 am, Bruce Johnson [EMAIL PROTECTED] wrote:
 Looks cool, Daniel. I do have a question about its basic usability, though.
 It seems that the combination of tree + paging is a recipe for end-user
 confusion. When you open a tree item with lots of children then advance to
 the next page, you see the children, but lose context on what its parents
 are.
 Anyone have thoughts on how we could address that?

 On Mon, Nov 24, 2008 at 7:09 AM, dflorey [EMAIL PROTECTED] wrote:

  Hi,
  I've put together a live demo for the TreeTable stuff in my branch.
  You can find the demo link in the wiki page that I've created
  containing a minimalistic tutorial:

 http://code.google.com/p/google-web-toolkit-incubator/wiki/TreeTable

  As you can see from the demo I've simplified the table creation by
  adding header information to the column definitions, providing typed
  column definitions with proper filtering, sorting and editing.
  The tables can now handle implicit data and header table creation, so
  creating a TreeTable is now as simple as can be.
  I've migrated the ImageBundles to ImmutableResourceBundle, localized
  the strings by using i18n Messages and used CssResource for styling.
  I've moved all classes required both on client and server side to the
  share subpackage and added an ant task to create the gwt-incubator-
  servlet.jar containing these classes.

  Any feedback is welcome!
--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---



[gwt-contrib] Re: gen2 TreeTable demo online

2008-11-25 Thread Brad Larson

Setting the page size dynamically might be the best solution for my
situation.

I have lots of top-level nodes (thousands) and some of them... maybe
5% will have 2-8 children nodes.  Nodes are never more than 1 child
deep.  I need paging, but don't want to adjust what page an item is on
due to opening or closing nodes.  I will look into setting the page
size dynamically... Daniel, please let me know if you get a chance to
test this and how it goes.

Thanks!
-Brad

On Nov 25, 7:43 am, dflorey [EMAIL PROTECTED] wrote:
 Another option would be to set the page size dynamically to the number
 of visible children of the opened root node. I'll give it a try and
 see if it makes navigation more intuitive.
 If you end up with many many child nodes you'll see that paging is not
 the worst possible solution (as rendering times will not esceed a
 certain level)  ;-)

 On 25 Nov., 14:34, Brad Larson [EMAIL PROTECTED] wrote:

  I've been following this patch because the app I'm working on will
  really benefit from it.

  Ideally, I do not want children to fall off the list to the next
  page.  My table will start with all children collapsed.  When the user
  opens a node, I would like for new rows to show up on the table.  My
  table will already have a vertical scroll bar, so I'd like the nodes
  below to just scroll down a bit.  I don't want to move what pages in
  the table items appear on because of opening/closing of nodes.

  Not all use-cases will be like this, but that is what would be best
  for my app.  Maybe a setting could be added to define the paging
  behavior when nodes are opened?

  Daniel - great work on this patch.  I'm very excited to pull it into
  my project!

  Thanks!
  -Brad

  On Nov 25, 7:10 am, Bruce Johnson [EMAIL PROTECTED] wrote:

   Looks cool, Daniel. I do have a question about its basic usability, 
   though.
   It seems that the combination of tree + paging is a recipe for end-user
   confusion. When you open a tree item with lots of children then advance to
   the next page, you see the children, but lose context on what its parents
   are.
   Anyone have thoughts on how we could address that?

   On Mon, Nov 24, 2008 at 7:09 AM, dflorey [EMAIL PROTECTED] wrote:

Hi,
I've put together a live demo for the TreeTable stuff in my branch.
You can find the demo link in the wiki page that I've created
containing a minimalistic tutorial:

   http://code.google.com/p/google-web-toolkit-incubator/wiki/TreeTable

As you can see from the demo I've simplified the table creation by
adding header information to the column definitions, providing typed
column definitions with proper filtering, sorting and editing.
The tables can now handle implicit data and header table creation, so
creating a TreeTable is now as simple as can be.
I've migrated the ImageBundles to ImmutableResourceBundle, localized
the strings by using i18n Messages and used CssResource for styling.
I've moved all classes required both on client and server side to the
share subpackage and added an ant task to create the gwt-incubator-
servlet.jar containing these classes.

Any feedback is welcome!
--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---



[gwt-contrib] Re: gen2 TreeTable demo online

2008-11-25 Thread dflorey

Yep, this seems to be a good idea! I'll add this as an option to the
tree.
As I still would like to keep the number of items per page limited I'd
propse to present the child when expanded like this (pagesize=5):
- Numbers - Integers ...
- ...more (click to collapse)
- 56
- 57
- 58
- ...more



On 25 Nov., 15:57, Bruce Johnson [EMAIL PROTECTED] wrote:
 On Tue, Nov 25, 2008 at 8:33 AM, dflorey [EMAIL PROTECTED] wrote:

  Hi Bruce,
  have you seen that you can easily navigate to the parent node by
  clicking on one of the dotted lines (links) on the left hand side of
  the leaf?

 I see that it works, but it still doesn't really address the general
 question of giving the user a clear sense of context.

 It seems like this would be better as an infinite scroll to achieve the
 effect of on-demand loading without forcibly breaking things across pages.
 If there happened to be a really large number of children for a tree item,
 perhaps we could introduce a notion of an ellipsis in the child list, like
 this:

 - Numbers
 --- Integers
 - 1
 - 2
 - ... (click to show all)
 - 99
 - 100

 That way, you could keep the hierarchical context for easy skimming of the
 overall structure, yet the user can drill down explicitly when they have
 enough of an idea about where they want to look. It's sort of like cold
 folding in IDE.
--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---



[gwt-contrib] Re: gen2 TreeTable demo online

2008-11-25 Thread ANDRES BRUN
Hi Daniel
I was testing the filters but, IQ Don't works, I put it on the field, the
117 number and nothing happened, all fields are blanking.

how works?

Please, sorry if don't work like that, and let me know the way.

Thanks.

On Tue, Nov 25, 2008 at 8:33 AM, dflorey [EMAIL PROTECTED] wrote:


 Hi Bruce,
 have you seen that you can easily navigate to the parent node by
 clicking on one of the dotted lines (links) on the left hand side of
 the leaf?
 My major issue concerning usability is the filtering... Should we only
 filter top level items (as it is implemented right now) or shall the
 filter be applied to children. And if yes, how to display the result?

 On 25 Nov., 14:10, Bruce Johnson [EMAIL PROTECTED] wrote:
  Looks cool, Daniel. I do have a question about its basic usability,
 though.
  It seems that the combination of tree + paging is a recipe for end-user
  confusion. When you open a tree item with lots of children then advance
 to
  the next page, you see the children, but lose context on what its parents
  are.
  Anyone have thoughts on how we could address that?
 
  On Mon, Nov 24, 2008 at 7:09 AM, dflorey [EMAIL PROTECTED]
 wrote:
 
   Hi,
   I've put together a live demo for the TreeTable stuff in my branch.
   You can find the demo link in the wiki page that I've created
   containing a minimalistic tutorial:
 
  http://code.google.com/p/google-web-toolkit-incubator/wiki/TreeTable
 
   As you can see from the demo I've simplified the table creation by
   adding header information to the column definitions, providing typed
   column definitions with proper filtering, sorting and editing.
   The tables can now handle implicit data and header table creation, so
   creating a TreeTable is now as simple as can be.
   I've migrated the ImageBundles to ImmutableResourceBundle, localized
   the strings by using i18n Messages and used CssResource for styling.
   I've moved all classes required both on client and server side to the
   share subpackage and added an ant task to create the gwt-incubator-
   servlet.jar containing these classes.
 
   Any feedback is welcome!
 



-- 
Un Saludo

ANDRES BRUN
-
WebSite Andres Brun http://www.andresbrun.tk
Blog - http://doyan2007.blogspot.com/
WebSite http://prolinetsystems.tk

--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---



[gwt-contrib] Re: gen2 TreeTable demo online

2008-11-24 Thread dflorey

BTW: Right now the filters are only applied to the top level elements.
I've tried other approaches but with confusing results for the user.
Any suggestions how to apply the filters to children are welcome!
I had the idea to add a chainsaw icon to the TreeController that will
flatten the tree to a normal ScrollTable. Filtering could be applied
to the flattened result and when switching back to tree view the
selection could be kept. But this is not very intuitive...


On 24 Nov., 13:09, dflorey [EMAIL PROTECTED] wrote:
 Hi,
 I've put together a live demo for the TreeTable stuff in my branch.
 You can find the demo link in the wiki page that I've created
 containing a minimalistic tutorial:

 http://code.google.com/p/google-web-toolkit-incubator/wiki/TreeTable

 As you can see from the demo I've simplified the table creation by
 adding header information to the column definitions, providing typed
 column definitions with proper filtering, sorting and editing.
 The tables can now handle implicit data and header table creation, so
 creating a TreeTable is now as simple as can be.
 I've migrated the ImageBundles to ImmutableResourceBundle, localized
 the strings by using i18n Messages and used CssResource for styling.
 I've moved all classes required both on client and server side to the
 share subpackage and added an ant task to create the gwt-incubator-
 servlet.jar containing these classes.

 Any feedback is welcome!
--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---