On Tuesday, March 26, 2013 13:53:29 Alan Alpert wrote:
> > import org.kde.plasma.components 1.0 as...
> >
> > and import the "right" set, but the ideal way is (if we are importing
> > touch
> > components) to have a set of "just" the components that are rewritten for
> > touchscreen, while falling
On Tue, Mar 26, 2013 at 6:07 AM, Marco Martin wrote:
> On Tuesday 26 March 2013, Alan Alpert wrote:
>> Hi,
>>
>> I can't find it now, but there was a note on one of the Plasma wiki
>> pages about some of the limitations of how QML files are 'switched
>> out' with platform content versions in a Pla
On Tuesday 26 March 2013, Alan Alpert wrote:
> Hi,
>
> I can't find it now, but there was a note on one of the Plasma wiki
> pages about some of the limitations of how QML files are 'switched
> out' with platform content versions in a Plasma package (from memory,
> stuff like requiring a qmldir an
On Tuesday 26 March 2013, Alan Alpert wrote:
> Hi,
>
> I can't find it now, but there was a note on one of the Plasma wiki
> pages about some of the limitations of how QML files are 'switched
> out' with platform content versions in a Plasma package (from memory,
> stuff like requiring a qmldir an
Hi,
I can't find it now, but there was a note on one of the Plasma wiki
pages about some of the limitations of how QML files are 'switched
out' with platform content versions in a Plasma package (from memory,
stuff like requiring a qmldir and not working with C++ plugins).
I've chosen the longest
