Hey,
In my case I want to build a Database Application with a list or table
(I am not sure which is best yet) of customers on the left side of the
window. When the user clicks on a customer in the list I want to
display the customer details in the same window to the right of the list.
Sounds like a classic master-detail relation, perfectly suited for data binding.
Questions:
1) Should I use a list or table for the customer list? The text in the
customer list will not be just a single field. It could be a customized
combination of fields. The data will be obtained from the server in
Json format
The table is a huge feature monster having all kind of features you might not
need for that kind of list like sorting, reordering columns, editing and all
that stuff. So I would suggest to go with a list and write a custom list item
holding all the values you need to display. With that approach, you are able to
use the data binding and you have the freedom to design the list item the way
you like it.
2) Should I use a store for the customer data? I have been reading the
documentation and using the demo browser to see when a store should be
used. I noticed that Remote table example just created a model and the
code does not show the use of a store. I have seen some other examples
of lists using a store. Can anyone explain when a store should be used?
The problem you describe is about the missing data binding controller for the
table. So using a store only makes sense if you need to have the data in a
model object which then, can be handled by a controller easily. As there is no
table controller, usually it makes not much sense to use a store to load data
for the table. But using the list, the store is the way to go, especially when
you have JSON data like you have.
I would suggest to take a look at the code of the feedreader demo application
we ship with qooxdoo. It has something similar like a master-detail view. A set
of slides [1] came just to my mind I made some time ago which might also help
to understand how the feedreader is build.
I hope that gets you some answers,
Martin
[1] http://www.slideshare.net/wittemann/data-binding-in-qooxdoo (slide 101+)
------------------------------------------------------------------------------
Why Cloud-Based Security and Archiving Make Sense
Osterman Research conducted this study that outlines how and why cloud
computing security and archiving is rapidly being adopted across the IT
space for its ease of implementation, lower cost, and increased
reliability. Learn more. http://www.accelacomm.com/jaw/sfnl/114/51425301/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
