Re: QML-using app developers: use private.* imports

2013-09-25 Thread Sebastian Kügler
Hola, On Thursday, September 26, 2013 02:23:31 Aleix Pol wrote: > Reducing API to maintain is a good thing, at least for complexity sake. But > of course there will be always the case where somebody needs (part of) the > private API. > > The question would be then, why is it that there's some API

Re: QML-using app developers: use private.* imports

2013-09-25 Thread Aleix Pol
On Wed, Sep 25, 2013 at 3:51 PM, Sebastian Kügler wrote: > Hey all, > > In Plasma, we've been looking into privatizing parts of the QML API we > offer. > With Qt5, we rely less on setContextProperty() and friends, and use imports > more. That's a technical necessity that makes one problem more ev

Re: QML-using app developers: use private.* imports

2013-09-25 Thread Sebastian Kügler
On Wednesday, September 25, 2013 17:51:41 Mark wrote: > Doesn't your naming proposal completely ruin the org.kde.* stuff? Up until > now i could fairly safely assume that all QML KDE imports where hidden > under org.kde.* but that isn't the case anymore if you introduce > private.org.kde.* That's

Re: QML-using app developers: use private.* imports

2013-09-25 Thread Ivan Čukić
> hidden under org.kde.* but that isn't the case anymore if you > introduce private.org.kde.* >From my POV, Sebastian's proposal is spot-on for that reason alone - it is not a (public) 'qml kde import'. It is a private thing. Cheerio, Ivan p.s. and, in all honesty grepping for org.kde will retur

Re: QML-using app developers: use private.* imports

2013-09-25 Thread Mark
On Wed, Sep 25, 2013 at 3:51 PM, Sebastian Kügler wrote: > Hey all, > > In Plasma, we've been looking into privatizing parts of the QML API we > offer. > With Qt5, we rely less on setContextProperty() and friends, and use imports > more. That's a technical necessity that makes one problem more ev

Fwd: looking for phonon gstreamer maintainer

2013-09-25 Thread Harald Sitter
-- Forwarded message -- From: Harald Sitter Date: Mon, Sep 23, 2013 at 4:55 PM Subject: looking for phonon gstreamer maintainer To: "For discussion of multimedia (sound/video) issues under KDE" Ahoy, since everyone who ever was/is/wanted to be Phonon GStreamer maintainer is eit

Re: how to add or modify, keyboard layouts: us(intl) hebrew-phonetic

2013-09-25 Thread Andriy Rysin
To change the layout you need to file a suggestion for xkeyboard-config at bugs.freedesktop.org For the local change, if you're sure you did the change in the right place you can try to clear the cache files in /var/lib/xkb/ Andriy 2013/9/25 Thiago Macieira : > On quarta-feira, 25 de setembro de

Re: how to add or modify, keyboard layouts: us(intl) hebrew-phonetic

2013-09-25 Thread Thiago Macieira
On quarta-feira, 25 de setembro de 2013 16:08:44, Uwe Brauer wrote: > Can somebody please provide me with advice or tell me where to ask? The X.org development list. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel Open Source Technology Center

how to add or modify, keyboard layouts: us(intl) hebrew-phonetic

2013-09-25 Thread Uwe Brauer
Hello I am not sure this is the right list to ask (or whether it should be a more general one X.org or so). I would like to propose one change in the us keyboard variant international (or to add a new keyboard us (intl2) with the modification) I propose that "s --> ß The relevant configuration

QML-using app developers: use private.* imports

2013-09-25 Thread Sebastian Kügler
Hey all, In Plasma, we've been looking into privatizing parts of the QML API we offer. With Qt5, we rely less on setContextProperty() and friends, and use imports more. That's a technical necessity that makes one problem more evident: It's unclear what QML-facing API is reliable and stable, and