while in certain cases it is appropriate to define extended/simple view on a 
per user bases I can image a lot more business case dependent situation for 
which the case itself is relevant if simple or extended view has to be used.

Example 1: a company deals in EUR and ocasionally in other currencies: All 
foreign exchange rate related information can usually be hidden - the user 
should have the option to switch to extended view for special cases, or even 
better, the system should "learn" and propose the extended view, if the partner 
"usually/mostly" deals in foreign currency.

Example 2: products same argument, but the relevant fields may depend usually 
on the product category or type (stockable and service differ usually - no 
volume, weight, make to stock, packaging, inventory and stock accounting 
properties...), but for rare cases it might be necessary to use and see all 
fields.
eventually  this could also be solved distributing 2 or 3 standard menu entries
* stockable product
* service product
* products

I greatly would appreciate to see this in 4.4 as usability enhancement




_______________________________________________
Tinyerp-users mailing list
http://tiny.be/mailman/listinfo/tinyerp-users

Reply via email to