Notes from "Async and representation"

[Marco Martin]

On Wednesday 15 January 2014 16:43:43 Mark Gaiser wrote:

> As for the Applet name. Why that name? I'm making a plasmoid, right?
> So name it as such:
> Plasmoid {
>   ...
> }
> 
> That is also easier to explain to a user:
> "To create a plasmoid you have to create a root QML item named
> Plasmoid { ... } which must contain the following properties ... bla
> bla, you get the point."

i would call it Plasmoid if i can merge it with the plasmoid object, that is 
now an object registered in the root context. i'm not sure it's possible, 
would like to tough.

> 
> Then yet another note.
> You say users must provide a:
> minimumWidth: ...
> minimumHeight: ...
> 
> which is being defined in the root item (whatever it ends up being).
> But why there? I mean, the compactRepresentation and
> fullRepresentation are likely to have their own different minimal
> width/height. It "could" be the same, yes. But it could also be wildly

good point, compactRepresentation and fullRepresentation should export those 
as attached properties, and the root object should not.

> the smallest minimal (likely compactRepresentation) but then it's just
> a bogus value for the other one (likely fullRepresentation).
> 
> 
> I hope you find my feedback valuable and not nitpicking :)

all feedback is ;)

-- 
Marco Martin