On Friday 02 October 2009 09:31:30 am Matti Airas wrote: > ext Richard Dale wrote: > > Yes, we'll have to ask Arno as it's his baby that he is probably very > > proud of, but it seems a good idea. We really could use the documentation > > extraction and conversion for multiple languages if Nokia were happy with > > the copyright situation on that it would be really useful. > > There are no copyright issues for sharing code back and forth and/or > merging projects. PySide is really an open project - contributors retain > their copyright to the contributed code. The more there are > contributions, the less danger there is of any Evil Corporation suddenly > changing the license or closing the development again. :-) I wasn't meaning the code, but the actual documentation itself which I've had to get permission from Trolltech to use (specifically converting the text of the cannon game tutorial to talk about ruby). Although the code is LGPL, I think slightly different rules apply to documentation and tutorials.
> > Yes, if you didn't mind I could add a smoke branch to PySide and just > > fool around with no obligation to release, I think that would be nice. I > > actually don't know if smoke is a good idea, and whether it has > > performance problems that can't be solved. But only by having some sort > > of python implementation can we find out. And it is a really good > > opportunity for me to learn python properly which I never got round to > > doing in the past. > > That would be great! Maybe the simplest practical way to start here > would be for you to simply clone the respective repos and work within > the clones, and once there's something to share, ask me or some of the > OpenBossa team members to set up the proper Gitorious repo in the > project. Is that ok? Yes, ok that's sounds fine. There isn't really any hurry as I don't have any running code yet - I'm mainly working on the QtScript smoke bindings (in gitorious too). They are a good test bed for trying out ways of making Smoke more efficient at runtime to address the battery life problem on portable devices. I don't think the idea of switching to Smoke after you've spent six months getting Shiboken working makes sense, as I would suspect the last thing you would want to do after that, is to start all over again. So maybe a Python Smoke is best seen as a backup plan to the backup plan for now. -- Richard _______________________________________________ PySide mailing list [email protected] http://lists.openbossa.org/listinfo/pyside
