On Wednesday, November 09, 2011 21:01:16 Martin Gräßlin wrote:
On Wednesday 09 November 2011 20:05:00 Marco Martin wrote:
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
On Wednesday, November 09, 2011 03:31:46 PM Marco Martin wrote:
Hi all,
there is still some work to do, but the components are almost done in their
final structure (good for the upoming freeze, ehehe :)
components are imported with:
import org.kde.plasma.components
regardless of the
On 11/09/2011 07:31 PM, Marco Martin wrote:
Hi all,
there is still some work to do, but the components are almost done in their
final structure (good for the upoming freeze, ehehe :)
components are imported with:
import org.kde.plasma.components
regardless of the platform we're in.
We have
Hi all,
there is still some work to do, but the components are almost done in their
final structure (good for the upoming freeze, ehehe :)
components are imported with:
import org.kde.plasma.components
regardless of the platform we're in.
We have at the moment 37 widgets in the touch profile,
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
On Wednesday 09 November 2011 20:05:00 Marco Martin wrote:
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]