<font face="trebuchet ms,sans-serif">Hi.</font><div><font face="trebuchet ms,sans-serif">I agree with Mehrdad.</font></div><div><font face="trebuchet ms,sans-serif">I think, it will be interesting and we try to add this to next releases.</font></div>
<div><font face="trebuchet ms,sans-serif"><br></font><br><div class="gmail_quote">2011/1/9 Mehrdad Momeny <span dir="ltr"><<a href="mailto:mehrdad.momeny@gmail.com">mehrdad.momeny@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi,<br>
This could be great, and I like to participate.<br>
Start the project and show me/us some code samples to know how to code! :)<br>
<div><div></div><div class="h5"><br>
----- Original message -----<br>
> Hi there fellow developers.<br>
><br>
> I'm sending this email because we are all working on applications or<br>
> libraries which have something in common: all of them are interacting in<br>
> some ways with "Web/Cloud/2.0/whatever" services.<br>
><br>
> The idea is to share code in form of KJob's and make them our raw<br>
> material to build our plugins above them, that way everybody can<br>
> continue having they plugins (kipi's, choqok, kamoso, recorditnow) or<br>
> they integrations (KDevelop, Amarok) but we will be all sharing the same<br>
> code base.<br>
><br>
> The project though should remain small and easy to maintain, having that<br>
> in mind this is what we thought:<br>
><br>
> -The project should have containers such Silk::Twitpic::Upload (Upload<br>
> is the KJob)<br>
> -We should try to maintain retrocompatibility but we should not be hard<br>
> on that, anyway adding things like "Upload2" should be allowed.<br>
> -We should think of this project like a bag full of code, where the<br>
> developer chooses what code to use (rather than thinking of it like a<br>
> complex unified abstract thing).<br>
><br>
> By doing this code organization, we can share code between applications<br>
> in an easy way, for example, if we had all KJob-ified right now, we<br>
> would be able to unify and use other's implementations:<br>
><br>
> Job: Current implementations:<br>
> Silk::Youtube::Upload···········(Kamoso, recorditnow)<br>
> Silk::Youtube::Download·········(Amarok)<br>
> Silk::Youtube::Search···········(Amarok)<br>
> Silk::Facebook::Upload··········(Kipi)<br>
> Silk::Flcker::Upload············(Kipi, Choqok)<br>
> Silk::Twitpic::Upload···········(Choqok)<br>
> Silk::Picasa::Upload ············(Kipi)<br>
><br>
> Aleix and I are willing to start the project, by implementing<br>
> Youtube::Upload, Facebook::Upload and Twitpic::Upload (by porting choqok<br>
> uploaders to KJob), but before we start we want to know if you will<br>
> follow the lead.<br>
><br>
> So, What do you think?<br>
<br>
</div></div></blockquote></div><br></div>