2007/5/21, jamie <<a href="mailto:jamiemcc@blueyonder.co.uk">jamiemcc@blueyonder.co.uk</a>>:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Mon, 2007-05-21 at 14:56 -0400, Joe Shaw wrote:<br>> Hi,<br>><br>> On 5/21/07, Evgeny Egorochkin <<a href="mailto:phreedom.stdin@gmail.com">phreedom.stdin@gmail.com</a>> wrote:<br>> > Not sure what you mean by "knowing how to display",
<br>><br>> Simply that code has to exist which pulls specific information<br>> provided and displays it in an optimal way. For instance, displaying<br>> some sort of widget for a "person" rather than a URI.
<br>><br>> It must also know how to filter information so that a user isn't<br>> overwhelmed. For a person, inundating the user with all possible<br>> information about that person in little more than a key-value format
<br>> isn't useful. Otherwise we might as well just be displaying the FOAF<br>> file itself and not bothering to parse it. :)<br>><br>> > but when app encounters meta-data outside of the core or known onto, it has
<br>> > to deal with it nevertheless.<br>><br>> Beagle's policy has always been to drop this information, actually.<br>> If we can't present it sanely to the user, it probably won't be useful<br>
> to them. (There is also the conscious decision that Beagle is just a<br>> search tool -- it largely provides information "at a glance" to the<br>> user; if they want details, another application is better suited than
<br>> we could ever be.)<br>><br>> > The more structured the onto is, the more opportunities the app<br>> > has to present/process the data properly.<br>><br>> Sure, but doesn't the app have to know about this?
<br><br><br>not really. Tracker is moving away from hard coding stuff like this so<br>that it can handle custom services with a tile based gui without a<br>priori knowledge or any hardcoding.<br><br>EG see our service def files (note the TileMetadata fields!)
<br><a href="http://svn.gnome.org/viewcvs/tracker/trunk/data/services/default.service?view=markup">http://svn.gnome.org/viewcvs/tracker/trunk/data/services/default.service?view=markup</a></blockquote><div><br><br>You mean by imposing a UIView and UIVisible property on each field and/or category i take it..?
<br><br>I can't really grok what the UIView property means...<br><br>Cheers,<br>Mikkel<br></div></div>