QML and Plasma -> progress()
Aaron J. Seigo
aseigo at kde.org
Thu Sep 16 18:12:44 CEST 2010
On Thursday, September 16, 2010, Marco Martin wrote:
> as i said, i don't think would really simplify the learning curve, because
> one would have to manage two "types" of javascript, with a difference
> between them that is quite an implementation detail (being on two engines)
is it possible to include() other JS scripts from a QML Plasmoid package?
because that's really what i'm most concerned about -> being able to use the
JS API we have now to drive the QML.
as for the engine not beign exposed, well .. i'm not surprised.
i have lost faith in the idea that QML development is in the hands of people
who are competent enough with design for it to ever be an unqualified success.
it will likely remain a land of promises half achieved and possibilities only
half realized. i expect it to be forked / re-written (using the same language)
at some point in the future with a reasonable API for developers using it.
it's QtMultimedia all over again: the same unwaranted bravado, the same
potential in the design ideas if not the implementation, the same evident
flaws that the developers are closing their ears to and therefore almost
certain to have the same kind of result due to that.
--
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43
KDE core developer sponsored by Qt Development Frameworks
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/plasma-devel/attachments/20100916/d477eae3/attachment-0001.sig
More information about the Plasma-devel
mailing list