GTG

Add search and save search views

Bug #487108 reported by Nukeador
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
GTG
Confirmed
Wishlist
Unassigned

Bug Description

It would be nice to have a search function and also been able to save the searches (related to bug #410822)

Changed in gtg:
importance: Undecided → Wishlist
status: New → Confirmed
Revision history for this message
Lionel Dricot (ploum-deactivatedaccount) wrote :

Bertrand, maybe you could post your mockup on this bug

Changed in gtg:
milestone: none → 0.3
Revision history for this message
Luca Invernizzi (invernizzi) wrote :

How about the "quick add" searches also? That is, it searches while you type, and it adds a new task when you press enter (maybe asking you if there is still a task in the search)

Revision history for this message
Pititjo (jonathan-barnoud) wrote : Re: [Bug 487108] Re: Add search and save search views

I think the two approach, GUI and quickadd, are both useful. I think we
should be able to do almost every thing in GTG from the quiadd entry but
a GUI to the search feature allow non advance user to use it.

If the architecture behind the search tool is good designed the two
approach should use almost the same code.

Le lundi 28 décembre 2009 à 07:50 +0000, Luca Invernizzi a écrit :
> How about the "quick add" searches also? That is, it searches while you
> type, and it adds a new task when you press enter (maybe asking you if
> there is still a task in the search)
>

Revision history for this message
Luca Invernizzi (invernizzi) wrote :

sure. Also, the guy could have more options, like the ability to save searches mentioned before

Revision history for this message
Jeff Fortin Tam (kiddo) wrote :

as long as it has good performance (ie: works without lagging on an
netbook's Atom processor). It shouldn't run the search for every
character that I type, unless it is *very* efficient. And it shouldn't
run the search if the query string has <4 characters.

Revision history for this message
Pititjo (jonathan-barnoud) wrote :

I agree. If we keep Luca's view, which is a good one, the update for
each character should be optional. I use GTG on a netbook and typing a
new subtask is not as fast as it should because of the refresh at each
characters.

Le lundi 28 décembre 2009 à 15:46 +0000, Jean-François Fortin Tam a
écrit :
> as long as it has good performance (ie: works without lagging on an
> netbook's Atom processor). It shouldn't run the search for every
> character that I type, unless it is *very* efficient. And it shouldn't
> run the search if the query string has <4 characters.
>

Revision history for this message
Jeff Fortin Tam (kiddo) wrote :

@Pititjo regarding the subtask performance, see Bug #476477

Changed in gtg:
milestone: 0.3 → 0.4
Revision history for this message
pt123 (pt123) wrote :

Search feature would be so useful, after using GTG many tasks build up in completed tasks, and rather than recreating the task it would be better to reactivate it.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.