GTK client fetches 80 (default) and webclient 20 records, some of them ordered by "name" some by id, some by nothing.
if the table has many rows (some 100 or 1000) the chances are low to get the the wanted records and the user has to enter a query anyhow. a) it is difficult to explain to users that there is sometimes no "visible" context to explain which records are displayed. b) on slow (mobile) internet connections it's waste of bandwidth and cost(!) Suggestion (as already made once elsewhere) It should be possible to define if the client should fetch the first set of records or not. The decision could be automatic * all records fit on the first screen or * the list is "short" (some screen full) and sorted by "name" or any other visible sort criteria and/or programmatic ( ir_act_window - autofetch - bool ) * fetch initial records yes/no + display text "pls enter search criteria") -------------------- m2f -------------------- -- http://www.openerp.com/forum/viewtopic.php?p=24444#24444 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
