<div>Just to clarify this: </div><div><br></div><br><div class="gmail_quote">On Sun, May 29, 2011 at 2:27 PM, Francesco Nwokeka <span dir="ltr"><<a href="mailto:francesco.nwokeka@gmail.com">francesco.nwokeka@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 Sunday 29 May 2011 14:54:30 Lukas wrote:<br>
> Hi Francesco,<br>
><br>
> Just to clarify:<br>
> a) The presence and contacts MUST be a separate plasmoids?<br>
</div>Yes<br>
<div class="im"><br>
> b) The it could be a unified plasmoid, but contacts is too much of overhead<br>
> for first version?So what that means in reality is that we have to make both the dataengine _and_ the plasmoid. Fortunately we only need to do the dataengine side once. Another issue is that we are developing for plasma2, which is a bit less documented. <br>
</div>No, I want to keep the two things seperate and break down jobs as much as possible.<br>
<div class="im"><br></div></blockquote><div>Nwoki has a plan for GSOC in which he makes two plasmoids (well 3 IIRC), as it's GSOC we've had to make these plans quite far in advance, and we're not going to change things just on a whim.</div>
<div> </div><div>This isn't in any way ruling out there ever being a combo plasmoid. With both implemented it would be ridiculously easy to do.</div><div><br></div><div>(in fact as you clearly know JS, you could do it yourself in not very long)</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">
> Just curious, as if I had to develop such contacts part/plasmoid for web<br>
> application, it to get it done 90%, it would be less than 1-2 days with 300<br>
> lines of code combined of CSS/JavaScript/and some server side scripting,<br>
> all with use of frameworks.</div></blockquote><div> </div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">
> Is developing for plasma more difficult? Does<br>
> telepathy make use of plasma data engines, or data should be fetched from<br>
> daemon directly?<br>
</div>Telepathy doesn't make use of dataengines, but the plasmoids do.<br>
<br></blockquote><div><br></div><div>So what that means in reality is that we have to make both the dataengine _and_ the plasmoid in order to get something that works. Fortunately we only need to do the dataengine side once. Another issue is that we are developing for plasma2, which is a bit less documented. </div>
<div> </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
The plasmoids for kde-telepathy are a project of mine for this year's google summer of code. So<br>
development of these components will be passing through me.<br>
<div class="im"><br>
><br>
> Cheers,<br>
> Lukas<br>
><br>
> > Hi Ben,<br>
> ><br>
> > I appreciate your work. But as I said, in a previous mail, the<br>
> ><br>
> > PRESENCE plasmoid will display<br>
> > info related to account presence. The contactlist is to be seen as<br>
> > another seperate plasmoid. We've<br>
> > already got some good ideas for the contact list so please wait to see<br>
> > the first layout before doing<br>
> > extra work on it. I'll definatly consider your mockups and ideas :)<br>
> ><br>
> > Francesco<br>
</div><div><div></div><div class="h5">_______________________________________________<br>
KDE-Telepathy mailing list<br>
<a href="mailto:KDE-Telepathy@kde.org">KDE-Telepathy@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kde-telepathy" target="_blank">https://mail.kde.org/mailman/listinfo/kde-telepathy</a><br>
</div></div></blockquote></div><br>