![]() |
2010-03-10
, 07:24
|
Posts: 10 |
Thanked: 4 times |
Joined on Jan 2010
@ Washington, DC
|
#31
|
![]() |
2010-03-10
, 08:02
|
Posts: 219 |
Thanked: 94 times |
Joined on Nov 2009
@ Helsinki, Finland
|
#32
|
The Following User Says Thank You to naabi For This Useful Post: | ||
![]() |
2010-03-10
, 08:55
|
Posts: 21 |
Thanked: 10 times |
Joined on Jan 2010
@ Madrid
|
#33
|
![]() |
2010-03-10
, 09:00
|
Posts: 12 |
Thanked: 13 times |
Joined on Feb 2010
|
#34
|
For battery usage we could implement an option to index only when connected to the power/USB cable.
But other OS/phones (like Iphone) have found the solution.
Indeed it is really strange that there is no Linux good search app like google desktop on windows platform and that no Guru programmer have coded something similar (even not so fast).
More over I don't understand why we don't take full use of the internal DB where are stored email, sms, contacts etc, making also a local search much more complete (example in company, notes field etc). We need more option to fully configure how and where we want to search.
The Following User Says Thank You to rivierakid For This Useful Post: | ||
![]() |
2010-03-10
, 09:07
|
Posts: 219 |
Thanked: 94 times |
Joined on Nov 2009
@ Helsinki, Finland
|
#35
|
Totally agree - Apple has it with iPhone and it's quite frankly possibly the *best* iPhone feature. How can Apple have found a way for instant search without killing the battery and the collective might of the open source community haven't?
The Following User Says Thank You to naabi For This Useful Post: | ||
![]() |
2010-03-10
, 09:15
|
Posts: 12 |
Thanked: 13 times |
Joined on Feb 2010
|
#36
|
It's also possible that all data pushed to device using iTunes is indexed by the the iTunes itself.
I guess for N900 the existing tracker is a good tool, but there's no point running two similar processes for global search and media indexing that already exists. Tracker has quite nice support for indexing file contents of different types of files. I have no idea how to add support for e.g. emails. Another issue is the somewhat outdated version of current tracker.
![]() |
2010-03-10
, 09:46
|
Posts: 219 |
Thanked: 94 times |
Joined on Nov 2009
@ Helsinki, Finland
|
#37
|
![]() |
2010-03-10
, 10:13
|
Posts: 247 |
Thanked: 91 times |
Joined on Jan 2008
@ London/M4 Corridor
|
#38
|
Hmmm. I can't believe that normal usage case (just from my hat) for indexing would occupy lots of resources. For first run surely, but if you put 5 documents and couple of songs daily. Instead lets say that you put 50 documents/emails daily and 100 songs then it could be problem.
The Following User Says Thank You to Alan_Peery For This Useful Post: | ||
![]() |
2010-03-10
, 10:30
|
Posts: 3,617 |
Thanked: 2,412 times |
Joined on Nov 2009
@ Cambridge, UK
|
#39
|
True, but you've implicitly assumed a much more complicated application. Rather than run a periodic sweep that simply scans files for strings, you have to first see that something has been changed (for all applications, however they store their data), and then index these changes. Oh, and remove the old references.
Editing the a contact and fixing Fred's last name, as you had incorrectly typed Fluntstone when you meant Flintstone, means that you have to have a model of individual records inside the contacts database, and be able to track down and remove all the old references. The app may not edit in place after all, Fred's new record number could be 123599, with the old record at 12012 marked as simply marked as old. Otherwise the othe fields ("Note: wife's name Wilma") that weren't changed would turn up Fred's old record.
The Following User Says Thank You to Rob1n For This Useful Post: | ||
![]() |
2010-03-10
, 10:37
|
Posts: 21 |
Thanked: 13 times |
Joined on Oct 2009
|
#40
|