> That's interesting... I am definitely "old-fashioned" in this respect. The > difference between "search" and "sort" is for me that with the "sort" > someone already put some time into trying to put some sense into > unstructured information. For example, with an index, someone already tried > to group the really relevant information together, guiding you to the heart > of the matter rather than to some useless location where a term is > mentioned. The same with a table of contents. That's why people still buy > books (I would by a qooxdoo book, BTW ;-) ). The "search" strategy, which I > use myself a lot, means that you are doing the categorization work again and > again, for each little piece of information that you're after, with less > knowledge than the one who would be designing the "sort" strategy. "Search", > for me, is always a fallback strategy that is much less efficient.
Nicely put. For me, I'm far less a "words" person. If I search for something it's usually much harder for me to come up with a search term (a word), rather than a "location" where it is likely to be found. I remember the "places" where I saw things, rather than the words expressing them. Therefore, structure, context and paths are more critical to me than clever search facilities. Thomas ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
