Great, good documentation is always needed! (I cannot access pyside.org right now so some of my comments might be stupid as I do not remember all the pyside details off the top of my head :-)
1) this would be a general, cross-platform pyside documentation, right? Are QtMobility python bindings out of the scope (or already documented properly somewhere)? 2) I would like to see installation/setup instructions also for other desktop platforms (mainly I am talking Windows and OS X here - yes, I remember that the support for those platforms is not entirely there, but still) 3) +1 for the packaging instructions best regards Hartti On Sat, Sep 4, 2010 at 6:31 AM, Sivan Greenberg <[email protected]> wrote: > Hi list, > > Finally, my weekends became more free than before and I can go back > to my (ambitious! ;)) initiative to provide better documentation for > the project. > > Googling around I see that most of the tutorials are either very > short with too much advanced details that might scare a new comer, on > the other hand the auto- generated reference documentation is rather > for those who have been either developing with Qt or PyQt for a while > and know exactly what they want. > > I have two main main goals: > > 1) Create an official tutorial, concentrating on the competitive edge > in rapid development and prototyping that PySide offers. This will > include setting up a development environment (with notes provided to > me here on the ML not long ago by some generous people of the mailing > list), setup from either source/git or provided packages on 2 desktop > platforms (Ubuntu and MeeGo). In order to emphasis the rapid > development I would like to demonstrate how to use PySide + QML for > fastest prototyping. > > 2) Create a "cookbook". So for each functionality incorporated from > Qt proper, I would like us to have a PySide example app or recipe. > Examples are "creating a web enabled app", a "service consuming app" , > a multimedia app, a "location based client server app" etc. Where a > complete recipe does not apply, we should at least provide a small > example. We could borrow from the Qt examples as they are if > applicable as I think Matti has started to do to some extent. > > So, for the PySide +QML (+MTF) bit I'd like to ask for bits of > guidance and/or references as while looking for this I found only very > small bits or mostly the QML parsing engine bindings reference in > PySide. > > Other than that- how does the whole idea sound? Any feedback and > suggestions are welcome as I want this to become as useful as > possible. > > BR, > > -Sivan > _______________________________________________ > PySide mailing list > [email protected] > http://lists.openbossa.org/listinfo/pyside >
_______________________________________________ PySide mailing list [email protected] http://lists.openbossa.org/listinfo/pyside
