Hello,

I saw in TODO that a priority task is to enhance sear functionality.
I totally agree.
The current function is powerful but too complex for every day work.
(for example, try to search a text on all columns without case sensitive)

To search:
* go on search page
* dble click on criteria
=> this add a criteria field
* click on criteria field to edit it
* select on combobox the comparator
=> this add a edit field
* click on new edit box
* enter text
* click on search

Lot of operation for just a 'simple' search !

The function allows mixed AND/OR search on all columns with lot of comparator (contains, regex, >, <, is lowercase....).

It is useful but as advanced of advanced mode !
(the next step is to allow direct SQL as in debug view )

Note: one can search on each page with list filtering. Moreover, with the column restricting option (a:xxx) and others options (+/-, next < > =...), it is easier/faster to search locally. But this is limited to one page.

I will try to add some posts on complex search in different software...

a+
Vicnet

What I need, by complexity order (and also by usage frequency):

• simple search: of a text on all account and all column, not case sensitive
• simple search, on one specific column
• AND search, on multiple specific columns
• complex search, as current search

All with minimum number of click !

Remark: we can imagine to search on specific columns with simple text search (first usecase) and column restriction (a:xxx m:xxx) !
(same syntax as filtering)

Even if search is enhanced, it could fill/use the current search tool. to allow more complex search.
For example: enter account:xxxx in simple text search will fill current search page with Account criteria and 'contains xxxx ' property.

Microsoft Money (1999)

When asking for a search, a first dialog appears that allows a simple text search.
A radio-box button allow to select Advanced Search (then Next, it is a wizard in fact).
Advanced search next page displays criteria as Tab pages:
* Text
* Account
* Date
* Amount
* Category
* Payee
* Details

Each page is specialized in a criteria and allow to enter search information quickly (or less rapid, bad example: payees that is horrible when lot of items).

This allow a AND type search only.

The before last page of the wizard show the results, and last page allow to replace some fields.

See doc
Interesting because also complex and in KDE as Skrooge

The search function is accessible by a left toolbar button.
The first view allow to do a simple text search (as Money) and to access Advanced search (with a button).

The advanced search presents criteria on folded areas.
Each area is organized in three 'column':
* name of property
* describe of search on this criteria
* user parameters

For example:

Code: Select all

Date          Return pictures created between            [   ] and [   ]

The always unfold first area is a simple text criteria.

A discret label on title are allow to select between AND, OR, NOR and NOT one searchs.
(these options are hidden at beginning)

There is also a 'Try' buttonthat allows to see the result (or a part of the result ?) of the current search without closing it.

When googling on money, found this page on how to design an UI
Not read yet...

vicnet wrote:Hello,

Hi Vicnet,

vicnet wrote:
I saw in TODO that a priority task is to enhance sear functionality.
I totally agree.
The current function is powerful but too complex for every day work.
(for example, try to search a text on all columns without case sensitive)

To search:
* go on search page
* dble click on criteria
=> this add a criteria field
* click on criteria field to edit it
* select on combobox the comparator
=> this add a edit field
* click on new edit box
* enter text
* click on search

Lot of operation for just a 'simple' search !

The function allows mixed AND/OR search on all columns with lot of comparator (contains, regex, >, <, is lowercase....).

It is useful but as advanced of advanced mode !

You are right, this is in the TODO list but, to be honest, the plan was to redesign the panel with the same functionalities.
This was not to reduce the number of clicks.

But, you are right. The search panel is powerful but complex.
We have to find a solution for basic needs.
This post is really interesting and push me to work on the topic.

vicnet wrote:(the next step is to allow direct SQL as in debug view )

This could be a solution for very advanced users (like you) but risky (sql ingestion, check of the syntax).

vicnet wrote:Note: one can search on each page with list filtering. Moreover, with the column restricting option (a:xxx) and others options (+/-, next < > =...), it is easier/faster to search locally. But this is limited to one page.

You are right, with the new functionalities in "Search" fields. The "Find and process" panel is less interesting for the "Search" but is still interesting for "Update".
I don't understand your remark : "But this is limited to one page.". What do you mean?

vicnet wrote:
I will try to add some posts on complex search in different software...

a+
Vicnet

vicnet wrote:What I need, by complexity order (and also by usage frequency):

• simple search: of a text on all account and all column, not case sensitive
• simple search, on one specific column
• AND search, on multiple specific columns
• complex search, as current search

I think this is the good approach.
I will try to implement "simple search: of a text on all account and all column, not case sensitive".
May be based on full text search feature of SQLITE: http://sqlite.org/fts3.html

vicnet wrote:All with minimum number of click !

Remark: we can imagine to search on specific columns with simple text search (first usecase) and column restriction (a:xxx m:xxx) !
(same syntax as filtering)

Even if search is enhanced, it could fill/use the current search tool. to allow more complex search.
For example: enter account:xxxx in simple text search will fill current search page with Account criteria and 'contains xxxx ' property.

This could be possible, but difficult to translate in SQL (mapping between natural language and SQL columns, syntax errors, ...).

smankowski wrote:I don't understand your remark : "But this is limited to one page.". What do you mean?

Limiting to filtering in an already opened view.
If I want to use this to find something in all account and all operation, I have to display all operations (long long time) then filtering.

So simple text search, with or without columns restriction, is necessary to search without viewing all operations.

a+
Vicnet

smankowski wrote:

vicnet wrote:For example: enter account:xxxx in simple text search will fill current search page with Account criteria and 'contains xxxx ' property.

This could be possible, but difficult to translate in SQL (mapping between natural language and SQL columns, syntax errors, ...).

What is difficult:
* fill advanced search view with simple search
or
* column restriction
?

a+
Vicnet

vicnet wrote:

smankowski wrote:

vicnet wrote:For example: enter account:xxxx in simple text search will fill current search page with Account criteria and 'contains xxxx ' property.

This could be possible, but difficult to translate in SQL (mapping between natural language and SQL columns, syntax errors, ...).

What is difficult:
* fill advanced search view with simple search
or
* column restriction
?

* column restriction

vicnet wrote:a+
Vicnet

Hi Vicnet,

I started to work on this topic.
In fact, SQLite full text search is not my preferred solution.
I came back to your proposal and I implemented a function to translate a search condition (like this: "+comment:blabla -hello amout>50") in SQL.
This seems to be feasible.
I will take you informed of the progress.

Regards,
Stephane

Hi Vicnet,

I committed the "Simple" mode in "Search & Process".

Are you able to test it by building Skrooge?
If not, I can publish a beta version in my ppa.

Regards.

Thank again for your help and your ideas.

Hello,

I will not be able to test nor the git nor the ppa for a week.
(I cannot produce also a anonymous file for unit bug).

a+
Vicnet

I just do few tests no simple text search.
It seems to work, no bug found, just cosmetic considerations:
- operation columns name are not visible when entering column search restriction
so one should remember column name to use this functionality
should not be difficult but perhaps a pb sometime
=> add a button near edit text to help to add column restriction like in digikam (drop down list that add restriction)
http://scribblesandsnaps.com/2010/06/03 ... h-digikam/
(there is also a [i] button but don't remeber what's for...)
- advanced mode widget: I will not use checkbox, but a button >> or << or ^ or v (like in kate search green button at right)
could be a tab also
- simple mode display tooltip of advanced mode: 'double click on list...' but tip could not be applied

I did a new commit. Could you test it?