[gwt-contrib] Re: "Locking" Columns in PagingScrollTable
You can find my branch here: http://code.google.com/p/google-web-toolkit-incubator/source/browse/#svn/branches/dflorey/tableAddons Description of some addons: http://code.google.com/p/google-web-toolkit-incubator/wiki/TreeTable Cheers, Daniel On 28 Jul., 19:43, jay wrote: > What branch and what functionality have you already added? > > jay > > On Jul 28, 1:44 am, dflorey wrote: > > > > > I'm not sure about the current status of when things will proceed and > > move to trunk, but I'd like to see this feature in the core table > > framework! > > If you have some patches, I can of course add them to my branch as > > I've already added some functionality to the tables and at least try > > to merge back the incubator trunk into my branch from time to time. > > This is how I'd implement this feature (just brainstorming): > > Add another table to the ScrollTable (copy&paste the code from > > creating the header table). The width of the header table columns has > > to be kept in sync manually when the content of the data table > > changes. So you should grab the same events and sync the height of the > > rows of your "fixedColumnTable". > > It would be cool if there would be a way to define the "fixed" > > property in the CoumnDefinition. The is already a bunch of classes for > > each column property so it does not harm to introduce another one ;-) > > Check for the "fixed" property when constructing the table and add > > additional tables for fixed columns not next to each other and recalc > > the column index to populate the proper tables when populating data. > > Finally we would end up with a dynamic number of data tables (think of > > a table with a fixed first and last column = 3 data tables) that all > > have to be kept in sync regarding row height. > > > On Jul 28, 7:35 am, jay wrote: > > > > I'm about to embark on coming up with a way to "lock" 1 or more of the > > > left-most columns. E.g., the locked columns will not scroll > > > horizontally as the other columns are scrolled. > > > > I've googled around, and not found any other work towards this, so I'm > > > hoping it's not impossible. > > > > Currently, I'm using the PagingScrollTable... My first thought is that > > > I would create a wrapper that would internally separate the TableModel > > > into two, and create two separate PagingScrollTable instances, smushed > > > side-by-side. > > > > However, if I do this, one thing I really am unsure of is how to keep > > > the height of each row in sync? > > > > I appreciate any hints, tips, and/or tricks! > > > > jay --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] Re: "Locking" Columns in PagingScrollTable
What branch and what functionality have you already added? jay On Jul 28, 1:44 am, dflorey wrote: > I'm not sure about the current status of when things will proceed and > move to trunk, but I'd like to see this feature in the core table > framework! > If you have some patches, I can of course add them to my branch as > I've already added some functionality to the tables and at least try > to merge back the incubator trunk into my branch from time to time. > This is how I'd implement this feature (just brainstorming): > Add another table to the ScrollTable (copy&paste the code from > creating the header table). The width of the header table columns has > to be kept in sync manually when the content of the data table > changes. So you should grab the same events and sync the height of the > rows of your "fixedColumnTable". > It would be cool if there would be a way to define the "fixed" > property in the CoumnDefinition. The is already a bunch of classes for > each column property so it does not harm to introduce another one ;-) > Check for the "fixed" property when constructing the table and add > additional tables for fixed columns not next to each other and recalc > the column index to populate the proper tables when populating data. > Finally we would end up with a dynamic number of data tables (think of > a table with a fixed first and last column = 3 data tables) that all > have to be kept in sync regarding row height. > > On Jul 28, 7:35 am, jay wrote: > > > > > I'm about to embark on coming up with a way to "lock" 1 or more of the > > left-most columns. E.g., the locked columns will not scroll > > horizontally as the other columns are scrolled. > > > I've googled around, and not found any other work towards this, so I'm > > hoping it's not impossible. > > > Currently, I'm using the PagingScrollTable... My first thought is that > > I would create a wrapper that would internally separate the TableModel > > into two, and create two separate PagingScrollTable instances, smushed > > side-by-side. > > > However, if I do this, one thing I really am unsure of is how to keep > > the height of each row in sync? > > > I appreciate any hints, tips, and/or tricks! > > > jay --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] Re: "Locking" Columns in PagingScrollTable
I'm not sure about the current status of when things will proceed and move to trunk, but I'd like to see this feature in the core table framework! If you have some patches, I can of course add them to my branch as I've already added some functionality to the tables and at least try to merge back the incubator trunk into my branch from time to time. This is how I'd implement this feature (just brainstorming): Add another table to the ScrollTable (copy&paste the code from creating the header table). The width of the header table columns has to be kept in sync manually when the content of the data table changes. So you should grab the same events and sync the height of the rows of your "fixedColumnTable". It would be cool if there would be a way to define the "fixed" property in the CoumnDefinition. The is already a bunch of classes for each column property so it does not harm to introduce another one ;-) Check for the "fixed" property when constructing the table and add additional tables for fixed columns not next to each other and recalc the column index to populate the proper tables when populating data. Finally we would end up with a dynamic number of data tables (think of a table with a fixed first and last column = 3 data tables) that all have to be kept in sync regarding row height. On Jul 28, 7:35 am, jay wrote: > I'm about to embark on coming up with a way to "lock" 1 or more of the > left-most columns. E.g., the locked columns will not scroll > horizontally as the other columns are scrolled. > > I've googled around, and not found any other work towards this, so I'm > hoping it's not impossible. > > Currently, I'm using the PagingScrollTable... My first thought is that > I would create a wrapper that would internally separate the TableModel > into two, and create two separate PagingScrollTable instances, smushed > side-by-side. > > However, if I do this, one thing I really am unsure of is how to keep > the height of each row in sync? > > I appreciate any hints, tips, and/or tricks! > > jay --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
