<div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">---------- Messaggio inoltrato ----------<br>From: Yuen Hoe Lim <<a href="mailto:yuenhoe86@gmail.com">yuenhoe86@gmail.com</a>><br>
To: <a href="mailto:plasma-devel@kde.org">plasma-devel@kde.org</a><br>Date: Tue, 2 Feb 2010 18:12:03 +0800<br>Subject: Re: plasmate alpha1 release<br>Hi guys,<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
would it be reasonable to try for an alpha release with:<br>
<br>
* tagging on the 8th<br>
* release on the 10th, assuming the tagging goes well<br></blockquote></div></blockquote><div><br>Good for me too, so we can start recieving feedbacks from the users :) <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"></blockquote><div><br>Sounds awesome! I'm not sure what kind of quality would be expected of alpha software though :P<br>
</div></div></blockquote><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="gmail_quote"><div>Some of my questons/concerns about the present state of PlasMate are as follows:<br>
<ul><li>AFAIK we are only (more or less) good to go for Plasmoids. I think runners et al don't quite work. Do we "hide" those options for now? :P</li></ul></div></div></blockquote><div>Hiding its not a good idea, i did it this summer and they told me to not do that; btw i agree with your idea to do something for that :)<br>
We need to add a dataEngine and runner templates in Javascript, as well a runner template written in ruby but, up to now, i didn't find any example in order to write good templates fot that. Hints ?<br>And theme support is still unavailable, in this current state.<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="gmail_quote"><div><ul><li>Likewise we currently have some UI stubs for unimplemented features (eg. Publish to GHNS), "hide" those too?</li>
<li>I haven't really been testing the timeline, and now that I tried it, it doesn't seem to work right =( Am I not using it correctly? Or is it bugged? Diego could you check? :P</li></ul></div></div></blockquote>
<div>If you would be more detailed, I'll be glad to help you :) <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="gmail_quote">
<div><ul><li>I can't seem to create a configuration dialog for my (Python) plasmoid in PlasMate. I used to override showConfigurationInterface(), but that doesn't seem to work while using PlasMate. As long as I set hasConfigurationInterface to True and have the "User Interface" folder empty, the plasmoid always crashes when I attempt to view the configuration interface (right-click > settings). IIRC you're supposed to put QtDesigner-generated ui files in "User Interface", if so, does it make sense to release now when there's no QtDesigner integration? Or we just leave the configuration interface to "future work"?<br>
</li><li>Additional, non-urgent point following from the last: crashing the plasmoid crashes PlasMate. This doesn't seem right, but I've no idea how to fix it at this point.</li></ul>What do you all think? If we could solve/get around these then for my part I think we're good :)<br>
</div></div></blockquote><div><br>Agree.<br>Furthermore, IMO, we should make PlasMate project-centric, for a couple of reasons:<br><br>*regardless the type of project started/opened, plasmate now loads the last layout saved ( moreover, the layout is not resetted when changing project in the same plasmate session ). Therefore, if we were developing a plasmoid with the previewer visible, and then we change to a dataengine project to fix a bug ( or if we start plasmate and open a dataengine project, when the last project developed was a plasmoid with the previewer on ), the user will see the previewer even if there is no reason on showing a preview for a dataengine;<br>
<br>*for each project, we could save the last modified file, and show it the next time the project will be opened again;<br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="gmail_quote"><div>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
we should have a release plan from that point forward as well. how about:<br>
<br>
* a release every month, around the 10th of the month<br>
* if changes warrant it and there is the manpower for it, interim releases<br>
* aim for first betas in may, this would also include a feature freeze<br>
* aim to move it into extragear/sdk/ and release a 0.1 release in tandem with<br>
KDE SC 4.5<br></blockquote><div><br>Sounds good to me, although with only 2-3 devs I'm not sure how many changes we'll be able to push each month. <br><br>----<br>Jason "moofang" Lim Yuen Hoe<br><a href="http://yuenhoe.co.cc/" target="_blank">http://yuenhoe.co.cc/</a><br>
<br>
<br>
</div></div>
<br>_______________________________________________<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>
<br></blockquote></div><br>