Well, i started with trying to use 1.4 Table with 1.5 RCx GWT and encountered numerous problems while trying to compile the example on the page. After solving all the issues i finaly managed to get it to work, but it didn't play nice in my prety complex GUI layout with a lot of Panels: size and visibility issues. In comparison to it, a Ext GWT table was a half an hour work and it works prety stable. Basicaly you can see all my issues when you look at the comments on the incubator page. I didn't report the issues because people did it before me and the was no response to it, and because the project seemed to be dead - no updates in months(but that was severall weeks ago).
On 4 Nov., 21:13, "Isaac Truett" <[EMAIL PROTECTED]> wrote: > > Bugs, bugs and one more time bugs. > > Alex, > > What problems did you encounter with PagingScrollTable? Have you > entered them into the issue tracker? > > - Isaac > > On Tue, Nov 4, 2008 at 4:53 AM, alex.d <[EMAIL PROTECTED]> wrote: > > > On 3 Nov., 15:30, Suri <[EMAIL PROTECTED]> wrote: > >> Hi Alex, > >> Well here are my concerns on both areas but before I get to that I'd > >> like to mention that I'm developing I guess a relatively small module > >> but something I think is complex in terms of the amount of > >> functionality its providing. The idea is to have a table of data that > >> is retrieved from the server and displayed to the user > > >> 1) The data should be sortable/pageable > >> 2) When the user clicks on a cell/row: > >> - the row gets highlighted > >> - the info of that row shall appear in a "editable" row below the > >> table where once the user makes and changes, these are reflected in > >> the main table > >> - once the user navigates to another row, the edited row should > >> have some sort of marker displaying that it is dirty until the save > >> button is clicked ( this is allowing for batch processing) > >> - thus when a user decides to sort/page this information would need > >> to be retained until the user saves. > >> 3) The user has a drop down above the table to filter by a couple of > >> the columns. > > So far not a problem with both of them. > > >> I looked at ext-GWT and GWT-ext. Both seem are somewhat ok about this, > >> however with ext-GWT > >> - You can't paginate/sort on the client side if I'm not wrong and the > >> whole model seems to force you to do remote pagination which from what > >> I saw, would basically reset the data each time - so not a good option > > You can sort on the client side - it's per default that way if you > > want to sort only the current page - in case you want to sort the > > whole data and then have a page Nr. N, you will have to sort/page on > > the server. New grid supports editing directly in the cells(so no page > > refresh necessary). But i haven't used it yet. > > >> And with GWT-ext: > >> I tried implementing it however, ran into some memory overflow problem > >> when trying to compile it. Plus, there was a file PagingMemoryProxy > >> that was not available in the GWT-ext library but then I later found > >> it in the gwtux library. Not sure why it is like that. > > I do not use GWT-ext. The whole javascript-wrapper concept isn't the > > best idea imho. > > >> On the whole the problem with both ideas is that, I thought of them > >> more as widgets but turns out they almost completely take over your > >> code with a whole bunch of different things to do as opposed to > >> standard GWT code. So, that isn't really an attractive idea. > > Well, i found out that writting smth. as complex as Ext-GWT's grid > > would take too much time and effort - can't really afford it in my > > project. Using existing widgets bring some problems, mostly due to the > > specific nature of your particular application, but they are solvable > > and you need much less time for it. > > >> Alex, > >> What were the problems you found with PagingScrollTable? Just curious > >> to know since I'm trying to get an idea of what I might need/ not > >> need. > > Bugs, bugs and one more time bugs. Imho you'll need far more time > > solving problems/fixing bugs with PagingScrollTable than doing same > > thing with Ext-GWT's grid. But if you decide to write your own grid, > > then using/rewriting/fixing PagingScrollTable might be a good > > approach. > > >> Thanks > >> Suri > >> On Nov 3, 4:46 am, "alex.d" <[EMAIL PROTECTED]> wrote: > > >> > PagingScrollTable isn't really smth. one can recommend. You have more > >> > trouble with it then anything else. Both GWT-EXT and Ext GWT have > >> > paging tables. It's worth to take a look. > > >> > On 31 Okt., 18:03, "Isaac Truett" <[EMAIL PROTECTED]> wrote: > > >> > > Yes, I've used the original version in several places in one project > >> > > and I plan on using the gen2 incarnation in another project. I highly > >> > > recommend PagingScrollTable. > > >> > > On Fri, Oct 31, 2008 at 12:53 PM, Suri <[EMAIL PROTECTED]> wrote: > > >> > > > Hi Issac, > >> > > > I had looked at that initially but got discouraged by the comments > >> > > > below on the page. Have you used it? Is it any good? > > >> > > > Thanks > >> > > > Suri > > >> > > > On Oct 31, 9:25 am, "Isaac Truett" <[EMAIL PROTECTED]> wrote: > >> > > >> The GWT Incubator has a PagingScrollTable. > > >> > > >>http://code.google.com/p/google-web-toolkit-incubator/wiki/PagingScro... > > >> > > >> On Fri, Oct 31, 2008 at 9:22 AM, Suri <[EMAIL PROTECTED]> wrote: > > >> > > >> > Is there a widget available for pagination/sorting? Other than > >> > > >> > the ext > >> > > >> > code. > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
