On quarta-feira, 3 de julho de 2013 19.27.16, Sebastien Bacher wrote:
> Because when you use an environment, there is a good chance you want to
> write an application using the framework used there.
That's unrelated to the problem at hand, even if we assume that it is true.
The only use-case I c
On Wednesday, July 3, 2013 23:53:44 Sebastien Bacher wrote:
> Staying on the IDE example, if you have templates for 15
> languages/toolkits, you can either:
> - list the 15 in your context menus,
> - list none (e.g because you don't want to pick a preferred)
> - decide to put in front those you sel
On Wednesday, July 3, 2013 19:27:16 Sebastien Bacher wrote:
> Le 03/07/2013 17:29, Aaron J. Seigo a écrit :
> > in the specific example given, i really don't understand why a "start Qt
> > project" would have anything whatsoever to do with the shell.
>
> Because when you use an environment, there
I think this is getting a bit excessive. We don't need to enumerate every
single place a desktop environment should put actions, we should simply
specify that they should appear around the launcher in the specification.
And if an action appears in both the messaging menu and the launcher menu,
oh w
On Wednesday, July 3, 2013 10:15:45 Lars Uebernickel wrote:
> On 07/02/2013 06:09 PM, Ted Gould wrote:
> > The use case was two fold. First there was concern that some desktops
> > might not want to implement the actions or might implement them
> > differently. It's also possible that desktops co
On Wednesday, July 3, 2013 15:53:40 Sebastien Bacher wrote:
> (I don't have specific examples in mind, but I can see it being used for
> desktop specific features or e.g when different desktops have different
> design views on what items should be exposed in their UI ... imagine an
> IDE, you might
On Wed, Jul 3, 2013 at 9:53 AM, Sebastien Bacher wrote:
> Le 02/07/2013 23:54, Jasper St. Pierre a écrit :
>
>
>> I'm curious what the original rationale for adding OnlyShowIn /
>> NotShowIn to desktop actions. Personally, I think applications
>> switching behavior based on what desktop environme
On Wed, 2013-07-03 at 10:38 +0200, Aaron J. Seigo wrote:
> On Tuesday, July 2, 2013 20:48:55 Ryan Lortie wrote:
> > > or might implement them differently.
> >
> > This is a good point that I hadn't considered before. Maybe gnome-shell
> > would show them in a place that Transmission considered i
On 3 July 2013 09:38, Aaron J. Seigo wrote:
> On Tuesday, July 2, 2013 20:48:55 Ryan Lortie wrote:
> > > or might implement them differently.
> >
> > This is a good point that I hadn't considered before. Maybe gnome-shell
> > would show them in a place that Transmission considered inappropriate.
On Tuesday, July 2, 2013 20:48:55 Ryan Lortie wrote:
> > or might implement them differently.
>
> This is a good point that I hadn't considered before. Maybe gnome-shell
> would show them in a place that Transmission considered inappropriate.
Should the application care about this at all? I'd su
On Tue, 2013-07-02 at 17:54 -0400, Jasper St. Pierre wrote:
> Now that we're trying to implement desktop actions in GNOME, we're
> running into the issue that a lot of existing desktop actions are
> using OnlyShowIn / NotShowIn incorrectly. For a quick example,
> Transmission's actions are being ma
Now that we're trying to implement desktop actions in GNOME, we're running
into the issue that a lot of existing desktop actions are using OnlyShowIn
/ NotShowIn incorrectly. For a quick example, Transmission's actions are
being marked as only showing in Unity:
https://trac.transmissionbt.com/atta
12 matches
Mail list logo
