Well, so far my lesson from that project has been 'do the other things first until you find the right grid'..... It's a really big project, so I've had plenty keeping me busy in the mean time.
What I do know is that making a grid out of a normal table severely limited my ability to do creative things with it - not all things that have data that falls into a grid, should sort like a grid, etc, looks like a perfect table. One implementation that would be exceptionally useful to me that I see your grid fitting into would be a dataset that gets loaded in the background so that pagination to the next 'page' of results in the grid get cached in javascript... in the background. if the 'next page' worth of data has been loaded, the grid immediately uses the data upon a next event. If it has not, then it waits for an ajax request for the info to be returned. The next hurdle would be sorting those columns, as it would only be able to sort using just what it has retrieved if it retrieved the entire set, otherwise it would have to do an ajax call to allow the server-side to return the dataset pre-sorted (using sql). Any thoughts on any of that? The main point of the above example is that your grid, seeing as its dataset is in javascript (arrays) and not in the DOM, I feel this would be easier for me to implement, and the implementation could make faster decisions about what to do next based on it's current cache of data vs what the server said was left. Am I barking up the right tree here? I see what you mean about the need for docs and solid ground - hopefully this discussion will arouse interest. The fact that you are not just creating a giant table in the DOM, and instead showing only what is necessary should be enough to peek an adept ajaxer's interest. I'd be all over helping you build this, however I'm not so much a javascript ninja yet. I'll be playing with it here, and will certainly offer my thoughts and experiences with it. -Zachariah On Mar 27, 4:14 pm, Tin <michael.leib...@gmail.com> wrote: > Zachariah, > > Thanks for the word of encouragement! Do you have any feedback/ > lessons learned from your application? > I've made a lot of progress recently in terms of adding a DataView to > drive the grid and optimizing the core loop, but formalizing the API > and writing the documentation haven't been moving very fast. > Unfortunately, without that documentation, a lot of people seem to be > dismissing it at first glance without realizing what makes SlickGrid > different. > > +Michael > > On Mar 27, 4:24 am, Zachariah <craniumcomput...@gmail.com> wrote: > > > Michael, > > > I am incredibly impressed with the speed of this grid. Last month I > > began a search for the right grid, and I didn't find it. For my > > application, I needed formatting flexibility that tables could not > > offer, and large data-set handling that make most other grids studder. > > I've been using jquery for quite sometime and yet have never been > > compelled to post in the forums until now (as I always found my answer > > before I did). I truly hope an incarnation of SlickGrid makes it into > > jquery ui and therefore gets all the love and attention necessary to > > make it the star it deserves to become. > > > -Zachariah
