CintaNotes Developer wrote:I agree that it might have a better usability. But there are two problems to solve here:
I understand your design decisions. Each user has different requirements also. To me the implementation is very technical. The design requires to store empty searches (reset search), to be able to show the delta. But this is extra information i don't care. I don't want to step back to "reset search". I can reset any time using Ctrl+F if i like to. I prefer a list of search results (absolute information) rather than a list of deltas (relative information).
CintaNotes Developer wrote:1) How to represent all filters in each history item without it becoming too long and bulky. Imagine, for example, it being represented like this:
"Tags: Projects/Todo/Tomorrow Projects/Todo/NextWeek -Archive/Done; Search: blog javascript ; Sort by: Last modified first".
I use a 30" screen, no problem to me
My practice is though very different. Usually it just takes 1-3 words of searching to find the desired notes. In rare cases i actually use a tag filter. I never change sorting. Others might use search differently though.
A history of mine could be:search for 'javascript blogs'
search for 'CintaNotes beta'
search for 'Ubuntu shortcuts'
This also brings up the request to have a shortcut to the history. Especially this makes sense if there would be only one history, rather than two for backward/forward.
CintaNotes Developer wrote:2) How to make things that change between two history states stand out. Compare with the history item above:
"Tags: Projects/Todo/Tomorrow Projects/Todo/NextWeek -Archive/Done; Search: blogs javascript ; Sort by: Last modified last".
Your example is fine as it is! I can see the difference if i look at it. Maybe the information can be shortened to gain a better oversight.
Your suggestion:"Tags: Projects/Todo/Tomorrow Projects/Todo/NextWeek -Archive/Done; Search: blog javascript ; Sort by: Last modified first".
Alternatives:"blog javascript" in (Projects/Todo/Tomorrow Projects/Todo/NextWeek -Archive/Done)
blog javascript (Projects/Todo/Tomorrow Projects/Todo/NextWeek -Archive/Done)
Maybe it is important for the sort order to take part in the history, but do we actually need to show it? In that case we would have the same entry twice, because it can not be distinguished (so what?).
Sort Alternatives:"blog javascript" in (Projects/Todo/Tomorrow Projects/Todo/NextWeek -Archive/Done) [Last modified first]
blog javascript (Projects/Todo/Tomorrow Projects/Todo/NextWeek -Archive/Done) [Last modified last]
Thomas
[EDIT 03.10.2014 00:26]
Sort Alternatives:"blog javascript" in (Projects/Todo/Tomorrow Projects/Todo/NextWeek -Archive/Done) [LAST MODIFIED]
blog javascript (Projects/Todo/Tomorrow Projects/Todo/NextWeek -Archive/Done) [last modified]