Re: Introducing components, how to

2011-11-10 Thread Marco Martin
On Wednesday 09 November 2011, Ivan Čukić wrote: > >> [Components-platform] > >> name=touch > > > > something Sune just noted to me.. > > maybe an environment variable would be better to chose this? > > As on override? For that, I'd say +1, otherwise -1 :) i added KDE_PLASMA_COMPONENTS_PLATFORM

Re: Introducing components, how to

2011-11-09 Thread Ivan Čukić
>> [Components-platform] >> name=touch > > something Sune just noted to me.. > maybe an environment variable would be better to chose this? As on override? For that, I'd say +1, otherwise -1 :) -- Cheerio, Ivan -- While you were hanging yourself on someone else's words Dying to believe in what

Re: Introducing components, how to

2011-11-09 Thread Marco Martin
On Wednesday 09 November 2011, Marco Martin wrote: > When writing a widget, an application etc, just use > import org.kde.plasma.components, the proper one is decided by the > kdeclarativerc file, if it has > [Components-platform] > name=touch something Sune just noted to me.. maybe an environment

Introducing components, how to

2011-11-09 Thread Marco Martin
Hi all, sending here as well after plasma-devel and active there is still some work to do, but the components are almost done in their final structure (good for the upcoming freeze, ehehe :) components are imported with: import org.kde.plasma.components regardless of the platform we're in. We