On Mon, Nov 7, 2011 at 1:09 AM, Florian Müllner <fmuell...@gnome.org> wrote:

> On lun, 2011-11-07 at 00:23 +0100, Seif Lotfy wrote:
> >
> > On Mon, Nov 7, 2011 at 12:10 AM, Florian Müllner <fmuell...@gnome.org>
> >
> >         To me it means that the application is in control of what
> >         appears in the
> >         jumplist, not necessarily that it is responsible for
> >         specifying the
> >         exact set of items. So I can imagine some "gnome-recent-items"
> >         action
> >         which is translated appropriately by the shell if included in
> >         the .desktop file, but I would not expect anything in the
> >         jumplist if
> >         the application does not specify anything.
> >
> >
> > However if the app doesn't specify a list why not have a fallback
> > option.
> > Mostly you will end up using it in cases like gedit, rhythmbox, totem,
> > epiphany and event documents. In that case I suggest the usage of
> > zeitgeist and not gtk.recentmanager. Since such lists are dynamic i
> > don't find it appropriate to keep updating the .desktop file with
> > recently/most used every time the app is used. If apps really would do
> > that I would suggest them push directly into zeitgeist.
>
>
> I did not suggest updating the .desktop file, I suggested "special"
> actions applications could specify to request certain content, for
> instance a list of recent items. (Obviously that would only be step
> three, after deciding whether the feature is wanted and implementing the
> basic functionality).
>
>
Fair enough :)


>
> Florian
>
>
_______________________________________________
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list

Reply via email to