Searching for a Calendar event now works perfectly.
I can search and find any text embedded in any 'Calendar' entry.
Although it takes exactly 4 min to search my 12 years of calender entries, quite OK, but slower than the old Palm device.
Selecting the calender entry, will display a 'screen capture' of the contents, (ie cannot be scrolled).
Yes the calendar entry view needs some more work. But you
can tap on the textfield and use the arrow keys to move the
cursor and the textfield will scroll.
Touching the 'Calendar' tab in this 'screen capture' will take you directly to the calendar event.
From there you can edit or scroll the contents. OK.
The search will also find any text embedded in a 'note' entry.
Selecting the note entry, will display a 'screen capture' of the contents, (ie cannot be scrolled).
Touching the 'Calendar' tab in this 'notes screen capture' will take you to a random calendar event,
but I wanted it to point to the searched 'note' item, not a calendar item.
Yes this is bad, but I can only open the calendar app with one
of three different views:
Month view,
Week view,
Agenda view.
It is not possible to jump directly to the notes list or to
the notes view. :-(
I hope the 'standard user' has not used calendar entries
from 12 years. Otherwise I have to think of some indexing
scheme.
Boah! From 12 Years? I guess this is not normal...
But you can ask me. As a common standard N900 user I had a look at my calendar and my oldest entry (expect the birthdays) is from 1999. But I have to wait under 1 Minute for the results. So I guess this extreme case with 12 years of meeting history has a little bit more entrys than I.
But in my opinion 12 years is not as long as it seems. I won't delete anything, too.
Hmm... I have 10 user defined Calendars, 2 of them are Smart Calendars. I use this as categories (private, work, appointments, Reminders, Birthdays, vataction planer, eCoach...).
Would you expect something valueable from the
results from the application search?
It shouldnt (if programmed correctly) return anything related because I doubt any application will have a name, description, etc with a phone number. It would just return SMSs with the number or/and contacts (in this case)
Tried the version that still crashed on conservations. That one took approximately 20 mb of my root memory.
I'll install the optified Scout version when it enters the extra testing repository, but can hardly wait.
No problem with root memory and Scout.
I guess it is because of the activation of EXTRA DEVEL at your device. (a lot of things are stored locally while updating the catalog - because of this it is so slow)
Simply deactivate EXTRA Devel and reboot your N900. Your lost memory will be there as before.
But I have to wait under 1 Minute for the results. So I guess this extreme case with 12 years of meeting history has a little bit more entrys than I. 
