On 5/7/08, Eben Eliason <[EMAIL PROTECTED]> wrote: > On Wed, May 7, 2008 at 11:04 AM, Mikus Grinbergs <[EMAIL PROTECTED]> wrote: > > In summary, I am concerned that by disallowing filtering (when using > > Journal) by arbitrary metadata properties, you will take away the > > freedom of __kids__ to explore/create "virtual database schemes". > > I think 'flexibility' for the user is worth the performance penalty. > > I do still think this is a really strong feature that we should try to > preserve if possible. We've lost the notion of "sort by, then by, > then by" for now, but it really could completely change the utility of > the Journal for those that choose to take advantage of such a feature > if we add it later. > > On a simpler note, I really do believe we have to offer metadata > search as well. Typing in activity:write should return all instances > of the Write activity. Typing pages:2 should return every two page > essay I wrote. Typing in artist:beatles should return every song by > them. Etc. Even things like haskey:my_arbitrary_category_key, > backed-up:true, etc. could be useful. I think exposing arbitrary > metadata for search purposes will really encourage kids to use the > Journal as an organizational tool if they so desire.
Ok, I agree with you. Also, supporting filtering/sorting by any metadata field will be very important when we try to "sell" a future datastore to linux desktops other than Sugar. Thanks, Tomeu _______________________________________________ Devel mailing list [email protected] http://lists.laptop.org/listinfo/devel
