On Fri, 11 Aug 2006 09:17:15 +0900 Carsten Haitzler (The Rasterman) <email@example.com> wrote: > On Fri, 11 Aug 2006 09:45:31 +1000 David Seikel <firstname.lastname@example.org> > babbled: > > > On Fri, 11 Aug 2006 08:01:33 +0900 Carsten Haitzler (The Rasterman) > > <email@example.com> wrote: > > > > > On Fri, 11 Aug 2006 08:07:56 +1000 David Seikel > > > <firstname.lastname@example.org> babbled: > > > > > > > On Thu, 10 Aug 2006 23:13:50 +0900 Carsten Haitzler (The > > > > Rasterman) <email@example.com> wrote: > > > > > > > > > i can be tipped to ecore given some arguments :) but as i > > > > > said - > > > > > > > > Arguments to tip you to ecore_desktop_* for the parsing code - > > > > > > ok- make it an ecore_fdo blob (ecore_fdo sounds good? or > > > ecore_xdg?) :) > > > > I thought about that. This is not the only fdo spec that we now, > > or might in the future, support. The other specs may or may not > > want to be covered by ecore_fdo, as their specs cover all sorts of > > different things. Xdg also covers all the other fdo specs. I think > > ecore_desktop is best, as this code deals with all the .desktop > > related stuff. > > hmm - so you plan on covering the fdo menu spec elsewhere? Nope, the fdo menu spec is ".desktop related stuff", it deals with pulling together all those .desktop files into a menu. So it also goes into ecore_desktop.
Description: PGP signature