Ryan Lortie desrt at desrt.ca writes:
My problem with these proposals is that schema and id are the
natural names to use here and that people will find a lot of online
help instructing them about that.
What about adding a versioning attribute to the toplevel element:
schemalist
On Wed, Oct 17, 2012 at 12:29 PM, Ryan Lortie de...@desrt.ca wrote:
From a purely aesthetic standpoint I guess I could accept schema
name=''...
Then we could have
schema name='a.b.c'/
schema name='x.y.z' relocatable='yes'/
and throw warnings if we ever see id=''... We could keep
On the more extremist side of my point of view:
https://lkml.org/lkml/2012/3/8/495 }:-)
From a more reasonable standpoint, expecting app developers to keep up with
every single library's changes is bad, specially for something so
fundamental as GLib/GIO. I do think it's unfortunate, but I think
hi,
One of the big design mistakes I made with GSettings is that this is
really weird:
schema id=org.a11y.atspi path=/org/a11y/atspi/
The requirement to specify a separate path is confusing. It causes
people to think that maybe the path should have a prefix like /apps/.
If you manage to
On Wed, Oct 17, 2012 at 12:02 PM, Ryan Lortie de...@desrt.ca wrote:
In this way we turn:
schema id='a.b.c' path='/a/b/c/' !-- common case --
schema id='x.y.z' !-- uncommon case --
to:
schema id='a.b.c' !-- common case --
schema
On 12-10-17 12:17 PM, Matthias Clasen wrote:
to
fixedschema id='a.b.c'
relocatableschema id='x.y.z'
Seb mentioned a variation on this theme focusing on attribute names instead:
schema pathid=... !-- same as fixedschema above --
My problem with these proposals is that schema and
Le 17/10/2012 18:02, Ryan Lortie a écrit :
Even if we don't do #2, I think doing #1 might be useful. I don't
have any evidence (even anecdotal) to support the idea that the
current situation is confusing but it seems that a helpful warning
explaining to the user that schema id='a.b.c'
On 17/10/12 18:02, Ryan Lortie wrote:
hi,
One of the big design mistakes I made with GSettings is that this is
really weird:
schema id=org.a11y.atspi path=/org/a11y/atspi/
The requirement to specify a separate path is confusing. It causes
people to think that maybe the path should have
