Re: application class thoughts

On Mon, Apr 5, 2010 at 5:02 PM, Ted Gould <ted gould cx> wrote:
> On Mon, 2010-04-05 at 11:16 -0400, Colin Walters wrote:
>> The most important thing is to implement the application menu,
>> offering at least global options like Quit, New Window, About.  And we
>> want to experiment with moving e.g. Copy&Paste in there, which could
>> get us to the point where basic applications wouldn't need a
>> per-window menu.
> For the messaging menu in Lucid we did a little bit of work similar to
> this, just the menu, not solving any of the other problems you've
> listed.  The design goal was to allow applications a way to provide
> commonly used messaging functions directly in the menu both when running
> and not (which many not entirely overlap with your use case).  Though,
> they don't have to be the same items, it would seem that for most
> applications you'd want the running set to be larger than the static
> set.
> The way that the static items work is by basically the Nautilus actions
> style of adding groups, but it's much much simpler.  We only have Name,
> Exec, and ShowIn.

Can you link me to some code/specs for this?

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]