The idea seems interesting.
On the other hand, things like gnome-control-center, lxqt-config and
other 'control-center'-ish apps are just showing a filtered list of
settings-related applications which in turn described by their
*.desktop entries.
Perhaps, refining categories for desktop files could accomplish the
task. So, for example, a tool to configure networks could be
properly labeled so in its desktop entry to be later properly
filtered and presented when needed.
Also, related concept: https://github.com/lxde/lxqt/issues/580
2016-01-16 03:12, Corentin Noël пишет:
Le 16 janv. 2016 1:03 AM, "Mattias Andrée" <[email protected]>
a écrit :
>
> Okay, so it is not fatal. But why do you need it?
> I think it is important not to introduce a bunch of
> standards just for completeness's sake, only if they
> are actually needed.
I actually need it in several places in the OS, in our
indicators we have links to settings panel, in settings panels
themselves we have crosslinks to other panels and in some of our
apps we tell the user to add an account to the online accounts
panel and give a button to open it. We also could use it in our
web browser to ask the user to check his connectivity...
>
> On Sat, 16 Jan 2016 00:57:36 +0100
> Corentin Noël <[email protected]>
wrote:
>
> > Le 16 janv. 2016 12:53 AM, "Mattias Andrée"
> > <[email protected]>
a écrit :
> > >
> > > Why would this be useful? And what about when
none of
> > > these are implemented, would that be a problem?
> >
> > It's then the same problem as clicking on an URL when
you
> > don't have any web browser. Nothing will happen, your
> > users will complain as "not working", but it the same
if
> > you hardcode things for unity-control-center and you
only
> > have gnome-control-center installed.
> >
> > >
> > > On Sat, 16 Jan 2016 00:28:37 +0100
> > > Corentin Noël <[email protected]>
wrote:
> > >
> > > > Hi everyone,
> > > > Many desktop environments have their own
System
> > > > Settings applications, but there is no clear
way for
> > > > developers to call settings from within
their
> > > > applications without resorting to
hardcoding in
> > > > commands for each and every Settings app. I
propose a
> > > > new specification that similar to other
scheme
> > > > handling in Desktop files, through a new
settings://
> > > > URI. With this, developers could call on
Settings
> > > > applications, without resorting to
hardcoding,
> > > > provided a desktop environment supports it.
For
> > > > example, an application calling
settings://bluetooth
> > > > would open Bluetooth settings for a given
desktop
> > > > environment.
> > > >
> > > > Here is the specification I propose:
> > > >
> > https://docs.google.com/document/d/1N0uqNtVXEFn3cLgNMeN75mP_dpMpCco-7uw5PKow-_Q/edit?usp=sharing
> > > >
> > > > I'm of course open to changes and feedbacks,
> > > > Corentin Noël
> > > > elementary OS Developer
> > >
> > >
> > > _______________________________________________
> > > xdg mailing list
> > > [email protected]
> > > http://lists.freedesktop.org/mailman/listinfo/xdg
> > >
>
_______________________________________________
xdg mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/xdg
|
_______________________________________________
xdg mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/xdg
