Notes from "Async and representation"

[Martin Klapetek]

On Wed, Jan 15, 2014 at 4:43 PM, Mark Gaiser <markg85 at gmail.com> wrote:

>
> But why?
> What's the reasoning behind that?
>
> If you learn QML from scratch you start with:
> Item {
>   ...
> }
>
> or
>
> Rectangle {
>   ...
> }
>
> Or if you make a application to look native with the controls:
> ApplicationWindow {
>   ...
> }
>
> I don't think KDE should add another one:
> Applet {
>   ...
> }
>
> Sure, it works and probably serves a need that i don't fully see yet,
> but it also makes it less obvious for people starting developing
> plasmoids.
> They will first have to figure out how to call their root object and
> why it's not Item{} but Applet{}.
>

However, plasmoids are not "just QML", they are pieces of the shell and as
such I think it's perfectly fine it's a bit different - the whole purpose
of plasmoids is slightly different.

Also, related to that, that's why we need good docs and/or tutorial where
it is explained or simply pointed out. You /need/ to read docs to start
developing components of anything anyway, so imho introducing another
thing, different from plain QML, is perfectly fine :)

I hope you find my feedback valuable and not nitpicking :)


Every feedback is great, thanks for it ;)

Cheers
-- 
Martin Klapetek | KDE Developer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20140115/654d1dc9/attachment-0001.html>