Ricardo Borillo Domenech schrieb:
El mié, 04-01-2006 a las 14:22 +0100, Sebastian Werner escribió:
Ricardo Borillo Domenech schrieb:
Hi,
I agree with you. It's necessary a more complex component derived from
QxListView.
Now, it's ok for me to implement pagging outside QxListView, but i have
a problem. How can i handle the sort event fired when i click in a
column? It's necessary to handle this even if you want to sort all the
dataset and reload de data in a concret page. Do you know what i mean?
I am not sure why you need something like paging. QxListView can easily
handle datasets with 10000 entries. If you want to paging inside more
data you just replace the content of the initial given array and update
the listview afterwards. The sort always sorts the current array which
is assigned with the listview. If you want to send this sort request to
the server you need to handle it someway different. Probably you can
have a look at QxListViewHeaderCell and send a patch (which is
compatible with the current behaviour) to allow an optional handling of
the sort stuff through some server based logic.
I think it's a problem of user usability. It's quite dificult IMHO for a
user to manage a scrolled view of 10000 rows. It's quite esasy to
navigate pagging, filtering and viewing a reduced subset of information.
It's true that QxListView can handle 10000 entries datatsets, but is
this good for performance?? I think no. If you have to retrieve a 10000
rows XML file from server produced by a SQL query (10000 records + order
by) and you want to do it a lot of times, i think thant would be heavy.
Instead of the old QxListView from HEAD the new one have no really heavy
performance impact when handling with thousands of entries. The problem
with this is more the backend nowadays. A query which sends all the
10000 entries from the database to the client is the most time not the
thing which is wanted.
I think both things are needed. Yes, filters are great, but a complete
list is sometimes wanted too. I would suggest to let the user choose the
view, by filtering the data, sorting it, or show the complete list.
Whatever the server can handle.
There are typical applications in the windows and mac world which has
these large lists like iTunes or so on. I don't think the user find it
to problematic as long as you have also the ability to filter the
results/list.
I think somethings like a background transfer/fill of the list could
work very well (while the user is looking at the first ones). But this
all depends on your application needs.
I really hate things like paging for navigation in list. But this is
just my opinion.
Sebastian
I take a look at QxListViewHeaderCell for handle sort events, thanks
I think that the problem (IMHO) is than in QxListView columns are not
classes ...
This is typical for the grid. The same is true for the rows. I don't
understand why this related to the above problem.
Sorry, you are write, the class that i was looking for was
QxListViewHeaderCell :)
More IMHO :)
I'm trying to adopt qooxdoo as a replacement of our desktop applications
(i think it's cool ;). In my enviroment a QxListView will be only an
base class, and the real usefull class would be QxDataGrid (look at the
attached image). In this enviroment the QxListView (that is amazing)
can't be used :(
Principal conditionants:
- Performance
- Multipage support for navigation, sort, filter, etc
- Data integration
What is your problem/question here? Why do you can't use it the way
shown in the image?
It's not a problem/question, i only try to explain my personal situation
in this topic. I will try to use it the way shown in the image, but I
would like to know if QxListView creators are working in this direction
or it's only a personal requirement.
Thanks
Sebastian
Thanks a lot
El mié, 04-01-2006 a las 22:26 +1100, Chris Ricks escribió:
Hi Ricardo!
I agree, but this may not belong in QxListView. Expecting a widget
already as complex as QxListView to handle that many records might be a
requirement if you want simple sorting for your entire dataset, but
creating a compound solution whereby the QxListView widget only contains
the currently visible data whilst handling other functions outside of it
may be easier (and allow for simpler development of QxListView).
What are your thoughts?
Best regards,
Chris
Ricardo Borillo Domenech wrote:
Hi,
I agree with the need of an editable grid, but I guess if it's possible
to add pagging/filtering support to the ListView. This feature will be
usefull when you have thousands of rows from a dataset.
Thanks,
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
