<div dir="ltr">On Fri, Oct 17, 2008 at 9:45 PM, C. Scott Ananian <span dir="ltr"><<a href="mailto:cscott@laptop.org">cscott@laptop.org</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Fri, Oct 17, 2008 at 3:36 PM, Erik Garrison <<a href="mailto:erik@laptop.org">erik@laptop.org</a>> wrote:<br>
> Perhaps we could also investigate the use of the xdg utilities for<br>
> managing mimetype associations and installing activities?<br>
<br>
</div>Good point. I've talked with sugar folk about this some already. My<br>
Journal2 code is going to use the GIO app launching mechanism, which<br>
is based on XDG, and sugar already uses XDG mechanisms to register<br>
mime types. Michael's already been thinking about how we can<br>
interpose rainbow-launch into app launching, which is not inconsistent<br>
with the XDG mechanisms. I think we've been a bit unsatisfied with<br>
how XDG scatters information about activities across the filesystem<br>
(mime types here, .desktop files there, etc); Sugar prefers the "all<br>
information related to an activity in a single directory" model,<br>
pioneered by NextSTEP and used in Mac OS X, etc. I think that can be<br>
made consistent with the XDG mechanisms, either by using a very long<br>
XDG_DATA_DIR spec which lists all the activity directories, or by<br>
using a userland filesystem to generate the proper XDG directory<br>
contents based on the activity registry. I should flesh this out and<br>
we'll deal with the details during the presentation.<br></blockquote><div><br>The way it's done right now is to copy mime information to ~/.local at installation time. <br></div></div><br>Marco<br></div>