<br><br><div class="gmail_quote">On Tue, Jul 27, 2010 at 11:52 PM, Marco Martin <span dir="ltr"><<a href="mailto:notmart@gmail.com">notmart@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Tuesday 27 July 2010, Aleix Pol wrote:<br>
<br>
> > > Here I guess that the<br>
problem would be that when restoring I wouldn't<br>
> > > get that argument and<br>
I would be lost again.<br>
> ><br>
> > yes. personally, i'd suggest you provide a<br>
built-in dataengine that the<br>
> > applets can connect to. set the project id<br>
in the dataengine, all the<br>
> > applets<br>
> > will get notified when that<br>
happens.<br>
><br>
> Hmmm... fair enough. I'll try that.<br>
<br>
</div>+1, that one would be the<br>
best way i think<br>
alternatively also setting a property on the applets could<br>
work... would prefer the dataenine tough<br>
<div class="im"><br>
> Would it be possible to get what<br>
Corona/Containment is going to receive the<br>
> new Applet instance in<br>
internalLoadApplet reimplementation?<br>
><br>
<br>
</div>you mean connecting to<br>
containment::appletAdded()? or the other way around?<br></blockquote><div>I mean knowing from the pluginloader what container is going to receive the applet</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
<br>
Cheers,<br>
<font color="#888888">Marco Martin<br>
</font><div><div></div><div class="h5">_______________________________________________<br>
Plasma-devel mailing list<br>
<a href="mailto:Plasma-devel@kde.org">Plasma-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/plasma-devel" target="_blank">https://mail.kde.org/mailman/listinfo/plasma-devel</a><br>
</div></div></blockquote></div><br>