> I want to bring here the discussion about the general aspect of having only on
> large text entry (like Google) instead of many widgets (currently).
> I think it will make the interface cleaner and more useful.
> Of course it will need some "clever" autocompletion help.
where will that search field be put?
i'm looking forward to have a global search field with a grouped
search result:
%<----------------------------------
[*hol* ] (Search)
results in:
Articles___________________
Holmes autograph
Sleepy Hollow - the movie
Party_____________________
Holmes and Watson Detectives
Holmes Inc.
Invoices___________________
Investigation to whatever
Calendar__________________
friday: Meeting with Watson and Holmes
Attachments_______________
holmes_picture_1.jpg
holmes_biography.pdf
%<----------------------------------
To have the same behaviour: put in text, and fire the search button
and take a deeper look in results.
Well, not everytime the best choice, but a lot of times very handy.
It may be necessary to define one or two global searchable fields per
model (name, description) or over every field via some fulltext-
engine.
And there should be the "old" extended search for searching inside
special Fields and/or Models.
For extended search it would be great to have a search to span over
multiple models to search for common attributes like "name" (product-
name, party-name). Maybe with an checkbox next to every model in the
list.
It would be a nice feature to surf through the resultset. I don't know
how to explain that very well. Here is an example how you can klick
through your data maybe with an indefinite tree-view, a new kind of
view or with new windows.
party
+invoices
| invoice 1
+ invoice 2
| article 1
+ article 2
| stock
+ party (supplier)
| address
+ invoices
+ invoice 1
+ article 1
| invoice 2
| article 3
| ...
| invoice 3
| invoice 4
well. hope you got it. imho treeview is not the best one, but good to
explain.
so its not very technical it post this via tryton
greets
tobias
--
[email protected] mailing list
