FilteringTable
FilteringTable will be replaced in Dijit 1.0 by a Table widget that reads it's data from a dojo.data Store, doing lazy loading, etc.
In the meantime, you can get the same functionality by following the DemoDataTable example in dojox/data/demos/demo_DataDemoTable.html
From Tom:
FilteringTable:
Will be replaced with a Grid widget. Parts of Filtering have already made its way into other parts of Dojo, particularly in Dojo Data (they lifted the sorting code almost verbatum, IIRC).The problem with Filtering is that it anticipated many of the things that are being more fully fleshed out in other parts of the Toolkit, such as data binding mechanisms, data stores, and more. What it really was was a widget I'd written for other projects which we slammed into Dojo because so many people were screaming for a grid. I never really wanted to add it, but there you have it.
We do recognize that a Grid is ridiculously important. I was on deck to write it but I simply don't have the time, and it's better if others who are more involved with the Dijit project take it on (I don't have anything to do with this project other than advice about rendering and layout).
- Printer-friendly version
- Login or register to post comments
- Unsubscribe post
Show Stopper
Without FilteringTable two of the most important pieces of UI I have built using Dojo will not function at all. Dijit having a Table/Grid is hugely important to me.
Even a very basic version of Table/Grid that only displays content from a binding to a dojo.data Store would be fine with me. I don't need sorting, I just need something to display retrieved JSON data from the server in tabular form.
I agree.
No Grid/Table/FilteringTable is a show stopper for 1.0, and as far as i know, it's a required component beforehand. The problem faced with quickly hacking together a 'working' table/grid widget without great lengths of thought is that it would be a shotty API at first, frequently changing, and eventually work it's way upto fully featured component, or be deprecated by a "second version" using an entirely different structure. Both are equally as annoying for developers both making and using said widget. But we hear the plea. One reason is limited resources. The existing stuff in beta has some warts, so a lot of devs are focusing on their own pieces of the puzzle, leaving no one floating about to just 'make Grid.' (I envision a powerful sorting/multiselect widget that can scale down to a simple fixed table of data from a store with paging, and that will take careful consideration and planning) ... Just my thoughts ...
I'm not _against_ a rough/experimental Grid widget in dojox, or even a fairly backwards compatible FilteringTable, but I would imagine most people would prefer something solid and supported in dijit, to avoid the issues dojo 0.4.x faced w/r/t second and third generation iterations. (RichText, Editor, Editor2) or even SortTable -> FilteringTable ... Perhaps you could start a thread in Dojox development where the future of Grid/FilteringTable should take, so all folks listening can have a centralized place to dumb their personal thoughts on the matter.
Thank you Dante
You are right. Dojo cannot simply put out a half-baked Grid widget. It would defeat the purpose of Dijit as a mature consistent platform. For the time being I will either do a basic functional port of FilteringTable or make a simple table widget to tide me over.
I have started Waiting for Grid: Interim ideas for FilteringTable-dependent code in DojoX General Discussion to allow people to share their solutions to this temporary problem.
We also use the
We also use the FilteringTable extensively in our application and would consider it a show stopper if it was not included.
Need Table widget
Without a Table widget that can load from dojo.Store, a 0.9/1.0 version will not suffice for me either. Thanks.
FilteringTable, SortableTable
David S. Boyer
mangr3n at gmail (figure the rest out on your own )
I don't know about you guys, but it's important for me too. I simply ported the SortableTable over, including some modifications I made to it.
I added a setData function for my own purposes. I wired up the selectionCallback and the dblClkCallback's to work, because they don't in 0.4.3 I'd love a "Store" version, but for now, just port the existing ones.
The only funky piece to it was that the initializer appears to be called AFTER postMixInProperties and postCreate. (And of course I'm not sure why startup isn't called). The point is I had to move the this.selection, this.data, and this.columns = [] lines into postMixInProperties for the sorting to work without deleting all of the data or failing completely cause it lost it's data and columns data which is created in postCreate().
It took me about 3 hours to finish the port of it. That's without any knowledge of Dojo 0.9 internals. I also ported some of the old dojo.html functions over into a new 0.9 type module using _hasResource. Which I currently have inlined in the file. I'm gonna externalize those functions and place them in a package specific to my project, but... Voila! I have that control.
Just a suggestion. I had 4 custom widgets, so far, and it has only taken me about 8 hours to get 3 of them ported, including the custom changes to SortableTable.
well hell.
thats _great_ ...
if you are interested in directing any of your enthusiasm towards the toolkit, fill out a CLA and submit some patches. Dojox makes a great home to just those kind of things, and there is obviously a big call for it ... perhaps an existing version in beta/trunk will prompt discussion as to the direction of Grid, or provide for an 'already-ported' foundation.
And I'm glad you caught how easy it was to port stuff ... a lot is just regexp replacing, even. and setting up a sibling library/namespace is as easy as following examples and putting files in a folder ...
keep it up. I'd like to see your results.
Is there any possibility of
Is there any possibility of you sharing the code you did for this port so others (myself) don't have to duplicate this work?
It'd be very very appreciated