From i at introo.me  Sun Mar  3 02:20:00 2013
From: i at introo.me (Shiyao Ma)
Date: Sun, 3 Mar 2013 09:20:00 +0800
Subject: [PySide] GSoC
In-Reply-To: <512652EF.2040003@wingware.com>
References: <20130221084213.3DDBF8ED@atlas.cz> <512652EF.2040003@wingware.com>
Message-ID: <CAJQX3Dw8UvA72CKxXi17isuPUxpYN0bNNmaU+jMrPQxNaLYFjw@mail.gmail.com>

I am also interested in your proposal.

On Fri, Feb 22, 2013 at 1:01 AM, Stephan Deibel <sdeibel at wingware.com>wrote:

> Vláďa wrote:
> > I'm wondering if there are any plans to join Google Summer of Code this
> year. For me the most important issue regarding PySide is missing Qt 5
> support. I need Qt 5 because of Qt Quick 2 and Qt Mobility.
> >
> > Also I think that another good project would to investigate how to use
> PySide to program for Ubuntu tablet and phone. AFAIK currently Qt with C++
> is suggested for phones and PyGTK for tablets. If PySide can be used for
> all platforms (mobile, tablet, desktop) it would be great.
> >
> > Maybe some people would be able to work on these tasks during GSoC. What
> do you think?
>
> I think it does require having one or more mentors that work with the
> students.  Also, I remember some Python related open source projects
> working through the PSF to participate in GSoC, probably because of
> requirements of there being some sort of legal entity.  If it turns out
> there are mentors and this is needed, I could ask contacts I have at the
> PSF about it.  I'm a member there and have been active on the board in
> the past.
>
> - Stephan
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>



-- 
My gpg pubring is available via: gpg --keyserver
subkeys.pgp.net--recv-keys 307CF736

More on: http://about.me/introom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130303/80a8fcf9/attachment.html>

From fabcastan at gmail.com  Mon Mar  4 23:40:38 2013
From: fabcastan at gmail.com (Fabien Castan)
Date: Mon, 4 Mar 2013 23:40:38 +0100
Subject: [PySide] QDropEvent.source() crash
Message-ID: <CAJQWia6Jq6oASoJshS7992oFHHtwPJCtAs4UDGP685_ukq3Dcg@mail.gmail.com>

Hi,
I created a DropArea for QtQuick 1.

So it's a QDeclarativeItem and I reimplemented the dropEvent. The problem
is when I read event.source(), it creates a seg. fault. at the end of the
application.
You could see the code, there:
https://github.com/buttleofx/QuickMamba/blob/master/quickmamba/gui/dropArea.py#L132

Just adding this print creates a seg. fault:
print "event source:", event.source()

This is true only when the drag event has been created inside the
application.
If you drag&drop files from a file browser, "event.source()" returns None
and there is no problem.

Some kind of widget ownership problem.

Program received signal SIGSEGV, Segmentation fault.
subtype_dealloc.25740 (self=<ButtleApp at remote 0x1f0eb00>) at
../Objects/typeobject.c:951
951 ../Objects/typeobject.c: Aucun fichier ou dossier de ce type.
(gdb)
(gdb)
(gdb) bt
#0  subtype_dealloc.25740 (self=<ButtleApp at remote 0x1f0eb00>) at
../Objects/typeobject.c:951
#1  0x00007fffef60b015 in Shiboken::decRefPyObjectList(std::list<_object*,
std::allocator<_object*> > const&, _object*) () from
/usr/local/lib/libshiboken-python2.7.so.1.1
#2  0x00007fffef60d5a6 in Shiboken::Object::clearReferences(SbkObject*) ()
from /usr/local/lib/libshiboken-python2.7.so.1.1
#3  0x00007fffef60ce0f in Shiboken::Object::deallocData(SbkObject*, bool)
() from /usr/local/lib/libshiboken-python2.7.so.1.1
#4  0x00007fffef609ba8 in SbkDeallocWrapper () from
/usr/local/lib/libshiboken-python2.7.so.1.1
#5  0x00007fffef60ca17 in Shiboken::Object::removeParent(SbkObject*, bool,
bool) () from /usr/local/lib/libshiboken-python2.7.so.1.1
#6  0x00007fffef60a39c in (anonymous
namespace)::_destroyParentInfo(SbkObject*, bool) () from
/usr/local/lib/libshiboken-python2.7.so.1.1
#7  0x00007fffef60c754 in Shiboken::Object::destroy(SbkObject*, void*) ()
from /usr/local/lib/libshiboken-python2.7.so.1.1
#8  0x00007fffef621901 in Shiboken::BindingManager::~BindingManager() ()
from /usr/local/lib/libshiboken-python2.7.so.1.1
#9  0x00007ffff6f1f901 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#10 0x00007ffff6f1f985 in exit () from /lib/x86_64-linux-gnu/libc.so.6
#11 0x00007ffff6f05774 in __libc_start_main () from
/lib/x86_64-linux-gnu/libc.so.6
#12 0x00000000004ce0ad in _start ()


Regards,
Fabien
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130304/9b024d96/attachment.html>

From contact at stephane-klein.info  Fri Mar  8 17:37:34 2013
From: contact at stephane-klein.info (=?ISO-8859-1?Q?St=E9phane_Klein?=)
Date: Fri, 08 Mar 2013 17:37:34 +0100
Subject: [PySide] "Could not detect Python module installation directory" on
 OSX with pyside-setup
Message-ID: <513A13CE.10406@stephane-klein.info>

Hi,

I've installed qt with :

$ brew install qt

Now, I try to compile PySide like this :

$ mkdir ~/tests
$ cd tests
$ git clone https://github.com/PySide/pyside-setup.git
$ cd pyside-setup/
$ python setup.py bdist_egg
...
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Using default python: -python2.7
CMake Error at /usr/lib/cmake/Shiboken-1.1.1/ShibokenConfig.cmake:5 (include):
  include could not find load file:


/Volumes/ramdisk/install/usr/lib/cmake/Shiboken-1.1.1/ShibokenConfig-python2.7.cmake
Call Stack (most recent call first):
  CMakeLists.txt:8 (find_package)


-- Looking for Q_WS_X11
-- Looking for Q_WS_X11 - not found
-- Looking for Q_WS_WIN
-- Looking for Q_WS_WIN - not found
-- Looking for Q_WS_QWS
-- Looking for Q_WS_QWS - not found
-- Looking for Q_WS_MAC
-- Looking for Q_WS_MAC - found
-- Looking for QT_MAC_USE_COCOA
-- Looking for QT_MAC_USE_COCOA - found
-- Found Qt4: /usr/local/bin/qmake (found suitable version "4.8.4", minimum
required is "4.5.0")
-- Detected OS: mac
CMake Error at CMakeLists.txt:148 (message):
  Could not detect Python module installation directory.


-- Configuring incomplete, errors occurred!
error: Error configuring pyside

Have you one idea about this error ?

You can read the full log here :
https://gist.github.com/harobed/efac6dd314a5bc53f94e

Best regards,
Stephane
-- 
Stéphane Klein <contact at stephane-klein.info>
blog: http://stephane-klein.info
Twitter: http://twitter.com/klein_stephane
cv: http://cv.stephane-klein.info
http://www.usenet-fr.net/fur/usenet/repondre-sur-usenet.html
http://fr.wikipedia.org/wiki/TOFU_(Usenet_et_Internet)


From biergaizi2009 at gmail.com  Sat Mar  9 08:08:26 2013
From: biergaizi2009 at gmail.com (Tom Li)
Date: Sat, 9 Mar 2013 15:08:26 +0800
Subject: [PySide] Fwd: How do I return an object in Python and use it in QML?
In-Reply-To: <CAB6YEzVi_iQGEd5-hK4r3GmJdGTazQ7jQiY2LB_b25RvmqA+ag@mail.gmail.com>
References: <CAB6YEzVi_iQGEd5-hK4r3GmJdGTazQ7jQiY2LB_b25RvmqA+ag@mail.gmail.com>
Message-ID: <CAB6YEzVcssoYo_SKKF5VmTH5hLtr7umW1pYnGSf8NvUFNY9yUQ@mail.gmail.com>

Well, I have no knowledge with JavaScript, or CSS. I just want to use
QML as a beautiful ListView.

I'm writing a Twitter client. I implemented TweetItem and TweetModel.
The issue is that there is a role in TweetItem called original. I want
it to point to the original tweet.

But I can not use it with "." operator in QML. I get an undefined value.
What is the right way to do it?

Thanks.

Here's my code.

main.py:

import sys
from PySide import QtCore, QtGui, QtDeclarative


class TweetModel(QtCore.QAbstractListModel):
    def __init__(self, prototype, parent=None):
        QtCore.QAbstractListModel.__init__(self, parent)
        self.setRoleNames(prototype.roleNames())
        self.tweets = []

    def appendRow(self, item):
        self.tweets.append(item)

    def rowCount(self, parent=QtCore.QModelIndex()):
        return len(self.tweets)

    def data(self, index, role):
        return self.tweets[index.row()].data(role)


class TweetItem(QtCore.QAbstractItemModel):
    def __init__(self, id=None, type=None, user=None, content=None,
time=None, original=None, parent=None):
        QtCore.QAbstractItemModel.__init__(self, parent)
        self.idRole = QtCore.Qt.UserRole + 1
        # More Roles
        self.originalRole = QtCore.Qt.UserRole + 6

        self.id = id
        self.original = original

    def roleNames(self):
        names = {}
        names[self.idRole] = "id"
        names[self.originalRole] = "original"
        return names

    def data(self, role):
        if role == self.idRole:
            return self.id
        elif role == self.originalRole:
            return self.original
        else:
            return QtCore.QVariant()


if __name__ = "__main__":
    model = TweetModel(TweetItem(), QtGui.qApp)
    item = TweetItem("0001", None, model)
    model.appendRow(TweetItem("0002", item, model))

    App = QtGui.QApplication(sys.argv)
    view = QtDeclarative.QDeclarativeView()
    view.rootContext().setContextProperty("mymodel", model)
    view.setSource(QtCore.QUrl.fromLocalFile("main.qml"))
    view.show()
    App.exec_()


main.qml:

import QtQuick 1.0

Rectangle {
  width: 360
  height: 360

  ListView {
         anchors.fill: parent
         model: mymodel
         // original.id == undefined
         delegate: Component { Text { text: id + " " + original.id } }
  }
}


From contact at stephane-klein.info  Sat Mar  9 10:27:22 2013
From: contact at stephane-klein.info (=?UTF-8?B?U3TDqXBoYW5lIEtsZWlu?=)
Date: Sat, 09 Mar 2013 10:27:22 +0100
Subject: [PySide] "Could not detect Python module installation
 directory" on OSX with pyside-setup
In-Reply-To: <CAG_nbntCM9Vg76xdD-YMCQLiTn=oG7e+wgjKHijh+NhHTM3q4A@mail.gmail.com>
References: <513A13CE.10406@stephane-klein.info>
	<CAG_nbntCM9Vg76xdD-YMCQLiTn=oG7e+wgjKHijh+NhHTM3q4A@mail.gmail.com>
Message-ID: <513B007A.4060806@stephane-klein.info>

Le 09/03/13 02:19, Srini Kommoori a écrit :
> If you are on pip or easy_install, it should work with them.
> 
> pip install PySide
> 
> Not sure about brew and dependencies. 
> 
> Hope this gets you going quickly.
> 

I've already did that.

No success.

This is the output of "pip intall PySide" :

https://gist.github.com/harobed/549c90e843612181c33b

Best regards,
Stephane
-- 
Stéphane Klein <contact at stephane-klein.info>
blog: http://stephane-klein.info
Twitter: http://twitter.com/klein_stephane
cv: http://cv.stephane-klein.info
http://www.usenet-fr.net/fur/usenet/repondre-sur-usenet.html
http://fr.wikipedia.org/wiki/TOFU_(Usenet_et_Internet)


From boris at pohlers-web.de  Sat Mar  9 12:55:54 2013
From: boris at pohlers-web.de (Boris Pohler)
Date: Sat, 09 Mar 2013 12:55:54 +0100
Subject: [PySide] Fwd: How do I return an object in Python and use it in
 QML?
In-Reply-To: <CAB6YEzVcssoYo_SKKF5VmTH5hLtr7umW1pYnGSf8NvUFNY9yUQ@mail.gmail.com>
References: <CAB6YEzVi_iQGEd5-hK4r3GmJdGTazQ7jQiY2LB_b25RvmqA+ag@mail.gmail.com>
	<CAB6YEzVcssoYo_SKKF5VmTH5hLtr7umW1pYnGSf8NvUFNY9yUQ@mail.gmail.com>
Message-ID: <1362830154.2822.0.camel@desktop>

You need to wrap the objects inside a QObject, have a look at this
example:
http://qt-project.org/wiki/Selectable-list-of-Python-objects-in-QML

Am Samstag, den 09.03.2013, 15:08 +0800 schrieb Tom Li:
> Well, I have no knowledge with JavaScript, or CSS. I just want to use
> QML as a beautiful ListView.
> 
> I'm writing a Twitter client. I implemented TweetItem and TweetModel.
> The issue is that there is a role in TweetItem called original. I want
> it to point to the original tweet.
> 
> But I can not use it with "." operator in QML. I get an undefined value.
> What is the right way to do it?
> 
> Thanks.
> 
> Here's my code.
> 
> main.py:
> 
> import sys
> from PySide import QtCore, QtGui, QtDeclarative
> 
> 
> class TweetModel(QtCore.QAbstractListModel):
>     def __init__(self, prototype, parent=None):
>         QtCore.QAbstractListModel.__init__(self, parent)
>         self.setRoleNames(prototype.roleNames())
>         self.tweets = []
> 
>     def appendRow(self, item):
>         self.tweets.append(item)
> 
>     def rowCount(self, parent=QtCore.QModelIndex()):
>         return len(self.tweets)
> 
>     def data(self, index, role):
>         return self.tweets[index.row()].data(role)
> 
> 
> class TweetItem(QtCore.QAbstractItemModel):
>     def __init__(self, id=None, type=None, user=None, content=None,
> time=None, original=None, parent=None):
>         QtCore.QAbstractItemModel.__init__(self, parent)
>         self.idRole = QtCore.Qt.UserRole + 1
>         # More Roles
>         self.originalRole = QtCore.Qt.UserRole + 6
> 
>         self.id = id
>         self.original = original
> 
>     def roleNames(self):
>         names = {}
>         names[self.idRole] = "id"
>         names[self.originalRole] = "original"
>         return names
> 
>     def data(self, role):
>         if role == self.idRole:
>             return self.id
>         elif role == self.originalRole:
>             return self.original
>         else:
>             return QtCore.QVariant()
> 
> 
> if __name__ = "__main__":
>     model = TweetModel(TweetItem(), QtGui.qApp)
>     item = TweetItem("0001", None, model)
>     model.appendRow(TweetItem("0002", item, model))
> 
>     App = QtGui.QApplication(sys.argv)
>     view = QtDeclarative.QDeclarativeView()
>     view.rootContext().setContextProperty("mymodel", model)
>     view.setSource(QtCore.QUrl.fromLocalFile("main.qml"))
>     view.show()
>     App.exec_()
> 
> 
> main.qml:
> 
> import QtQuick 1.0
> 
> Rectangle {
>   width: 360
>   height: 360
> 
>   ListView {
>          anchors.fill: parent
>          model: mymodel
>          // original.id == undefined
>          delegate: Component { Text { text: id + " " + original.id } }
>   }
> }
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside




From backup.rlacko at gmail.com  Sat Mar  9 21:36:54 2013
From: backup.rlacko at gmail.com (Roman Lacko)
Date: Sat, 9 Mar 2013 21:36:54 +0100
Subject: [PySide] "Could not detect Python module installation
 directory" on OSX with pyside-setup
In-Reply-To: <513B007A.4060806@stephane-klein.info>
References: <513A13CE.10406@stephane-klein.info>
	<CAG_nbntCM9Vg76xdD-YMCQLiTn=oG7e+wgjKHijh+NhHTM3q4A@mail.gmail.com>
	<513B007A.4060806@stephane-klein.info>
Message-ID: <CAHC6v6iwxQDXd4tJJicGsK_aRUeV-ENsZB2EkH=1TqbVtCM=rA@mail.gmail.com>

2013/3/9 Stéphane Klein <contact at stephane-klein.info>

> Le 09/03/13 02:19, Srini Kommoori a écrit :
> > If you are on pip or easy_install, it should work with them.
> >
> > pip install PySide
> >
> > Not sure about brew and dependencies.
> >
> > Hope this gets you going quickly.
> >
>
> I've already did that.
>
> No success.
>

OSX is supported in master branch of pyside-setup,
you can  try the following command:

pip install git+https://github.com/PySide/pyside-setup.git
--install-option="--version=1.1.2"

you can avoid --install-option="--version=1.1.2" if you dont need
pyside stable version

Regards
R.


>
> This is the output of "pip intall PySide" :
>
> https://gist.github.com/harobed/549c90e843612181c33b
>
> Best regards,
> Stephane
> --
> Stéphane Klein <contact at stephane-klein.info>
> blog: http://stephane-klein.info
> Twitter: http://twitter.com/klein_stephane
> cv: http://cv.stephane-klein.info
> http://www.usenet-fr.net/fur/usenet/repondre-sur-usenet.html
> http://fr.wikipedia.org/wiki/TOFU_(Usenet_et_Internet)
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130309/7429eabd/attachment.html>

From contact at stephane-klein.info  Sun Mar 10 09:59:28 2013
From: contact at stephane-klein.info (=?ISO-8859-1?Q?St=E9phane_Klein?=)
Date: Sun, 10 Mar 2013 09:59:28 +0100
Subject: [PySide] "Could not detect Python module installation
 directory" on OSX with pyside-setup
In-Reply-To: <CAHC6v6iwxQDXd4tJJicGsK_aRUeV-ENsZB2EkH=1TqbVtCM=rA@mail.gmail.com>
References: <513A13CE.10406@stephane-klein.info>
	<CAG_nbntCM9Vg76xdD-YMCQLiTn=oG7e+wgjKHijh+NhHTM3q4A@mail.gmail.com>
	<513B007A.4060806@stephane-klein.info>
	<CAHC6v6iwxQDXd4tJJicGsK_aRUeV-ENsZB2EkH=1TqbVtCM=rA@mail.gmail.com>
Message-ID: <513C4B70.4090106@stephane-klein.info>

Le 09/03/13 21:36, Roman Lacko a écrit :
> OSX is supported in master branch of pyside-setup,
> you can  try the following command:
> 
> pip install git+https://github.com/PySide/pyside-setup.git --install-option="--version=1.1.2"
> 
> you can avoid --install-option="--version=1.1.2" if you dont need pyside stable version

Thanks for this tips.

But I've always the same error :

-- Found Qt4: /usr/local/bin/qmake (found suitable version "4.8.4", minimum
required is "4.5.0")
-- Detected OS: mac
CMake Error at CMakeLists.txt:148 (message):
  Could not detect Python module installation directory.
-- Configuring incomplete, errors occurred!
error: Error configuring pyside

Full log : https://gist.github.com/harobed/a79a580419dfbc223be5

I need to specify another parameter ?

Best regards,
Stephane
-- 
Stéphane Klein <contact at stephane-klein.info>
blog: http://stephane-klein.info
Twitter: http://twitter.com/klein_stephane
cv: http://cv.stephane-klein.info
http://www.usenet-fr.net/fur/usenet/repondre-sur-usenet.html
http://fr.wikipedia.org/wiki/TOFU_(Usenet_et_Internet)


From contact at stephane-klein.info  Sun Mar 10 18:54:53 2013
From: contact at stephane-klein.info (=?ISO-8859-1?Q?St=E9phane_Klein?=)
Date: Sun, 10 Mar 2013 18:54:53 +0100
Subject: [PySide] "Could not detect Python module installation
 directory" on OSX with pyside-setup
In-Reply-To: <513A13CE.10406@stephane-klein.info>
References: <513A13CE.10406@stephane-klein.info>
Message-ID: <513CC8ED.2010108@stephane-klein.info>

Le 08/03/13 17:37, Stéphane Klein a écrit :
> $ python setup.py bdist_egg

Now, if I do :

(env1)$ python setup.py bdist_egg --debug

I've this error :

error: Failed to locate the Python library with
/Users/stephaneklein/.pythonz/pythons/CPython-2.7.3/lib/libpython2.7_d.so,
/Users/stephaneklein/.pythonz/pythons/CPython-2.7.3/lib/libpython2.7_d.dylib,
/Users/stephaneklein/.pythonz/pythons/CPython-2.7.3/lib/libpython2.7_d.so.1,
/Users/stephaneklein/.pythonz/pythons/CPython-2.7.3/lib/libpython2.7_d.a

Full log : https://gist.github.com/harobed/c756eb7c46ca2a241f7c

Do you have an idea to fix that ?

Best regards,
Stephane
-- 
Stéphane Klein <contact at stephane-klein.info>
blog: http://stephane-klein.info
Twitter: http://twitter.com/klein_stephane
cv: http://cv.stephane-klein.info
http://www.usenet-fr.net/fur/usenet/repondre-sur-usenet.html
http://fr.wikipedia.org/wiki/TOFU_(Usenet_et_Internet)


From ltanure at gmail.com  Mon Mar 11 18:47:49 2013
From: ltanure at gmail.com (Lucas Tanure)
Date: Mon, 11 Mar 2013 14:47:49 -0300
Subject: [PySide]  - Leaving
Message-ID: <CAJyon0tH6c5wd1kOjJYpWCr1QNQAmAKNSXWwsaYb_Oi=5=W+Ew@mail.gmail.com>

Hi guys,

Thanks for the support, but I will go with pyqt.
PySide is far better than PyQt, but now I cant install on my Arch Linux and
I dont see any future for pyside.

I really tryed to help, but I cant embrace the world.

The pybingen could be a great future for pyside, but needs someone full
time working on that.

Thanks
Best Regards

Lucas A. Tanure Alves
+55 (19) 88176559
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130311/ca93af82/attachment.html>

From techtonik at gmail.com  Thu Mar 14 00:52:28 2013
From: techtonik at gmail.com (anatoly techtonik)
Date: Thu, 14 Mar 2013 02:52:28 +0300
Subject: [PySide] - Leaving
In-Reply-To: <CAJyon0tH6c5wd1kOjJYpWCr1QNQAmAKNSXWwsaYb_Oi=5=W+Ew@mail.gmail.com>
References: <CAJyon0tH6c5wd1kOjJYpWCr1QNQAmAKNSXWwsaYb_Oi=5=W+Ew@mail.gmail.com>
Message-ID: <CAPkN8x+Ctj5g=dsHG9AptOr=SYEVOeKH7TQjixQrCW6Wi_8noA@mail.gmail.com>

On Mon, Mar 11, 2013 at 8:47 PM, Lucas Tanure <ltanure at gmail.com> wrote:

> Hi guys,
>
> Thanks for the support, but I will go with pyqt.
> PySide is far better than PyQt, but now I cant install on my Arch Linux
> and I dont see any future for pyside.
>
> I really tryed to help, but I cant embrace the world.
>
> The pybingen could be a great future for pyside, but needs someone full
> time working on that.
>

Bye! PySide still bears a lot of tasty legacy, so feel free to get back to
proceed. Anytime. =)
-- 
anatoly t.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130314/8efc1604/attachment.html>

From diego at gaustein.com.ar  Thu Mar 14 04:59:51 2013
From: diego at gaustein.com.ar (Diego Gaustein)
Date: Thu, 14 Mar 2013 00:59:51 -0300
Subject: [PySide] - Leaving
In-Reply-To: <CAJyon0tH6c5wd1kOjJYpWCr1QNQAmAKNSXWwsaYb_Oi=5=W+Ew@mail.gmail.com>
References: <CAJyon0tH6c5wd1kOjJYpWCr1QNQAmAKNSXWwsaYb_Oi=5=W+Ew@mail.gmail.com>
Message-ID: <CAEq4Lwj5jH3VHqMvo3XsPCnA=HbhNy9cWB51eB5XApDwN_VbVA@mail.gmail.com>

PySide is working as always on my Arch Linux install, I got Qt5, but the
Qt4 packages were updated, feel free to drop by the forums or IRC channel
if you are having trouble.

Diego


On Mon, Mar 11, 2013 at 2:47 PM, Lucas Tanure <ltanure at gmail.com> wrote:

> Hi guys,
>
> Thanks for the support, but I will go with pyqt.
> PySide is far better than PyQt, but now I cant install on my Arch Linux
> and I dont see any future for pyside.
>
> I really tryed to help, but I cant embrace the world.
>
> The pybingen could be a great future for pyside, but needs someone full
> time working on that.
>
> Thanks
> Best Regards
>
> Lucas A. Tanure Alves
> +55 (19) 88176559
>
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130314/5816cbee/attachment.html>

From lndndev at gmail.com  Sun Mar 17 12:10:58 2013
From: lndndev at gmail.com (lndn)
Date: Sun, 17 Mar 2013 04:10:58 -0700
Subject: [PySide] Resurrecting PySide
Message-ID: <CAJ6WS8tFZpScDnyYs12T+tnDZrEp+RHPLUW3J6VYBZFPyr98RA@mail.gmail.com>

All the recent scary "PySide is Dead" emails really prompted me to think
about what we can do to improve the situation.  Not being familiar with the
PySide/Shiboken internals, I thought it would be a good idea to start by
cleaning up the wiki pages on qt-project.

However, as I combed through these pages, I noticed that many of the links
were broken and pointing to old pyside.org pages that no longer exist and
the content contains outdated and incomplete information.  What is really
needed is a major overhaul in updating the content.

So what's the official word on a massive re-organizing of these pages?  Can
I just take the initiative and do it?  I'd like to start off by just
putting the wiki pages in some order so things are easy to find and then
later go through the content and update the content one page at a time.  My
goal is just to help users and developers easily navigate to the pages they
need.

Any thoughts or people interested in helping would be great.

Thanks,
lndn
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130317/e5f59166/attachment.html>

From a.richi at bluewin.ch  Sun Mar 17 12:35:20 2013
From: a.richi at bluewin.ch (Aaron Richiger)
Date: Sun, 17 Mar 2013 12:35:20 +0100
Subject: [PySide] Resurrecting PySide
In-Reply-To: <CAJ6WS8tFZpScDnyYs12T+tnDZrEp+RHPLUW3J6VYBZFPyr98RA@mail.gmail.com>
References: <CAJ6WS8tFZpScDnyYs12T+tnDZrEp+RHPLUW3J6VYBZFPyr98RA@mail.gmail.com>
Message-ID: <5145AA78.1020709@bluewin.ch>

Hello Indn!

I would say: Any improvement is welcome, so feel free to take the 
initiative! I hope, the content of the broken links is still available 
somewhere. We are currently working a lot on bringing PySide to Android, 
so I do not have any time to help you for the moment, sorry!

Have a nice day!
Aaron


Am 17.03.2013 12:10, schrieb lndn:
> All the recent scary "PySide is Dead" emails really prompted me to 
> think about what we can do to improve the situation.  Not being 
> familiar with the PySide/Shiboken internals, I thought it would be a 
> good idea to start by cleaning up the wiki pages on qt-project.
>
> However, as I combed through these pages, I noticed that many of the 
> links were broken and pointing to old pyside.org <http://pyside.org> 
> pages that no longer exist and the content contains outdated and 
> incomplete information.  What is really needed is a major overhaul in 
> updating the content.
>
> So what's the official word on a massive re-organizing of these pages? 
>  Can I just take the initiative and do it?  I'd like to start off by 
> just putting the wiki pages in some order so things are easy to find 
> and then later go through the content and update the content one page 
> at a time.  My goal is just to help users and developers easily 
> navigate to the pages they need.
>
> Any thoughts or people interested in helping would be great.
>
> Thanks,
> lndn
>
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130317/df2ce772/attachment.html>

From a.richi at bluewin.ch  Sun Mar 17 12:39:51 2013
From: a.richi at bluewin.ch (Aaron Richiger)
Date: Sun, 17 Mar 2013 12:39:51 +0100
Subject: [PySide] Resurrecting PySide
In-Reply-To: <CAJ6WS8uEsLVFi5uPP65m3Pov2jNELXtoBa9Y_HdUVHQD7J8rpg@mail.gmail.com>
References: <CAJ6WS8tFZpScDnyYs12T+tnDZrEp+RHPLUW3J6VYBZFPyr98RA@mail.gmail.com>
	<5145A726.5050402@bluewin.ch>
	<CAJ6WS8uEsLVFi5uPP65m3Pov2jNELXtoBa9Y_HdUVHQD7J8rpg@mail.gmail.com>
Message-ID: <5145AB87.8010907@bluewin.ch>

Hello Indn

Yes, I would say so. Having everything in a central place will simplify 
future movements to another host. I would say, old content is ok as long 
as it is still valid. But if the content is out of date, it should be 
clearly remarked as such or removed.

Good luck!

Am 17.03.2013 12:29, schrieb lndn:
> Hey Aaron, thanks for replying.  You brought up a good point.  If 
> there is content available somewhere on the web or internet archives, 
> even if it's old, I think I'll just copy it and put it on the wiki 
> pages so they're comprehensive and all-inclusive.  Better to have 
> everything in one place, than scattered.
>
> lndn
>
>
> On Sun, Mar 17, 2013 at 4:21 AM, Aaron Richiger <a.richi at bluewin.ch 
> <mailto:a.richi at bluewin.ch>> wrote:
>
>     Hello Indn!
>
>     I would say: Any improvement is welcome, so feel free to take the
>     initiative! I hope, the content of the broken links is still
>     available somewhere. We are currently working a lot on bringing
>     PySide to Android, so I do not have any time to help you for the
>     moment, sorry!
>
>     Have a nice day!
>     Aaron
>
>
>
>
>     Am 17.03.2013 12:10, schrieb lndn:
>>     All the recent scary "PySide is Dead" emails really prompted me
>>     to think about what we can do to improve the situation.  Not
>>     being familiar with the PySide/Shiboken internals, I thought it
>>     would be a good idea to start by cleaning up the wiki pages on
>>     qt-project.
>>
>>     However, as I combed through these pages, I noticed that many of
>>     the links were broken and pointing to old pyside.org
>>     <http://pyside.org> pages that no longer exist and the content
>>     contains outdated and incomplete information.  What is really
>>     needed is a major overhaul in updating the content.
>>
>>     So what's the official word on a massive re-organizing of these
>>     pages?  Can I just take the initiative and do it?  I'd like to
>>     start off by just putting the wiki pages in some order so things
>>     are easy to find and then later go through the content and update
>>     the content one page at a time.  My goal is just to help users
>>     and developers easily navigate to the pages they need.
>>
>>     Any thoughts or people interested in helping would be great.
>>
>>     Thanks,
>>     lndn
>>
>>
>>     _______________________________________________
>>     PySide mailing list
>>     PySide at qt-project.org  <mailto:PySide at qt-project.org>
>>     http://lists.qt-project.org/mailman/listinfo/pyside
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130317/cf30a90d/attachment.html>

From sdeibel at wingware.com  Sun Mar 17 17:17:14 2013
From: sdeibel at wingware.com (Stephan Deibel)
Date: Sun, 17 Mar 2013 09:17:14 -0700
Subject: [PySide] Resurrecting PySide
In-Reply-To: <CAJ6WS8tFZpScDnyYs12T+tnDZrEp+RHPLUW3J6VYBZFPyr98RA@mail.gmail.com>
References: <CAJ6WS8tFZpScDnyYs12T+tnDZrEp+RHPLUW3J6VYBZFPyr98RA@mail.gmail.com>
Message-ID: <5145EC8A.8080900@wingware.com>

lndn wrote:
> All the recent scary "PySide is Dead" emails really prompted me to 
> think about what we can do to improve the situation.  Not being 
> familiar with the PySide/Shiboken internals, I thought it would be a 
> good idea to start by cleaning up the wiki pages on qt-project.
>
> However, as I combed through these pages, I noticed that many of the 
> links were broken and pointing to old pyside.org <http://pyside.org> 
> pages that no longer exist and the content contains outdated and 
> incomplete information.  What is really needed is a major overhaul in 
> updating the content.
>
> So what's the official word on a massive re-organizing of these pages? 
>  Can I just take the initiative and do it?  I'd like to start off by 
> just putting the wiki pages in some order so things are easy to find 
> and then later go through the content and update the content one page 
> at a time.  My goal is just to help users and developers easily 
> navigate to the pages they need.
>
> Any thoughts or people interested in helping would be great.

This would be very helpful!

I have in the past found some of the missing pages on archive.org.  You 
can paste urls there in the WayBackMachine box and see dated archives of 
the page.  It would be great to put back some of that lost content 
(which I think was lost in the Nokia -> Digia transition).

For outdated docs, it seems best to keep them somewhere (an archive 
area?) or clearly label them, rather than removing them for now.  I 
suspect some of these may be helpful to people trying to understand and 
move PySide forward.

Thanks for offering to do this!

- Stephan



From jpe at wingware.com  Mon Mar 18 18:37:01 2013
From: jpe at wingware.com (John Ehresman)
Date: Mon, 18 Mar 2013 10:37:01 -0700
Subject: [PySide] Additional pyside reviewers
In-Reply-To: <1592310.DtA18LIKW2@hugodesktop>
References: <CAJyon0vanPWaucHhhrq5wDnS-Tg91eMTdtfsS7172w4v0Eo=SA@mail.gmail.com>
	<CAHfg+FPpYG+-TYzpAUJGKi6w_netfEQodr0cgn6G_5wzmukrcw@mail.gmail.com>
	<50CB38FC.6000807@wingware.com> <1592310.DtA18LIKW2@hugodesktop>
Message-ID: <514750BD.7060504@wingware.com>

On 12/14/12 9:01 AM, Hugo Parente Lima wrote:
> To be reviewer, I propose John Ehresman or John Cummings, some of
> the last useful commits in months were made by them.

I'd like to pick up this thread from a few months ago and ask if we
can add more approvers to the pyside project.  If I'm reading the qt
rules at http://qt-project.org/wiki/The_Qt_Governance_Model correctly,
we need a nomination and a second from current approvers.

I ask now because I want to move towards a new shiboken & pyside
release.  There are a few bugs fixed in the current sources and we
should push those fixes out.  Is there any documentation of what is
needed to make a new release?

Thanks,

John


From hugo.lima at openbossa.org  Mon Mar 18 22:52:12 2013
From: hugo.lima at openbossa.org (Hugo Parente Lima)
Date: Mon, 18 Mar 2013 18:52:12 -0300
Subject: [PySide] Additional pyside reviewers
In-Reply-To: <514750BD.7060504@wingware.com>
References: <CAJyon0vanPWaucHhhrq5wDnS-Tg91eMTdtfsS7172w4v0Eo=SA@mail.gmail.com>
	<1592310.DtA18LIKW2@hugodesktop> <514750BD.7060504@wingware.com>
Message-ID: <2800764.YRBIifK68U@hugodesktop>

On Monday, March 18, 2013 10:37:01 AM John Ehresman wrote:
> On 12/14/12 9:01 AM, Hugo Parente Lima wrote:
> > To be reviewer, I propose John Ehresman or John Cummings, some of
> > the last useful commits in months were made by them.
> 
> I'd like to pick up this thread from a few months ago and ask if we
> can add more approvers to the pyside project.  If I'm reading the qt
> rules at http://qt-project.org/wiki/The_Qt_Governance_Model correctly,
> we need a nomination and a second from current approvers.

Yes, I want to step down as maintainer, I'm no longer working on PySide and 
the code base in fading out from my memory month after month, the main problem 
now is that I don't know who on Qt-Project is responsible for add/remove 
approvers/maintainers.
 
> I ask now because I want to move towards a new shiboken & pyside
> release.  There are a few bugs fixed in the current sources and we
> should push those fixes out.  Is there any documentation of what is
> needed to make a new release?

We had a list with steps to do for a release somewhere in the Wiki, the 
technical part is:

- Run "make dist" to create the tarball.
- Tag the version on git.
- Bump the version on CMakeLists.txt.
- Upload the tarball.
- Update the download links on our wiki page.
- Send a email to the list telling.
 
> Thanks,
> 
> John
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130318/4dc72306/attachment.sig>

From jpe at wingware.com  Mon Mar 18 23:48:00 2013
From: jpe at wingware.com (John Ehresman)
Date: Mon, 18 Mar 2013 15:48:00 -0700
Subject: [PySide] Additional pyside reviewers
In-Reply-To: <2800764.YRBIifK68U@hugodesktop>
References: <CAJyon0vanPWaucHhhrq5wDnS-Tg91eMTdtfsS7172w4v0Eo=SA@mail.gmail.com>
	<1592310.DtA18LIKW2@hugodesktop> <514750BD.7060504@wingware.com>
	<2800764.YRBIifK68U@hugodesktop>
Message-ID: <514799A0.7060505@wingware.com>

On 3/18/13 2:52 PM, Hugo Parente Lima wrote:
> Yes, I want to step down as maintainer, I'm no longer working on
> PySide and the code base in fading out from my memory month after
> month, the main problem now is that I don't know who on Qt-Project
> is responsible for add/remove approvers/maintainers.

Would Lars Knoll be the one to ask?  It would probably be better if
the request came from you and Marcelo Lira since you're listed as the
maintainers on http://qt-project.org/wiki/Maintainers

>> I ask now because I want to move towards a new shiboken & pyside 
>> release.  There are a few bugs fixed in the current sources and
>> we should push those fixes out.  Is there any documentation of
>> what is needed to make a new release?
> 
> We had a list with steps to do for a release somewhere in the Wiki,
> the technical part is:
> 
> - Run "make dist" to create the tarball. - Tag the version on git. 
> - Bump the version on CMakeLists.txt. - Upload the tarball. -
> Update the download links on our wiki page. - Send a email to the
> list telling.

I can't seem to find it on the wiki, but that list is probably a good
start.

Thanks,

John



From lndndev at gmail.com  Tue Mar 19 03:57:44 2013
From: lndndev at gmail.com (lndn)
Date: Mon, 18 Mar 2013 19:57:44 -0700
Subject: [PySide] Additional pyside reviewers
In-Reply-To: <514799A0.7060505@wingware.com>
References: <CAJyon0vanPWaucHhhrq5wDnS-Tg91eMTdtfsS7172w4v0Eo=SA@mail.gmail.com>
	<1592310.DtA18LIKW2@hugodesktop> <514750BD.7060504@wingware.com>
	<2800764.YRBIifK68U@hugodesktop> <514799A0.7060505@wingware.com>
Message-ID: <CAJ6WS8vC__b3a4s2amuHkPtu1qS_J5=Z3Oicfd4Ayu5oRr3-WA@mail.gmail.com>

John, any updates on getting added as a reviewer or maintainer?

Since I don't know who's who and the PySide contributors list (
http://qt-project.org/wiki/PySideContributors) is way out of date, I'm
wondering if any of the core developers are still around to contribute.  I
just re-organized some of the pyside wiki pages (
http://qt-project.org/wiki/PySide) and the development section really needs
someone who is more knowledgeable to update the content, or maybe write a
page or two.




On Mon, Mar 18, 2013 at 3:48 PM, John Ehresman <jpe at wingware.com> wrote:

> On 3/18/13 2:52 PM, Hugo Parente Lima wrote:
> > Yes, I want to step down as maintainer, I'm no longer working on
> > PySide and the code base in fading out from my memory month after
> > month, the main problem now is that I don't know who on Qt-Project
> > is responsible for add/remove approvers/maintainers.
>
> Would Lars Knoll be the one to ask?  It would probably be better if
> the request came from you and Marcelo Lira since you're listed as the
> maintainers on http://qt-project.org/wiki/Maintainers
>
> >> I ask now because I want to move towards a new shiboken & pyside
> >> release.  There are a few bugs fixed in the current sources and
> >> we should push those fixes out.  Is there any documentation of
> >> what is needed to make a new release?
> >
> > We had a list with steps to do for a release somewhere in the Wiki,
> > the technical part is:
> >
> > - Run "make dist" to create the tarball. - Tag the version on git.
> > - Bump the version on CMakeLists.txt. - Upload the tarball. -
> > Update the download links on our wiki page. - Send a email to the
> > list telling.
>
> I can't seem to find it on the wiki, but that list is probably a good
> start.
>
> Thanks,
>
> John
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130318/2b7e9927/attachment.html>

From lndndev at gmail.com  Tue Mar 19 04:02:49 2013
From: lndndev at gmail.com (lndn)
Date: Mon, 18 Mar 2013 20:02:49 -0700
Subject: [PySide] Resurrecting PySide
In-Reply-To: <5145EC8A.8080900@wingware.com>
References: <CAJ6WS8tFZpScDnyYs12T+tnDZrEp+RHPLUW3J6VYBZFPyr98RA@mail.gmail.com>
	<5145EC8A.8080900@wingware.com>
Message-ID: <CAJ6WS8szz_Df+XprBBUBkEM5KQb85vfEPu0yCE_xZrJM=PuZyA@mail.gmail.com>

I just spent the weekend organizing some of the pyside wiki pages (
http://qt-project.org/wiki/PySide) and making small updates to the content
here and there.

Still needs a lot of work, but if someone can take a look and tell me what
you think so far, I can start focusing on important areas.

Thanks!


On Sun, Mar 17, 2013 at 9:17 AM, Stephan Deibel <sdeibel at wingware.com>wrote:

> lndn wrote:
>
>> All the recent scary "PySide is Dead" emails really prompted me to think
>> about what we can do to improve the situation.  Not being familiar with the
>> PySide/Shiboken internals, I thought it would be a good idea to start by
>> cleaning up the wiki pages on qt-project.
>>
>> However, as I combed through these pages, I noticed that many of the
>> links were broken and pointing to old pyside.org <http://pyside.org>
>> pages that no longer exist and the content contains outdated and incomplete
>> information.  What is really needed is a major overhaul in updating the
>> content.
>>
>>
>> So what's the official word on a massive re-organizing of these pages?
>>  Can I just take the initiative and do it?  I'd like to start off by just
>> putting the wiki pages in some order so things are easy to find and then
>> later go through the content and update the content one page at a time.  My
>> goal is just to help users and developers easily navigate to the pages they
>> need.
>>
>> Any thoughts or people interested in helping would be great.
>>
>
> This would be very helpful!
>
> I have in the past found some of the missing pages on archive.org.  You
> can paste urls there in the WayBackMachine box and see dated archives of
> the page.  It would be great to put back some of that lost content (which I
> think was lost in the Nokia -> Digia transition).
>
> For outdated docs, it seems best to keep them somewhere (an archive area?)
> or clearly label them, rather than removing them for now.  I suspect some
> of these may be helpful to people trying to understand and move PySide
> forward.
>
> Thanks for offering to do this!
>
> - Stephan
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130318/4d9cd05b/attachment.html>

From mairas at iki.fi  Tue Mar 19 05:49:42 2013
From: mairas at iki.fi (Matti Airas)
Date: Tue, 19 Mar 2013 06:49:42 +0200
Subject: [PySide] Additional pyside reviewers
In-Reply-To: <2800764.YRBIifK68U@hugodesktop>
References: <CAJyon0vanPWaucHhhrq5wDnS-Tg91eMTdtfsS7172w4v0Eo=SA@mail.gmail.com>
	<1592310.DtA18LIKW2@hugodesktop> <514750BD.7060504@wingware.com>
	<2800764.YRBIifK68U@hugodesktop>
Message-ID: <CAHfg+FNOYdEQ0M5vowLL5UAnN-eMwo_qyy-xQhvkKF_RwoPzAA@mail.gmail.com>

On 18 Mar 2013 23:53, "Hugo Parente Lima" <hugo.lima at openbossa.org> wrote:
> Yes, I want to step down as maintainer, I'm no longer working on PySide
and
> the code base in fading out from my memory month after month, the main
problem
> now is that I don't know who on Qt-Project is responsible for add/remove
> approvers/maintainers.

I'd like to thank on my behalf for the awesome contribution you've done for
PySide over the past years. It's been quite incredible!

The different roles and nomination process are described here:

http://qt-project.org/wiki/The_Qt_Governance_Model

Basically, you, Hugo, should just send an email your proposal to
development at qt-project.org mailing list. A cc to Lars probably won't harm,
but the reasoning should be in public.

http://lists.qt-project.org/mailman/listinfo/development

Nominating a bunch of new approvers at the same time probably wouldn't
harm, either... :-)

Cheers,

ma.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130319/03837eb8/attachment.html>

From backup.rlacko at gmail.com  Tue Mar 19 08:14:17 2013
From: backup.rlacko at gmail.com (Roman Lacko)
Date: Tue, 19 Mar 2013 08:14:17 +0100
Subject: [PySide] Resurrecting PySide
In-Reply-To: <CAJ6WS8szz_Df+XprBBUBkEM5KQb85vfEPu0yCE_xZrJM=PuZyA@mail.gmail.com>
References: <CAJ6WS8tFZpScDnyYs12T+tnDZrEp+RHPLUW3J6VYBZFPyr98RA@mail.gmail.com>
	<5145EC8A.8080900@wingware.com>
	<CAJ6WS8szz_Df+XprBBUBkEM5KQb85vfEPu0yCE_xZrJM=PuZyA@mail.gmail.com>
Message-ID: <CAHC6v6jYUW9k7SgeDJn2z6zGTBP9FgG+Xrt4=BVf2KoK+Cfq+A@mail.gmail.com>

Hi,

2013/3/19 lndn <lndndev at gmail.com>

> I just spent the weekend organizing some of the pyside wiki pages (
> http://qt-project.org/wiki/PySide) and making small updates to the
> content here and there.
>
> Still needs a lot of work, but if someone can take a look and tell me what
> you think so far, I can start focusing on important areas.
>
> Thanks!
>
> Thanks for doing this!

It would be great to put somewhere information about the PyPI page [1].
It contains the installation instructions (for windows and linux) and full
source code of PySide, Shiboken, PySideTool, examples and build scripts
bundled in standard distutils package. Also here is the downloads page for
prebuild windows packages and source budles [2]. I should put the
information on wiki myself but never had time to do it.

Thanks
R.

[1] https://pypi.python.org/pypi/PySide
[2] http://releases.qt-project.org/pyside/


> On Sun, Mar 17, 2013 at 9:17 AM, Stephan Deibel <sdeibel at wingware.com>wrote:
>
>> lndn wrote:
>>
>>> All the recent scary "PySide is Dead" emails really prompted me to think
>>> about what we can do to improve the situation.  Not being familiar with the
>>> PySide/Shiboken internals, I thought it would be a good idea to start by
>>> cleaning up the wiki pages on qt-project.
>>>
>>> However, as I combed through these pages, I noticed that many of the
>>> links were broken and pointing to old pyside.org <http://pyside.org>
>>> pages that no longer exist and the content contains outdated and incomplete
>>> information.  What is really needed is a major overhaul in updating the
>>> content.
>>>
>>>
>>> So what's the official word on a massive re-organizing of these pages?
>>>  Can I just take the initiative and do it?  I'd like to start off by just
>>> putting the wiki pages in some order so things are easy to find and then
>>> later go through the content and update the content one page at a time.  My
>>> goal is just to help users and developers easily navigate to the pages they
>>> need.
>>>
>>> Any thoughts or people interested in helping would be great.
>>>
>>
>> This would be very helpful!
>>
>> I have in the past found some of the missing pages on archive.org.  You
>> can paste urls there in the WayBackMachine box and see dated archives of
>> the page.  It would be great to put back some of that lost content (which I
>> think was lost in the Nokia -> Digia transition).
>>
>> For outdated docs, it seems best to keep them somewhere (an archive
>> area?) or clearly label them, rather than removing them for now.  I suspect
>> some of these may be helpful to people trying to understand and move PySide
>> forward.
>>
>> Thanks for offering to do this!
>>
>> - Stephan
>>
>>
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130319/0c1df6c9/attachment.html>

From lndndev at gmail.com  Tue Mar 19 08:43:30 2013
From: lndndev at gmail.com (lndn)
Date: Tue, 19 Mar 2013 00:43:30 -0700
Subject: [PySide] Resurrecting PySide
In-Reply-To: <CAHC6v6jYUW9k7SgeDJn2z6zGTBP9FgG+Xrt4=BVf2KoK+Cfq+A@mail.gmail.com>
References: <CAJ6WS8tFZpScDnyYs12T+tnDZrEp+RHPLUW3J6VYBZFPyr98RA@mail.gmail.com>
	<5145EC8A.8080900@wingware.com>
	<CAJ6WS8szz_Df+XprBBUBkEM5KQb85vfEPu0yCE_xZrJM=PuZyA@mail.gmail.com>
	<CAHC6v6jYUW9k7SgeDJn2z6zGTBP9FgG+Xrt4=BVf2KoK+Cfq+A@mail.gmail.com>
Message-ID: <CAJ6WS8tmY4dn0bU3-VFtRzsFO7fudApTFetnX-vWuDMO48Jf5Q@mail.gmail.com>

Hi Roman,
Thanks for the reply!

The PyPI link is now on:
http://qt-project.org/wiki/Get-PySide

The prebuilt windows packages link is now on:
http://qt-project.org/wiki/PySide_Binaries_Windows


If later I see other pages that require these links, I'll update it at that
time.



On Tue, Mar 19, 2013 at 12:14 AM, Roman Lacko <backup.rlacko at gmail.com>wrote:

> Hi,
>
> 2013/3/19 lndn <lndndev at gmail.com>
>
>> I just spent the weekend organizing some of the pyside wiki pages (
>> http://qt-project.org/wiki/PySide) and making small updates to the
>> content here and there.
>>
>> Still needs a lot of work, but if someone can take a look and tell me
>> what you think so far, I can start focusing on important areas.
>>
>> Thanks!
>>
>> Thanks for doing this!
>
> It would be great to put somewhere information about the PyPI page [1].
> It contains the installation instructions (for windows and linux) and full
> source code of PySide, Shiboken, PySideTool, examples and build scripts
> bundled in standard distutils package. Also here is the downloads page for
> prebuild windows packages and source budles [2]. I should put the
> information on wiki myself but never had time to do it.
>
> Thanks
> R.
>
> [1] https://pypi.python.org/pypi/PySide
> [2] http://releases.qt-project.org/pyside/
>
>
>> On Sun, Mar 17, 2013 at 9:17 AM, Stephan Deibel <sdeibel at wingware.com>wrote:
>>
>>> lndn wrote:
>>>
>>>> All the recent scary "PySide is Dead" emails really prompted me to
>>>> think about what we can do to improve the situation.  Not being familiar
>>>> with the PySide/Shiboken internals, I thought it would be a good idea to
>>>> start by cleaning up the wiki pages on qt-project.
>>>>
>>>> However, as I combed through these pages, I noticed that many of the
>>>> links were broken and pointing to old pyside.org <http://pyside.org>
>>>> pages that no longer exist and the content contains outdated and incomplete
>>>> information.  What is really needed is a major overhaul in updating the
>>>> content.
>>>>
>>>>
>>>> So what's the official word on a massive re-organizing of these pages?
>>>>  Can I just take the initiative and do it?  I'd like to start off by just
>>>> putting the wiki pages in some order so things are easy to find and then
>>>> later go through the content and update the content one page at a time.  My
>>>> goal is just to help users and developers easily navigate to the pages they
>>>> need.
>>>>
>>>> Any thoughts or people interested in helping would be great.
>>>>
>>>
>>> This would be very helpful!
>>>
>>> I have in the past found some of the missing pages on archive.org.  You
>>> can paste urls there in the WayBackMachine box and see dated archives of
>>> the page.  It would be great to put back some of that lost content (which I
>>> think was lost in the Nokia -> Digia transition).
>>>
>>> For outdated docs, it seems best to keep them somewhere (an archive
>>> area?) or clearly label them, rather than removing them for now.  I suspect
>>> some of these may be helpful to people trying to understand and move PySide
>>> forward.
>>>
>>> Thanks for offering to do this!
>>>
>>> - Stephan
>>>
>>>
>>
>> _______________________________________________
>> PySide mailing list
>> PySide at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/pyside
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130319/73c06c3c/attachment.html>

From backup.rlacko at gmail.com  Tue Mar 19 08:55:36 2013
From: backup.rlacko at gmail.com (Roman Lacko)
Date: Tue, 19 Mar 2013 08:55:36 +0100
Subject: [PySide] Resurrecting PySide
In-Reply-To: <CAJ6WS8tmY4dn0bU3-VFtRzsFO7fudApTFetnX-vWuDMO48Jf5Q@mail.gmail.com>
References: <CAJ6WS8tFZpScDnyYs12T+tnDZrEp+RHPLUW3J6VYBZFPyr98RA@mail.gmail.com>
	<5145EC8A.8080900@wingware.com>
	<CAJ6WS8szz_Df+XprBBUBkEM5KQb85vfEPu0yCE_xZrJM=PuZyA@mail.gmail.com>
	<CAHC6v6jYUW9k7SgeDJn2z6zGTBP9FgG+Xrt4=BVf2KoK+Cfq+A@mail.gmail.com>
	<CAJ6WS8tmY4dn0bU3-VFtRzsFO7fudApTFetnX-vWuDMO48Jf5Q@mail.gmail.com>
Message-ID: <CAHC6v6ibiWVTKeC9rKNHQCk11wiA_-YY0DQLhpvVEbO3xheYDQ@mail.gmail.com>

I appreciate your work, Thanks!

2013/3/19 lndn <lndndev at gmail.com>

> Hi Roman,
> Thanks for the reply!
>
> The PyPI link is now on:
> http://qt-project.org/wiki/Get-PySide
>
> The prebuilt windows packages link is now on:
> http://qt-project.org/wiki/PySide_Binaries_Windows
>
>
> If later I see other pages that require these links, I'll update it at
> that time.
>
>
>
> On Tue, Mar 19, 2013 at 12:14 AM, Roman Lacko <backup.rlacko at gmail.com>wrote:
>
>> Hi,
>>
>> 2013/3/19 lndn <lndndev at gmail.com>
>>
>>> I just spent the weekend organizing some of the pyside wiki pages (
>>> http://qt-project.org/wiki/PySide) and making small updates to the
>>> content here and there.
>>>
>>> Still needs a lot of work, but if someone can take a look and tell me
>>> what you think so far, I can start focusing on important areas.
>>>
>>> Thanks!
>>>
>>> Thanks for doing this!
>>
>> It would be great to put somewhere information about the PyPI page [1].
>> It contains the installation instructions (for windows and linux) and
>> full source code of PySide, Shiboken, PySideTool, examples and build
>> scripts bundled in standard distutils package. Also here is the downloads
>> page for prebuild windows packages and source budles [2]. I should put the
>> information on wiki myself but never had time to do it.
>>
>> Thanks
>> R.
>>
>> [1] https://pypi.python.org/pypi/PySide
>> [2] http://releases.qt-project.org/pyside/
>>
>>
>>> On Sun, Mar 17, 2013 at 9:17 AM, Stephan Deibel <sdeibel at wingware.com>wrote:
>>>
>>>> lndn wrote:
>>>>
>>>>> All the recent scary "PySide is Dead" emails really prompted me to
>>>>> think about what we can do to improve the situation.  Not being familiar
>>>>> with the PySide/Shiboken internals, I thought it would be a good idea to
>>>>> start by cleaning up the wiki pages on qt-project.
>>>>>
>>>>> However, as I combed through these pages, I noticed that many of the
>>>>> links were broken and pointing to old pyside.org <http://pyside.org>
>>>>> pages that no longer exist and the content contains outdated and incomplete
>>>>> information.  What is really needed is a major overhaul in updating the
>>>>> content.
>>>>>
>>>>>
>>>>> So what's the official word on a massive re-organizing of these pages?
>>>>>  Can I just take the initiative and do it?  I'd like to start off by just
>>>>> putting the wiki pages in some order so things are easy to find and then
>>>>> later go through the content and update the content one page at a time.  My
>>>>> goal is just to help users and developers easily navigate to the pages they
>>>>> need.
>>>>>
>>>>> Any thoughts or people interested in helping would be great.
>>>>>
>>>>
>>>> This would be very helpful!
>>>>
>>>> I have in the past found some of the missing pages on archive.org.
>>>>  You can paste urls there in the WayBackMachine box and see dated archives
>>>> of the page.  It would be great to put back some of that lost content
>>>> (which I think was lost in the Nokia -> Digia transition).
>>>>
>>>> For outdated docs, it seems best to keep them somewhere (an archive
>>>> area?) or clearly label them, rather than removing them for now.  I suspect
>>>> some of these may be helpful to people trying to understand and move PySide
>>>> forward.
>>>>
>>>> Thanks for offering to do this!
>>>>
>>>> - Stephan
>>>>
>>>>
>>>
>>> _______________________________________________
>>> PySide mailing list
>>> PySide at qt-project.org
>>> http://lists.qt-project.org/mailman/listinfo/pyside
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130319/da66e35d/attachment.html>

From lndndev at gmail.com  Tue Mar 19 11:31:11 2013
From: lndndev at gmail.com (lndn)
Date: Tue, 19 Mar 2013 03:31:11 -0700
Subject: [PySide] Additional pyside reviewers
In-Reply-To: <CAHfg+FNOYdEQ0M5vowLL5UAnN-eMwo_qyy-xQhvkKF_RwoPzAA@mail.gmail.com>
References: <CAJyon0vanPWaucHhhrq5wDnS-Tg91eMTdtfsS7172w4v0Eo=SA@mail.gmail.com>
	<1592310.DtA18LIKW2@hugodesktop> <514750BD.7060504@wingware.com>
	<2800764.YRBIifK68U@hugodesktop>
	<CAHfg+FNOYdEQ0M5vowLL5UAnN-eMwo_qyy-xQhvkKF_RwoPzAA@mail.gmail.com>
Message-ID: <CAJ6WS8sdyBUoGNm0KtfOygbZs6BNMKf0cka1=UPjiCk24ODycw@mail.gmail.com>

Great news, just heard back from Lars Knoll regarding how to add new
maintainers, see his email reply below.


On Tue, Mar 19, 2013 at 3:22 AM, Knoll Lars <Lars.Knoll at digia.com> wrote:

> Hi,
>
> yes, I'm in the position to add new maintainers. I'd say we follow the
> process we have on qt-project for this as well.
>
> Ideally, Hugo proposes a successor on the pyside mailing list. If he
> doesn't do it, I would propose to initiate a discussion about the best
> candidate on the ML. Please put me on CC, so I can follow the thread. If
> the person gets support on the ML, I'll give him formal maintainer status
> a little later.
>
> Cheers,
> Lars
>
> On 3/19/13 12:18 AM, "LNDN" wrote:
>
> >Hi Lars,
>
> >Are you in a position to add new maintainers to the PySide project?  And
> if so, what
> >do we need to do on our side to do this?
> >
> >
> >Thank you,
> >LNDN
> >
>


On Mon, Mar 18, 2013 at 9:49 PM, Matti Airas <mairas at iki.fi> wrote:

>
> On 18 Mar 2013 23:53, "Hugo Parente Lima" <hugo.lima at openbossa.org> wrote:
> > Yes, I want to step down as maintainer, I'm no longer working on PySide
> and
> > the code base in fading out from my memory month after month, the main
> problem
> > now is that I don't know who on Qt-Project is responsible for add/remove
> > approvers/maintainers.
>
> I'd like to thank on my behalf for the awesome contribution you've done
> for PySide over the past years. It's been quite incredible!
>
> The different roles and nomination process are described here:
>
> http://qt-project.org/wiki/The_Qt_Governance_Model
>
> Basically, you, Hugo, should just send an email your proposal to
> development at qt-project.org mailing list. A cc to Lars probably won't
> harm, but the reasoning should be in public.
>
> http://lists.qt-project.org/mailman/listinfo/development
>
> Nominating a bunch of new approvers at the same time probably wouldn't
> harm, either... :-)
>
> Cheers,
>
> ma.
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130319/d5bda49d/attachment.html>

From sable at users.sourceforge.net  Tue Mar 19 12:11:52 2013
From: sable at users.sourceforge.net (=?ISO-8859-1?Q?S=E9bastien_Sabl=E9?=)
Date: Tue, 19 Mar 2013 12:11:52 +0100
Subject: [PySide] Resurrecting PySide
In-Reply-To: <CAJ6WS8tmY4dn0bU3-VFtRzsFO7fudApTFetnX-vWuDMO48Jf5Q@mail.gmail.com>
References: <CAJ6WS8tFZpScDnyYs12T+tnDZrEp+RHPLUW3J6VYBZFPyr98RA@mail.gmail.com>
	<5145EC8A.8080900@wingware.com>
	<CAJ6WS8szz_Df+XprBBUBkEM5KQb85vfEPu0yCE_xZrJM=PuZyA@mail.gmail.com>
	<CAHC6v6jYUW9k7SgeDJn2z6zGTBP9FgG+Xrt4=BVf2KoK+Cfq+A@mail.gmail.com>
	<CAJ6WS8tmY4dn0bU3-VFtRzsFO7fudApTFetnX-vWuDMO48Jf5Q@mail.gmail.com>
Message-ID: <CAJqKL-suJnuCUw2gYh5p57F8R=cGzBkr3obnKwmLK8ECB39y1A@mail.gmail.com>

Hi,

thanks for help!
If you have time, it would be nice to put online the tutorial that Roman
posted a few weeks ago.
That is what got me started binding my own library.

I also did a bit of cleanup in the documentation a couple weeks ago (fixing
and moving to the right page the paths to git repositories, and explaining
that you need to go through gerrit to submit code for PySide).
If I can find some time, I will take a look at what you did and try to
help. I recently started to contribute to the project, so the limitations
of the doc are still fresh in my mind.
I would like to build a step by step tutorial on how to setup a linux
environment to checkout the git sources for pyside, build it, run the unit
tests, add some more tests, run a test in the debugger to fix it. This
could help to get more developers to contribute to the project rather than
just opening tickets.

regards

Sébastien



2013/3/19 lndn <lndndev at gmail.com>

> Hi Roman,
> Thanks for the reply!
>
> The PyPI link is now on:
> http://qt-project.org/wiki/Get-PySide
>
> The prebuilt windows packages link is now on:
> http://qt-project.org/wiki/PySide_Binaries_Windows
>
>
> If later I see other pages that require these links, I'll update it at
> that time.
>
>
>
> On Tue, Mar 19, 2013 at 12:14 AM, Roman Lacko <backup.rlacko at gmail.com>wrote:
>
>> Hi,
>>
>> 2013/3/19 lndn <lndndev at gmail.com>
>>
>>> I just spent the weekend organizing some of the pyside wiki pages (
>>> http://qt-project.org/wiki/PySide) and making small updates to the
>>> content here and there.
>>>
>>> Still needs a lot of work, but if someone can take a look and tell me
>>> what you think so far, I can start focusing on important areas.
>>>
>>> Thanks!
>>>
>>> Thanks for doing this!
>>
>> It would be great to put somewhere information about the PyPI page [1].
>> It contains the installation instructions (for windows and linux) and
>> full source code of PySide, Shiboken, PySideTool, examples and build
>> scripts bundled in standard distutils package. Also here is the downloads
>> page for prebuild windows packages and source budles [2]. I should put the
>> information on wiki myself but never had time to do it.
>>
>> Thanks
>> R.
>>
>> [1] https://pypi.python.org/pypi/PySide
>> [2] http://releases.qt-project.org/pyside/
>>
>>
>>> On Sun, Mar 17, 2013 at 9:17 AM, Stephan Deibel <sdeibel at wingware.com>wrote:
>>>
>>>> lndn wrote:
>>>>
>>>>> All the recent scary "PySide is Dead" emails really prompted me to
>>>>> think about what we can do to improve the situation.  Not being familiar
>>>>> with the PySide/Shiboken internals, I thought it would be a good idea to
>>>>> start by cleaning up the wiki pages on qt-project.
>>>>>
>>>>> However, as I combed through these pages, I noticed that many of the
>>>>> links were broken and pointing to old pyside.org <http://pyside.org>
>>>>> pages that no longer exist and the content contains outdated and incomplete
>>>>> information.  What is really needed is a major overhaul in updating the
>>>>> content.
>>>>>
>>>>>
>>>>> So what's the official word on a massive re-organizing of these pages?
>>>>>  Can I just take the initiative and do it?  I'd like to start off by just
>>>>> putting the wiki pages in some order so things are easy to find and then
>>>>> later go through the content and update the content one page at a time.  My
>>>>> goal is just to help users and developers easily navigate to the pages they
>>>>> need.
>>>>>
>>>>> Any thoughts or people interested in helping would be great.
>>>>>
>>>>
>>>> This would be very helpful!
>>>>
>>>> I have in the past found some of the missing pages on archive.org.
>>>>  You can paste urls there in the WayBackMachine box and see dated archives
>>>> of the page.  It would be great to put back some of that lost content
>>>> (which I think was lost in the Nokia -> Digia transition).
>>>>
>>>> For outdated docs, it seems best to keep them somewhere (an archive
>>>> area?) or clearly label them, rather than removing them for now.  I suspect
>>>> some of these may be helpful to people trying to understand and move PySide
>>>> forward.
>>>>
>>>> Thanks for offering to do this!
>>>>
>>>> - Stephan
>>>>
>>>>
>>>
>>> _______________________________________________
>>> PySide mailing list
>>> PySide at qt-project.org
>>> http://lists.qt-project.org/mailman/listinfo/pyside
>>>
>>>
>>
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130319/10f11aaa/attachment.html>

From lndndev at gmail.com  Tue Mar 19 12:23:13 2013
From: lndndev at gmail.com (lndn)
Date: Tue, 19 Mar 2013 04:23:13 -0700
Subject: [PySide] Resurrecting PySide
In-Reply-To: <CAJqKL-suJnuCUw2gYh5p57F8R=cGzBkr3obnKwmLK8ECB39y1A@mail.gmail.com>
References: <CAJ6WS8tFZpScDnyYs12T+tnDZrEp+RHPLUW3J6VYBZFPyr98RA@mail.gmail.com>
	<5145EC8A.8080900@wingware.com>
	<CAJ6WS8szz_Df+XprBBUBkEM5KQb85vfEPu0yCE_xZrJM=PuZyA@mail.gmail.com>
	<CAHC6v6jYUW9k7SgeDJn2z6zGTBP9FgG+Xrt4=BVf2KoK+Cfq+A@mail.gmail.com>
	<CAJ6WS8tmY4dn0bU3-VFtRzsFO7fudApTFetnX-vWuDMO48Jf5Q@mail.gmail.com>
	<CAJqKL-suJnuCUw2gYh5p57F8R=cGzBkr3obnKwmLK8ECB39y1A@mail.gmail.com>
Message-ID: <CAJ6WS8sQC3cSHZL8jKhkkdudV26N4V+MnzZS9V9r3jOPK_xK-g@mail.gmail.com>

Are you talking about Roman's tutorial right here:
http://qt-project.org/wiki/PySide_Shiboken_Tutorial

If you have time to write the step-by-step tutorial, that would be
phenomenal.  I also started doing something similar, but it's a getting
started guide for new developers.  Check it out here:
http://qt-project.org/wiki/PySide_Development_Getting_Started.  Just
started yesterday, so its far from done.

Thanks for helping out, we need more people to contribute!




On Tue, Mar 19, 2013 at 4:11 AM, Sébastien Sablé <
sable at users.sourceforge.net> wrote:

> Hi,
>
> thanks for help!
> If you have time, it would be nice to put online the tutorial that Roman
> posted a few weeks ago.
> That is what got me started binding my own library.
>
> I also did a bit of cleanup in the documentation a couple weeks ago
> (fixing and moving to the right page the paths to git repositories, and
> explaining that you need to go through gerrit to submit code for PySide).
> If I can find some time, I will take a look at what you did and try to
> help. I recently started to contribute to the project, so the limitations
> of the doc are still fresh in my mind.
> I would like to build a step by step tutorial on how to setup a linux
> environment to checkout the git sources for pyside, build it, run the unit
> tests, add some more tests, run a test in the debugger to fix it. This
> could help to get more developers to contribute to the project rather than
> just opening tickets.
>
> regards
>
> Sébastien
>
>
>
> 2013/3/19 lndn <lndndev at gmail.com>
>
>> Hi Roman,
>> Thanks for the reply!
>>
>> The PyPI link is now on:
>> http://qt-project.org/wiki/Get-PySide
>>
>> The prebuilt windows packages link is now on:
>> http://qt-project.org/wiki/PySide_Binaries_Windows
>>
>>
>> If later I see other pages that require these links, I'll update it at
>> that time.
>>
>>
>>
>> On Tue, Mar 19, 2013 at 12:14 AM, Roman Lacko <backup.rlacko at gmail.com>wrote:
>>
>>> Hi,
>>>
>>> 2013/3/19 lndn <lndndev at gmail.com>
>>>
>>>> I just spent the weekend organizing some of the pyside wiki pages (
>>>> http://qt-project.org/wiki/PySide) and making small updates to the
>>>> content here and there.
>>>>
>>>> Still needs a lot of work, but if someone can take a look and tell me
>>>> what you think so far, I can start focusing on important areas.
>>>>
>>>> Thanks!
>>>>
>>>> Thanks for doing this!
>>>
>>> It would be great to put somewhere information about the PyPI page [1].
>>> It contains the installation instructions (for windows and linux) and
>>> full source code of PySide, Shiboken, PySideTool, examples and build
>>> scripts bundled in standard distutils package. Also here is the downloads
>>> page for prebuild windows packages and source budles [2]. I should put the
>>> information on wiki myself but never had time to do it.
>>>
>>> Thanks
>>> R.
>>>
>>> [1] https://pypi.python.org/pypi/PySide
>>> [2] http://releases.qt-project.org/pyside/
>>>
>>>
>>>> On Sun, Mar 17, 2013 at 9:17 AM, Stephan Deibel <sdeibel at wingware.com>wrote:
>>>>
>>>>> lndn wrote:
>>>>>
>>>>>> All the recent scary "PySide is Dead" emails really prompted me to
>>>>>> think about what we can do to improve the situation.  Not being familiar
>>>>>> with the PySide/Shiboken internals, I thought it would be a good idea to
>>>>>> start by cleaning up the wiki pages on qt-project.
>>>>>>
>>>>>> However, as I combed through these pages, I noticed that many of the
>>>>>> links were broken and pointing to old pyside.org <http://pyside.org>
>>>>>> pages that no longer exist and the content contains outdated and incomplete
>>>>>> information.  What is really needed is a major overhaul in updating the
>>>>>> content.
>>>>>>
>>>>>>
>>>>>> So what's the official word on a massive re-organizing of these
>>>>>> pages?  Can I just take the initiative and do it?  I'd like to start off by
>>>>>> just putting the wiki pages in some order so things are easy to find and
>>>>>> then later go through the content and update the content one page at a
>>>>>> time.  My goal is just to help users and developers easily navigate to the
>>>>>> pages they need.
>>>>>>
>>>>>> Any thoughts or people interested in helping would be great.
>>>>>>
>>>>>
>>>>> This would be very helpful!
>>>>>
>>>>> I have in the past found some of the missing pages on archive.org.
>>>>>  You can paste urls there in the WayBackMachine box and see dated archives
>>>>> of the page.  It would be great to put back some of that lost content
>>>>> (which I think was lost in the Nokia -> Digia transition).
>>>>>
>>>>> For outdated docs, it seems best to keep them somewhere (an archive
>>>>> area?) or clearly label them, rather than removing them for now.  I suspect
>>>>> some of these may be helpful to people trying to understand and move PySide
>>>>> forward.
>>>>>
>>>>> Thanks for offering to do this!
>>>>>
>>>>> - Stephan
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> PySide mailing list
>>>> PySide at qt-project.org
>>>> http://lists.qt-project.org/mailman/listinfo/pyside
>>>>
>>>>
>>>
>>
>> _______________________________________________
>> PySide mailing list
>> PySide at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/pyside
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130319/a1d958ad/attachment.html>

From sable at users.sourceforge.net  Tue Mar 19 12:24:33 2013
From: sable at users.sourceforge.net (=?ISO-8859-1?Q?S=E9bastien_Sabl=E9?=)
Date: Tue, 19 Mar 2013 12:24:33 +0100
Subject: [PySide] Additional pyside reviewers
In-Reply-To: <CAJ6WS8sdyBUoGNm0KtfOygbZs6BNMKf0cka1=UPjiCk24ODycw@mail.gmail.com>
References: <CAJyon0vanPWaucHhhrq5wDnS-Tg91eMTdtfsS7172w4v0Eo=SA@mail.gmail.com>
	<1592310.DtA18LIKW2@hugodesktop> <514750BD.7060504@wingware.com>
	<2800764.YRBIifK68U@hugodesktop>
	<CAHfg+FNOYdEQ0M5vowLL5UAnN-eMwo_qyy-xQhvkKF_RwoPzAA@mail.gmail.com>
	<CAJ6WS8sdyBUoGNm0KtfOygbZs6BNMKf0cka1=UPjiCk24ODycw@mail.gmail.com>
Message-ID: <CAJqKL-ueNNa-q-_YOeH2P3UEoaVHY=qOHsGn_UU9ZDC+f+oiXg@mail.gmail.com>

Hi,

I got a couple bug fixes for shiboken merged into PySide the last few
weeks; I have a few more in the pipe.

I am too new on the project to be a code reviewer, however I also think
there is a lot of work needed on the issue tracker side:
https://bugreports.qt-project.org/browse/PYSIDE
There are 111 tickets that not been evaluated at all.

Would it be possible to get some rights so that I could change tickets?

I would like to start prioritizing them, possibly closing the one which do
not provide enough information to reproduce or that may be deprecated and
writing unit tests for those which have enough details.
Then I will try to fix one ticket per week depending on how much available
time I have.

best regards

Sébastien




2013/3/19 lndn <lndndev at gmail.com>

> Great news, just heard back from Lars Knoll regarding how to add new
> maintainers, see his email reply below.
>
>
> On Tue, Mar 19, 2013 at 3:22 AM, Knoll Lars <Lars.Knoll at digia.com> wrote:
>
>> Hi,
>>
>> yes, I'm in the position to add new maintainers. I'd say we follow the
>> process we have on qt-project for this as well.
>>
>> Ideally, Hugo proposes a successor on the pyside mailing list. If he
>> doesn't do it, I would propose to initiate a discussion about the best
>> candidate on the ML. Please put me on CC, so I can follow the thread. If
>> the person gets support on the ML, I'll give him formal maintainer status
>> a little later.
>>
>> Cheers,
>> Lars
>>
>> On 3/19/13 12:18 AM, "LNDN" wrote:
>>
>> >Hi Lars,
>>
>> >Are you in a position to add new maintainers to the PySide project?  And
>> if so, what
>> >do we need to do on our side to do this?
>> >
>> >
>> >Thank you,
>> >LNDN
>> >
>>
>
>
> On Mon, Mar 18, 2013 at 9:49 PM, Matti Airas <mairas at iki.fi> wrote:
>
>>
>> On 18 Mar 2013 23:53, "Hugo Parente Lima" <hugo.lima at openbossa.org>
>> wrote:
>> > Yes, I want to step down as maintainer, I'm no longer working on PySide
>> and
>> > the code base in fading out from my memory month after month, the main
>> problem
>> > now is that I don't know who on Qt-Project is responsible for add/remove
>> > approvers/maintainers.
>>
>> I'd like to thank on my behalf for the awesome contribution you've done
>> for PySide over the past years. It's been quite incredible!
>>
>> The different roles and nomination process are described here:
>>
>> http://qt-project.org/wiki/The_Qt_Governance_Model
>>
>> Basically, you, Hugo, should just send an email your proposal to
>> development at qt-project.org mailing list. A cc to Lars probably won't
>> harm, but the reasoning should be in public.
>>
>> http://lists.qt-project.org/mailman/listinfo/development
>>
>> Nominating a bunch of new approvers at the same time probably wouldn't
>> harm, either... :-)
>>
>> Cheers,
>>
>> ma.
>>
>> _______________________________________________
>> PySide mailing list
>> PySide at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/pyside
>>
>>
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130319/01cd8b54/attachment.html>

From lndndev at gmail.com  Tue Mar 19 12:38:40 2013
From: lndndev at gmail.com (lndn)
Date: Tue, 19 Mar 2013 04:38:40 -0700
Subject: [PySide] Additional pyside reviewers
In-Reply-To: <CAJqKL-ueNNa-q-_YOeH2P3UEoaVHY=qOHsGn_UU9ZDC+f+oiXg@mail.gmail.com>
References: <CAJyon0vanPWaucHhhrq5wDnS-Tg91eMTdtfsS7172w4v0Eo=SA@mail.gmail.com>
	<1592310.DtA18LIKW2@hugodesktop> <514750BD.7060504@wingware.com>
	<2800764.YRBIifK68U@hugodesktop>
	<CAHfg+FNOYdEQ0M5vowLL5UAnN-eMwo_qyy-xQhvkKF_RwoPzAA@mail.gmail.com>
	<CAJ6WS8sdyBUoGNm0KtfOygbZs6BNMKf0cka1=UPjiCk24ODycw@mail.gmail.com>
	<CAJqKL-ueNNa-q-_YOeH2P3UEoaVHY=qOHsGn_UU9ZDC+f+oiXg@mail.gmail.com>
Message-ID: <CAJ6WS8v4A2T093-w0MHnuLgKze8KGxr+wsd_=ch7bh8zA-=n+w@mail.gmail.com>

>  Would it be possible to get some rights so that I could change tickets?

I don't know the answer, but it's a good question.  My guess is that you
would need to become an Approver.  According to the Qt Governance Model (
http://qt-project.org/wiki/The_Qt_Governance_Model), an existing Approver
must nominate you and another to second that nomination.  But I don't know
if there are any Approvers left in the project for this to happen.  I think
Lars Knoll may be the only one who can do this (according to his email).
 If so, you have my vote of support.




On Tue, Mar 19, 2013 at 4:24 AM, Sébastien Sablé <
sable at users.sourceforge.net> wrote:

> Hi,
>
> I got a couple bug fixes for shiboken merged into PySide the last few
> weeks; I have a few more in the pipe.
>
> I am too new on the project to be a code reviewer, however I also think
> there is a lot of work needed on the issue tracker side:
> https://bugreports.qt-project.org/browse/PYSIDE
> There are 111 tickets that not been evaluated at all.
>
> Would it be possible to get some rights so that I could change tickets?
>
> I would like to start prioritizing them, possibly closing the one which do
> not provide enough information to reproduce or that may be deprecated and
> writing unit tests for those which have enough details.
> Then I will try to fix one ticket per week depending on how much available
> time I have.
>
> best regards
>
> Sébastien
>
>
>
>
> 2013/3/19 lndn <lndndev at gmail.com>
>
>> Great news, just heard back from Lars Knoll regarding how to add new
>> maintainers, see his email reply below.
>>
>>
>> On Tue, Mar 19, 2013 at 3:22 AM, Knoll Lars <Lars.Knoll at digia.com> wrote:
>>
>>> Hi,
>>>
>>> yes, I'm in the position to add new maintainers. I'd say we follow the
>>> process we have on qt-project for this as well.
>>>
>>> Ideally, Hugo proposes a successor on the pyside mailing list. If he
>>> doesn't do it, I would propose to initiate a discussion about the best
>>> candidate on the ML. Please put me on CC, so I can follow the thread. If
>>> the person gets support on the ML, I'll give him formal maintainer status
>>> a little later.
>>>
>>> Cheers,
>>> Lars
>>>
>>> On 3/19/13 12:18 AM, "LNDN" wrote:
>>>
>>> >Hi Lars,
>>>
>>> >Are you in a position to add new maintainers to the PySide project?
>>>  And if so, what
>>> >do we need to do on our side to do this?
>>> >
>>> >
>>> >Thank you,
>>> >LNDN
>>> >
>>>
>>
>>
>> On Mon, Mar 18, 2013 at 9:49 PM, Matti Airas <mairas at iki.fi> wrote:
>>
>>>
>>> On 18 Mar 2013 23:53, "Hugo Parente Lima" <hugo.lima at openbossa.org>
>>> wrote:
>>> > Yes, I want to step down as maintainer, I'm no longer working on
>>> PySide and
>>> > the code base in fading out from my memory month after month, the main
>>> problem
>>> > now is that I don't know who on Qt-Project is responsible for
>>> add/remove
>>> > approvers/maintainers.
>>>
>>> I'd like to thank on my behalf for the awesome contribution you've done
>>> for PySide over the past years. It's been quite incredible!
>>>
>>> The different roles and nomination process are described here:
>>>
>>> http://qt-project.org/wiki/The_Qt_Governance_Model
>>>
>>> Basically, you, Hugo, should just send an email your proposal to
>>> development at qt-project.org mailing list. A cc to Lars probably won't
>>> harm, but the reasoning should be in public.
>>>
>>> http://lists.qt-project.org/mailman/listinfo/development
>>>
>>> Nominating a bunch of new approvers at the same time probably wouldn't
>>> harm, either... :-)
>>>
>>> Cheers,
>>>
>>> ma.
>>>
>>> _______________________________________________
>>> PySide mailing list
>>> PySide at qt-project.org
>>> http://lists.qt-project.org/mailman/listinfo/pyside
>>>
>>>
>>
>> _______________________________________________
>> PySide mailing list
>> PySide at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/pyside
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130319/7c63333c/attachment.html>

From jcummings2 at users.sf.net  Tue Mar 19 14:43:55 2013
From: jcummings2 at users.sf.net (John Cummings)
Date: Tue, 19 Mar 2013 08:43:55 -0500
Subject: [PySide] Additional pyside reviewers
In-Reply-To: <CAHfg+FNOYdEQ0M5vowLL5UAnN-eMwo_qyy-xQhvkKF_RwoPzAA@mail.gmail.com>
References: <CAJyon0vanPWaucHhhrq5wDnS-Tg91eMTdtfsS7172w4v0Eo=SA@mail.gmail.com>
	<1592310.DtA18LIKW2@hugodesktop> <514750BD.7060504@wingware.com>
	<2800764.YRBIifK68U@hugodesktop>
	<CAHfg+FNOYdEQ0M5vowLL5UAnN-eMwo_qyy-xQhvkKF_RwoPzAA@mail.gmail.com>
Message-ID: <51486B9B.4060808@users.sf.net>

On 03/18/2013 11:49 PM, Matti Airas wrote:
>
>
> On 18 Mar 2013 23:53, "Hugo Parente Lima" <hugo.lima at openbossa.org
> <mailto:hugo.lima at openbossa.org>> wrote:
> > Yes, I want to step down as maintainer, I'm no longer working on PySide and
> > the code base in fading out from my memory month after month, the main problem
> > now is that I don't know who on Qt-Project is responsible for add/remove
> > approvers/maintainers.
>
> I'd like to thank on my behalf for the awesome contribution you've done for
> PySide over the past years. It's been quite incredible!
>
> The different roles and nomination process are described here:
>
> http://qt-project.org/wiki/The_Qt_Governance_Model
>
> Basically, you, Hugo, should just send an email your proposal to
> development at qt-project.org <mailto:development at qt-project.org> mailing list. A
> cc to Lars probably won't harm, but the reasoning should be in public.
>
> http://lists.qt-project.org/mailman/listinfo/development
>
> Nominating a bunch of new approvers at the same time probably wouldn't harm,
> either... :-)
>
> Cheers,
>
> ma.
>

Hugo, I second Matti's words of praise for your PySide work. Nice job. come back
anytime.

All, last year I volunteered to be a code reviewer. I'm still willing to do so
since it sounds like we need some new code reviewers.

Thank you,
John Cummings
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130319/6e6d583a/attachment.html>

From sable at users.sourceforge.net  Tue Mar 19 15:32:11 2013
From: sable at users.sourceforge.net (=?ISO-8859-1?Q?S=E9bastien_Sabl=E9?=)
Date: Tue, 19 Mar 2013 15:32:11 +0100
Subject: [PySide] Resurrecting PySide
In-Reply-To: <CAJ6WS8sQC3cSHZL8jKhkkdudV26N4V+MnzZS9V9r3jOPK_xK-g@mail.gmail.com>
References: <CAJ6WS8tFZpScDnyYs12T+tnDZrEp+RHPLUW3J6VYBZFPyr98RA@mail.gmail.com>
	<5145EC8A.8080900@wingware.com>
	<CAJ6WS8szz_Df+XprBBUBkEM5KQb85vfEPu0yCE_xZrJM=PuZyA@mail.gmail.com>
	<CAHC6v6jYUW9k7SgeDJn2z6zGTBP9FgG+Xrt4=BVf2KoK+Cfq+A@mail.gmail.com>
	<CAJ6WS8tmY4dn0bU3-VFtRzsFO7fudApTFetnX-vWuDMO48Jf5Q@mail.gmail.com>
	<CAJqKL-suJnuCUw2gYh5p57F8R=cGzBkr3obnKwmLK8ECB39y1A@mail.gmail.com>
	<CAJ6WS8sQC3cSHZL8jKhkkdudV26N4V+MnzZS9V9r3jOPK_xK-g@mail.gmail.com>
Message-ID: <CAJqKL-vGENVWiaZSVq9ewfuNPMZAd4KWQPbCh0NRKbJCHdrF1A@mail.gmail.com>

I am talking about the one mentioned in this email thread:
http://www.mail-archive.com/pyside at qt-project.org/msg00976.html

It is close to what is in the wiki, but providing the actual full project
and the build steps really helps a lot.

Your wiki page is a nice start to get the environment; at least it goes
into the right direction, great!


2013/3/19 lndn <lndndev at gmail.com>

> Are you talking about Roman's tutorial right here:
> http://qt-project.org/wiki/PySide_Shiboken_Tutorial
>
> If you have time to write the step-by-step tutorial, that would be
> phenomenal.  I also started doing something similar, but it's a getting
> started guide for new developers.  Check it out here:
> http://qt-project.org/wiki/PySide_Development_Getting_Started.  Just
> started yesterday, so its far from done.
>
> Thanks for helping out, we need more people to contribute!
>
>
>
>
> On Tue, Mar 19, 2013 at 4:11 AM, Sébastien Sablé <
> sable at users.sourceforge.net> wrote:
>
>> Hi,
>>
>> thanks for help!
>> If you have time, it would be nice to put online the tutorial that Roman
>> posted a few weeks ago.
>> That is what got me started binding my own library.
>>
>> I also did a bit of cleanup in the documentation a couple weeks ago
>> (fixing and moving to the right page the paths to git repositories, and
>> explaining that you need to go through gerrit to submit code for PySide).
>> If I can find some time, I will take a look at what you did and try to
>> help. I recently started to contribute to the project, so the limitations
>> of the doc are still fresh in my mind.
>> I would like to build a step by step tutorial on how to setup a linux
>> environment to checkout the git sources for pyside, build it, run the unit
>> tests, add some more tests, run a test in the debugger to fix it. This
>> could help to get more developers to contribute to the project rather than
>> just opening tickets.
>>
>> regards
>>
>> Sébastien
>>
>>
>>
>> 2013/3/19 lndn <lndndev at gmail.com>
>>
>>> Hi Roman,
>>> Thanks for the reply!
>>>
>>> The PyPI link is now on:
>>> http://qt-project.org/wiki/Get-PySide
>>>
>>> The prebuilt windows packages link is now on:
>>> http://qt-project.org/wiki/PySide_Binaries_Windows
>>>
>>>
>>> If later I see other pages that require these links, I'll update it at
>>> that time.
>>>
>>>
>>>
>>> On Tue, Mar 19, 2013 at 12:14 AM, Roman Lacko <backup.rlacko at gmail.com>wrote:
>>>
>>>> Hi,
>>>>
>>>> 2013/3/19 lndn <lndndev at gmail.com>
>>>>
>>>>> I just spent the weekend organizing some of the pyside wiki pages (
>>>>> http://qt-project.org/wiki/PySide) and making small updates to the
>>>>> content here and there.
>>>>>
>>>>> Still needs a lot of work, but if someone can take a look and tell me
>>>>> what you think so far, I can start focusing on important areas.
>>>>>
>>>>> Thanks!
>>>>>
>>>>> Thanks for doing this!
>>>>
>>>> It would be great to put somewhere information about the PyPI page [1].
>>>> It contains the installation instructions (for windows and linux) and
>>>> full source code of PySide, Shiboken, PySideTool, examples and build
>>>> scripts bundled in standard distutils package. Also here is the downloads
>>>> page for prebuild windows packages and source budles [2]. I should put the
>>>> information on wiki myself but never had time to do it.
>>>>
>>>> Thanks
>>>> R.
>>>>
>>>> [1] https://pypi.python.org/pypi/PySide
>>>> [2] http://releases.qt-project.org/pyside/
>>>>
>>>>
>>>>> On Sun, Mar 17, 2013 at 9:17 AM, Stephan Deibel <sdeibel at wingware.com>wrote:
>>>>>
>>>>>> lndn wrote:
>>>>>>
>>>>>>> All the recent scary "PySide is Dead" emails really prompted me to
>>>>>>> think about what we can do to improve the situation.  Not being familiar
>>>>>>> with the PySide/Shiboken internals, I thought it would be a good idea to
>>>>>>> start by cleaning up the wiki pages on qt-project.
>>>>>>>
>>>>>>> However, as I combed through these pages, I noticed that many of the
>>>>>>> links were broken and pointing to old pyside.org <http://pyside.org>
>>>>>>> pages that no longer exist and the content contains outdated and incomplete
>>>>>>> information.  What is really needed is a major overhaul in updating the
>>>>>>> content.
>>>>>>>
>>>>>>>
>>>>>>> So what's the official word on a massive re-organizing of these
>>>>>>> pages?  Can I just take the initiative and do it?  I'd like to start off by
>>>>>>> just putting the wiki pages in some order so things are easy to find and
>>>>>>> then later go through the content and update the content one page at a
>>>>>>> time.  My goal is just to help users and developers easily navigate to the
>>>>>>> pages they need.
>>>>>>>
>>>>>>> Any thoughts or people interested in helping would be great.
>>>>>>>
>>>>>>
>>>>>> This would be very helpful!
>>>>>>
>>>>>> I have in the past found some of the missing pages on archive.org.
>>>>>>  You can paste urls there in the WayBackMachine box and see dated archives
>>>>>> of the page.  It would be great to put back some of that lost content
>>>>>> (which I think was lost in the Nokia -> Digia transition).
>>>>>>
>>>>>> For outdated docs, it seems best to keep them somewhere (an archive
>>>>>> area?) or clearly label them, rather than removing them for now.  I suspect
>>>>>> some of these may be helpful to people trying to understand and move PySide
>>>>>> forward.
>>>>>>
>>>>>> Thanks for offering to do this!
>>>>>>
>>>>>> - Stephan
>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> PySide mailing list
>>>>> PySide at qt-project.org
>>>>> http://lists.qt-project.org/mailman/listinfo/pyside
>>>>>
>>>>>
>>>>
>>>
>>> _______________________________________________
>>> PySide mailing list
>>> PySide at qt-project.org
>>> http://lists.qt-project.org/mailman/listinfo/pyside
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130319/e52f98c6/attachment.html>

From jpe at wingware.com  Tue Mar 19 19:03:26 2013
From: jpe at wingware.com (John Ehresman)
Date: Tue, 19 Mar 2013 11:03:26 -0700
Subject: [PySide] Additional pyside reviewers
In-Reply-To: <CAJ6WS8vC__b3a4s2amuHkPtu1qS_J5=Z3Oicfd4Ayu5oRr3-WA@mail.gmail.com>
References: <CAJyon0vanPWaucHhhrq5wDnS-Tg91eMTdtfsS7172w4v0Eo=SA@mail.gmail.com>
	<1592310.DtA18LIKW2@hugodesktop> <514750BD.7060504@wingware.com>
	<2800764.YRBIifK68U@hugodesktop> <514799A0.7060505@wingware.com>
	<CAJ6WS8vC__b3a4s2amuHkPtu1qS_J5=Z3Oicfd4Ayu5oRr3-WA@mail.gmail.com>
Message-ID: <5148A86E.1010601@wingware.com>

On 3/18/13 7:57 PM, lndn wrote:
> Since I don't know who's who and the PySide contributors list
> (http://qt-project.org/wiki/PySideContributors) is way out of date, I'm
> wondering if any of the core developers are still around to contribute.
>  I just re-organized some of the pyside wiki pages
> (http://qt-project.org/wiki/PySide) and the development section really
> needs someone who is more knowledgeable to update the content, or maybe
> write a page or two.

Thanks for cleaning up some of the wiki pages!  I think we should wait
for new reviewers & maintainers to be added before updating the wiki;
this is likely to take a bit of time.

I wonder if we should somehow tag some of the pages as not being
reviewed or only link to them from an archive page.  There is useful
material in most of the pages, but it's sometimes hard to tell what is
up to date.

Cheers,

John



From hugo.lima at openbossa.org  Tue Mar 19 19:54:28 2013
From: hugo.lima at openbossa.org (Hugo Parente Lima)
Date: Tue, 19 Mar 2013 15:54:28 -0300
Subject: [PySide] Additional pyside reviewers
In-Reply-To: <CAHfg+FNOYdEQ0M5vowLL5UAnN-eMwo_qyy-xQhvkKF_RwoPzAA@mail.gmail.com>
References: <CAJyon0vanPWaucHhhrq5wDnS-Tg91eMTdtfsS7172w4v0Eo=SA@mail.gmail.com>
	<2800764.YRBIifK68U@hugodesktop>
	<CAHfg+FNOYdEQ0M5vowLL5UAnN-eMwo_qyy-xQhvkKF_RwoPzAA@mail.gmail.com>
Message-ID: <8523860.PdH7xHadSn@hugodesktop>

On Tuesday, March 19, 2013 06:49:42 AM Matti Airas wrote:
> On 18 Mar 2013 23:53, "Hugo Parente Lima" <hugo.lima at openbossa.org> wrote:
> > Yes, I want to step down as maintainer, I'm no longer working on PySide
> 
> and
> 
> > the code base in fading out from my memory month after month, the main
> 
> problem
> 
> > now is that I don't know who on Qt-Project is responsible for add/remove
> > approvers/maintainers.
> 
> I'd like to thank on my behalf for the awesome contribution you've done for
> PySide over the past years. It's been quite incredible!
> 
> The different roles and nomination process are described here:
> 
> http://qt-project.org/wiki/The_Qt_Governance_Model
> 
> Basically, you, Hugo, should just send an email your proposal to
> development at qt-project.org mailing list. A cc to Lars probably won't harm,
> but the reasoning should be in public.

E-mail sent, thanks Matti for pointing me the way.

http://lists.qt-project.org/pipermail/development/2013-March/010451.html

 
> http://lists.qt-project.org/mailman/listinfo/development
> 
> Nominating a bunch of new approvers at the same time probably wouldn't
> harm, either... :-)
> 
> Cheers,
> 
> ma.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130319/f63dc0c1/attachment.sig>

From vasure at gmail.com  Tue Mar 19 21:28:43 2013
From: vasure at gmail.com (Srini Kommoori)
Date: Tue, 19 Mar 2013 13:28:43 -0700
Subject: [PySide] Additional pyside reviewers
In-Reply-To: <8523860.PdH7xHadSn@hugodesktop>
References: <CAJyon0vanPWaucHhhrq5wDnS-Tg91eMTdtfsS7172w4v0Eo=SA@mail.gmail.com>
	<2800764.YRBIifK68U@hugodesktop>
	<CAHfg+FNOYdEQ0M5vowLL5UAnN-eMwo_qyy-xQhvkKF_RwoPzAA@mail.gmail.com>
	<8523860.PdH7xHadSn@hugodesktop>
Message-ID: <CAG_nbnt2UiJ4AVTzmu-GgV2Xz6mc8nY20kTNzVPjU5UpD_yWMw@mail.gmail.com>

Thanks and great to see the initiative.

I would like to propose a 30mins hangout every week. I started on Qt5 port
but don't know who is where and I am going at a snails pace. Hangout or
some kinda syncup would get us going and not to repeat each other.

Thanks,
-Srini

On Tue, Mar 19, 2013 at 11:54 AM, Hugo Parente Lima <hugo.lima at openbossa.org
> wrote:

> On Tuesday, March 19, 2013 06:49:42 AM Matti Airas wrote:
> > On 18 Mar 2013 23:53, "Hugo Parente Lima" <hugo.lima at openbossa.org>
> wrote:
> > > Yes, I want to step down as maintainer, I'm no longer working on PySide
> >
> > and
> >
> > > the code base in fading out from my memory month after month, the main
> >
> > problem
> >
> > > now is that I don't know who on Qt-Project is responsible for
> add/remove
> > > approvers/maintainers.
> >
> > I'd like to thank on my behalf for the awesome contribution you've done
> for
> > PySide over the past years. It's been quite incredible!
> >
> > The different roles and nomination process are described here:
> >
> > http://qt-project.org/wiki/The_Qt_Governance_Model
> >
> > Basically, you, Hugo, should just send an email your proposal to
> > development at qt-project.org mailing list. A cc to Lars probably won't
> harm,
> > but the reasoning should be in public.
>
> E-mail sent, thanks Matti for pointing me the way.
>
> http://lists.qt-project.org/pipermail/development/2013-March/010451.html
>
>
> > http://lists.qt-project.org/mailman/listinfo/development
> >
> > Nominating a bunch of new approvers at the same time probably wouldn't
> > harm, either... :-)
> >
> > Cheers,
> >
> > ma.
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130319/8143836d/attachment.html>

From jpe at wingware.com  Tue Mar 19 21:54:11 2013
From: jpe at wingware.com (John Ehresman)
Date: Tue, 19 Mar 2013 13:54:11 -0700
Subject: [PySide] Additional pyside reviewers
In-Reply-To: <CAG_nbnt2UiJ4AVTzmu-GgV2Xz6mc8nY20kTNzVPjU5UpD_yWMw@mail.gmail.com>
References: <CAJyon0vanPWaucHhhrq5wDnS-Tg91eMTdtfsS7172w4v0Eo=SA@mail.gmail.com>
	<2800764.YRBIifK68U@hugodesktop>
	<CAHfg+FNOYdEQ0M5vowLL5UAnN-eMwo_qyy-xQhvkKF_RwoPzAA@mail.gmail.com>
	<8523860.PdH7xHadSn@hugodesktop>
	<CAG_nbnt2UiJ4AVTzmu-GgV2Xz6mc8nY20kTNzVPjU5UpD_yWMw@mail.gmail.com>
Message-ID: <5148D073.6050800@wingware.com>

On 3/19/13 1:28 PM, Srini Kommoori wrote:
> Thanks and great to see the initiative. 
> 
> I would like to propose a 30mins hangout every week. I started on Qt5
> port but don't know who is where and I am going at a snails pace.
> Hangout or some kinda syncup would get us going and not to repeat each
> other. 

pyside still has an irc channel on freenode and I plan to stay logged in
there so poke me (jpe) if you have a question -- though I am going to be
traveling for the next couple of days.

Thanks,

John



From hugo.lima at openbossa.org  Tue Mar 19 21:54:55 2013
From: hugo.lima at openbossa.org (Hugo Parente Lima)
Date: Tue, 19 Mar 2013 17:54:55 -0300
Subject: [PySide] Additional pyside reviewers
In-Reply-To: <5148D073.6050800@wingware.com>
References: <CAJyon0vanPWaucHhhrq5wDnS-Tg91eMTdtfsS7172w4v0Eo=SA@mail.gmail.com>
	<CAG_nbnt2UiJ4AVTzmu-GgV2Xz6mc8nY20kTNzVPjU5UpD_yWMw@mail.gmail.com>
	<5148D073.6050800@wingware.com>
Message-ID: <3778250.j70eXGsWED@hugodesktop>

On Tuesday, March 19, 2013 01:54:11 PM John Ehresman wrote:
> On 3/19/13 1:28 PM, Srini Kommoori wrote:
> > Thanks and great to see the initiative.
> > 
> > I would like to propose a 30mins hangout every week. I started on Qt5
> > port but don't know who is where and I am going at a snails pace.
> > Hangout or some kinda syncup would get us going and not to repeat each
> > other.
> 
> pyside still has an irc channel on freenode and I plan to stay logged in
> there so poke me (jpe) if you have a question -- though I am going to be
> traveling for the next couple of days.

And I'll op+ the new maintainers/approvers.
 
> Thanks,
> 
> John
> 
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130319/0be18b0d/attachment.sig>

From lndndev at gmail.com  Tue Mar 19 23:18:14 2013
From: lndndev at gmail.com (lndn)
Date: Tue, 19 Mar 2013 15:18:14 -0700
Subject: [PySide] Resurrecting PySide
In-Reply-To: <CAJqKL-vGENVWiaZSVq9ewfuNPMZAd4KWQPbCh0NRKbJCHdrF1A@mail.gmail.com>
References: <CAJ6WS8tFZpScDnyYs12T+tnDZrEp+RHPLUW3J6VYBZFPyr98RA@mail.gmail.com>
	<5145EC8A.8080900@wingware.com>
	<CAJ6WS8szz_Df+XprBBUBkEM5KQb85vfEPu0yCE_xZrJM=PuZyA@mail.gmail.com>
	<CAHC6v6jYUW9k7SgeDJn2z6zGTBP9FgG+Xrt4=BVf2KoK+Cfq+A@mail.gmail.com>
	<CAJ6WS8tmY4dn0bU3-VFtRzsFO7fudApTFetnX-vWuDMO48Jf5Q@mail.gmail.com>
	<CAJqKL-suJnuCUw2gYh5p57F8R=cGzBkr3obnKwmLK8ECB39y1A@mail.gmail.com>
	<CAJ6WS8sQC3cSHZL8jKhkkdudV26N4V+MnzZS9V9r3jOPK_xK-g@mail.gmail.com>
	<CAJqKL-vGENVWiaZSVq9ewfuNPMZAd4KWQPbCh0NRKbJCHdrF1A@mail.gmail.com>
Message-ID: <CAJ6WS8t1KCJTASo8_=QGL8gch_NCbZx9g2Zh=0qBFK7SQs+uqA@mail.gmail.com>

Yeah, that email thread and the link I posted are one and the same thing.
 I haven't gone through the tutorial to check for errors yet, but I used
the thread to update the tutorial with useful info.

http://www.mail-archive.com/pyside at qt-project.org/msg00976.html
http://qt-project.org/wiki/PySide_Shiboken_Tutorial



Best regards,

Long Duong
UC Irvine School of Medicine
long at uci.edu
Cell:  949-872-1052

------------------------------
This message contains confidential information and is intended only for the
individual named. If you are not the named addressee you should not
disseminate, distribute or copy this e-mail. Please notify the sender
immediately by e-mail if you have received this e-mail by mistake and
delete this e-mail from your system. E-mail transmission cannot be
guaranteed to be secure or error-free as information could be intercepted,
corrupted, lost, destroyed, arrive late or incomplete, or contain viruses.
The sender therefore does not accept liability for any errors or omissions
in the contents of this message, which arise as a result of e-mail
transmission.


On Tue, Mar 19, 2013 at 7:32 AM, Sébastien Sablé <
sable at users.sourceforge.net> wrote:

> I am talking about the one mentioned in this email thread:
> http://www.mail-archive.com/pyside at qt-project.org/msg00976.html
>
> It is close to what is in the wiki, but providing the actual full project
> and the build steps really helps a lot.
>
> Your wiki page is a nice start to get the environment; at least it goes
> into the right direction, great!
>
>
> 2013/3/19 lndn <lndndev at gmail.com>
>
>> Are you talking about Roman's tutorial right here:
>> http://qt-project.org/wiki/PySide_Shiboken_Tutorial
>>
>> If you have time to write the step-by-step tutorial, that would be
>> phenomenal.  I also started doing something similar, but it's a getting
>> started guide for new developers.  Check it out here:
>> http://qt-project.org/wiki/PySide_Development_Getting_Started.  Just
>> started yesterday, so its far from done.
>>
>> Thanks for helping out, we need more people to contribute!
>>
>>
>>
>>
>> On Tue, Mar 19, 2013 at 4:11 AM, Sébastien Sablé <
>> sable at users.sourceforge.net> wrote:
>>
>>> Hi,
>>>
>>> thanks for help!
>>> If you have time, it would be nice to put online the tutorial that Roman
>>> posted a few weeks ago.
>>> That is what got me started binding my own library.
>>>
>>> I also did a bit of cleanup in the documentation a couple weeks ago
>>> (fixing and moving to the right page the paths to git repositories, and
>>> explaining that you need to go through gerrit to submit code for PySide).
>>> If I can find some time, I will take a look at what you did and try to
>>> help. I recently started to contribute to the project, so the limitations
>>> of the doc are still fresh in my mind.
>>> I would like to build a step by step tutorial on how to setup a linux
>>> environment to checkout the git sources for pyside, build it, run the unit
>>> tests, add some more tests, run a test in the debugger to fix it. This
>>> could help to get more developers to contribute to the project rather than
>>> just opening tickets.
>>>
>>> regards
>>>
>>> Sébastien
>>>
>>>
>>>
>>> 2013/3/19 lndn <lndndev at gmail.com>
>>>
>>>> Hi Roman,
>>>> Thanks for the reply!
>>>>
>>>> The PyPI link is now on:
>>>> http://qt-project.org/wiki/Get-PySide
>>>>
>>>> The prebuilt windows packages link is now on:
>>>> http://qt-project.org/wiki/PySide_Binaries_Windows
>>>>
>>>>
>>>> If later I see other pages that require these links, I'll update it at
>>>> that time.
>>>>
>>>>
>>>>
>>>> On Tue, Mar 19, 2013 at 12:14 AM, Roman Lacko <backup.rlacko at gmail.com>wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> 2013/3/19 lndn <lndndev at gmail.com>
>>>>>
>>>>>> I just spent the weekend organizing some of the pyside wiki pages (
>>>>>> http://qt-project.org/wiki/PySide) and making small updates to the
>>>>>> content here and there.
>>>>>>
>>>>>> Still needs a lot of work, but if someone can take a look and tell me
>>>>>> what you think so far, I can start focusing on important areas.
>>>>>>
>>>>>> Thanks!
>>>>>>
>>>>>> Thanks for doing this!
>>>>>
>>>>> It would be great to put somewhere information about the PyPI page [1].
>>>>> It contains the installation instructions (for windows and linux) and
>>>>> full source code of PySide, Shiboken, PySideTool, examples and build
>>>>> scripts bundled in standard distutils package. Also here is the downloads
>>>>> page for prebuild windows packages and source budles [2]. I should put the
>>>>> information on wiki myself but never had time to do it.
>>>>>
>>>>> Thanks
>>>>> R.
>>>>>
>>>>> [1] https://pypi.python.org/pypi/PySide
>>>>> [2] http://releases.qt-project.org/pyside/
>>>>>
>>>>>
>>>>>> On Sun, Mar 17, 2013 at 9:17 AM, Stephan Deibel <sdeibel at wingware.com
>>>>>> > wrote:
>>>>>>
>>>>>>> lndn wrote:
>>>>>>>
>>>>>>>> All the recent scary "PySide is Dead" emails really prompted me to
>>>>>>>> think about what we can do to improve the situation.  Not being familiar
>>>>>>>> with the PySide/Shiboken internals, I thought it would be a good idea to
>>>>>>>> start by cleaning up the wiki pages on qt-project.
>>>>>>>>
>>>>>>>> However, as I combed through these pages, I noticed that many of
>>>>>>>> the links were broken and pointing to old pyside.org <
>>>>>>>> http://pyside.org> pages that no longer exist and the content
>>>>>>>> contains outdated and incomplete information.  What is really needed is a
>>>>>>>> major overhaul in updating the content.
>>>>>>>>
>>>>>>>>
>>>>>>>> So what's the official word on a massive re-organizing of these
>>>>>>>> pages?  Can I just take the initiative and do it?  I'd like to start off by
>>>>>>>> just putting the wiki pages in some order so things are easy to find and
>>>>>>>> then later go through the content and update the content one page at a
>>>>>>>> time.  My goal is just to help users and developers easily navigate to the
>>>>>>>> pages they need.
>>>>>>>>
>>>>>>>> Any thoughts or people interested in helping would be great.
>>>>>>>>
>>>>>>>
>>>>>>> This would be very helpful!
>>>>>>>
>>>>>>> I have in the past found some of the missing pages on archive.org.
>>>>>>>  You can paste urls there in the WayBackMachine box and see dated archives
>>>>>>> of the page.  It would be great to put back some of that lost content
>>>>>>> (which I think was lost in the Nokia -> Digia transition).
>>>>>>>
>>>>>>> For outdated docs, it seems best to keep them somewhere (an archive
>>>>>>> area?) or clearly label them, rather than removing them for now.  I suspect
>>>>>>> some of these may be helpful to people trying to understand and move PySide
>>>>>>> forward.
>>>>>>>
>>>>>>> Thanks for offering to do this!
>>>>>>>
>>>>>>> - Stephan
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> PySide mailing list
>>>>>> PySide at qt-project.org
>>>>>> http://lists.qt-project.org/mailman/listinfo/pyside
>>>>>>
>>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> PySide mailing list
>>>> PySide at qt-project.org
>>>> http://lists.qt-project.org/mailman/listinfo/pyside
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130319/1c02664c/attachment.html>

From tismer at stackless.com  Wed Mar 20 08:41:00 2013
From: tismer at stackless.com (Christian Tismer)
Date: Wed, 20 Mar 2013 00:41:00 -0700
Subject: [PySide] Honkin Idea for PySide's thriving
Message-ID: <1F30AF68-F941-4786-B8D3-B65F1E1ABC97@stackless.com>

Hey friends, it struck me, and I want to share before it's gone. 

I am writing this in the spirit of the PyCon US pyside BOF:

Besides the technical issues and the things we discussed to create a real
PySide community, I would like to add a hew goal. 

Make PySide the new standard Gui toolkit for Python!

I see a lot of my core Python friends sharing my impression that PySide
Is a great thing. If we can push it enough, it could even be an officially supported toolkit for python-dev!

Either as a replacement or a supported alternative to Tcl/Tk, it could quite rapidly grow a pretty large community!

This is a very rough and fresh idea, and I would like to know what would be
Stopping us from doing that?

I see a lot of advantages by going this far. We could even move away from PySide's object layout and invent a really pythonic new implementation. 

Comments are welcome -- chris

Sent from my Ei4Steve

From mairas at iki.fi  Wed Mar 20 08:57:02 2013
From: mairas at iki.fi (Matti Airas)
Date: Wed, 20 Mar 2013 09:57:02 +0200
Subject: [PySide] Honkin Idea for PySide's thriving
In-Reply-To: <1F30AF68-F941-4786-B8D3-B65F1E1ABC97@stackless.com>
References: <1F30AF68-F941-4786-B8D3-B65F1E1ABC97@stackless.com>
Message-ID: <CAHfg+FOj7+VLhRooZfZ9HWOqUKH=cO2+K3GiUVQNXQEZoOXxGw@mail.gmail.com>

On 20 March 2013 09:41, Christian Tismer <tismer at stackless.com> wrote:

> Make PySide the new standard Gui toolkit for Python!
>
> I see a lot of my core Python friends sharing my impression that PySide
> Is a great thing. If we can push it enough, it could even be an officially
> supported toolkit for python-dev!
>
> Either as a replacement or a supported alternative to Tcl/Tk, it could
> quite rapidly grow a pretty large community!
>
> This is a very rough and fresh idea, and I would like to know what would be
> Stopping us from doing that?
>

Hi Christian,

It sounds like a nice idea that would help a lot in the long term, as long
as the short-term issues are effectively dealt with.

This would of course require discussion with PSF, but it doesn't sound
impossible. However, I believe they would require a license change from
LGPL to PSL. I think this would be doable for the individual contributors,
but a bigger question mark would be the Nokia-copyrighted contributions.
I'm not sure whether they were sold to Digia when they bought Qt. If so,
we'd need to convince Digia to let go of their commercial prospects towards
PySide. They haven't shown much practical interest so far, so I don't know
whether it would be feasible or not. However, if the copyright is still
owned by Nokia, it might get hairy - you'd need to find a person within the
current, heavily pruned organization and negotiate the licence change. It
could still be doable, but not necessarily straightforward.

Just my 2 c. :-)

Cheers,

ma.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130320/55a1601d/attachment.html>

From techtonik at gmail.com  Wed Mar 20 09:46:27 2013
From: techtonik at gmail.com (anatoly techtonik)
Date: Wed, 20 Mar 2013 11:46:27 +0300
Subject: [PySide] Honkin Idea for PySide's thriving
In-Reply-To: <1F30AF68-F941-4786-B8D3-B65F1E1ABC97@stackless.com>
References: <1F30AF68-F941-4786-B8D3-B65F1E1ABC97@stackless.com>
Message-ID: <CAPkN8xKM_zn93XTOBEiCueef1prpvqTD1bcDZ2K7FBSqBJLbbQ@mail.gmail.com>

On Wed, Mar 20, 2013 at 10:41 AM, Christian Tismer <tismer at stackless.com>wrote:

> Hey friends, it struck me, and I want to share before it's gone.
>
> I am writing this in the spirit of the PyCon US pyside BOF:
>
> Besides the technical issues and the things we discussed to create a real
> PySide community, I would like to add a hew goal.
>
> Make PySide the new standard Gui toolkit for Python!
>
> I see a lot of my core Python friends sharing my impression that PySide
> Is a great thing. If we can push it enough, it could even be an officially
> supported toolkit for python-dev!
>
> Either as a replacement or a supported alternative to Tcl/Tk, it could
> quite rapidly grow a pretty large community!
>
> This is a very rough and fresh idea, and I would like to know what would be
> Stopping us from doing that?
>
> I see a lot of advantages by going this far. We could even move away from
> PySide's object layout and invent a really pythonic new implementation.
>
> Comments are welcome -- chris
>

Few concerns.
1. Security
- all Qt security bugs are actual for PySide (all?)
- Python release cycle is longer than PySide
  = there should be a mechanism to have faster release cycle for PySide
than for the Python
     - this means shipping Python with PySide in site-packages/
       - which creates problems with all operating systems except Windows
         - and requires Python to invent its guidelines for those systems
           - which means it should have an understanding how different
systems handle it
             - which means there that some guidelines for OS developers
from Python should appear
               to help people *understand* Python distribution model and
*why* it is important
               - because often docs fail to explain why, and it is essential
     - this also means ability to detect when PySide needs updating
       - https://code.google.com/p/winpython/wiki/ControlPanel

2. Run-time size
- i don't want my server process to accidentally load PySide and eat all
the memory
  - which means that PySide (and GUI stuff in general) should not be copied
to virtualenv
    - which means that stdlib probably needs a split into core and GUI
things
      - and scientific community probably knows the problem and can show
some approaches
  - probably virtualenv should have an ability to copy stdlib without heavy
GUI or other stuff
    - for that stdlib needs partitioning
      - which means you can operate on stdlib module information
      - and query different info (which partition a module belongs, which
module is a file belongs, ..)
        - https://bitbucket.org/techtonik/python-stdlib

3. OpenGL canvas can be more useful
- direct access to hardware
- cross-platform API without intermediates
- requires a good user story based approach though, as it is not that simple

There were more concerns here. I am not sure if they are actual. In fact, I
have to go, so I can not even reread this.
http://mail.python.org/pipermail/python-dev/2009-November/094011.html

Some more ideas.

- IPython folks should be interested - if they are at PyCon, please talk to
them.
- Hugo said that the code base in fading out from his memory. That's
something that should be acted upon rather soon. We need to increase the
bus factor, and that means put more effort in simplifying codebase or at
least documenting it while it is still possible. Maybe some software
preservation fund, I don't know. Never worked with funds.
- A X/MIT-like license (not even PSF license) will definitely steer more
interest.
-- 
anatoly t.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130320/a3944a5f/attachment.html>

From techtonik at gmail.com  Wed Mar 20 09:52:06 2013
From: techtonik at gmail.com (anatoly techtonik)
Date: Wed, 20 Mar 2013 11:52:06 +0300
Subject: [PySide] Honkin Idea for PySide's thriving
In-Reply-To: <CAPkN8xKM_zn93XTOBEiCueef1prpvqTD1bcDZ2K7FBSqBJLbbQ@mail.gmail.com>
References: <1F30AF68-F941-4786-B8D3-B65F1E1ABC97@stackless.com>
	<CAPkN8xKM_zn93XTOBEiCueef1prpvqTD1bcDZ2K7FBSqBJLbbQ@mail.gmail.com>
Message-ID: <CAPkN8x+Sor6P3DVP994P_JT6wCWS8QKeU7HCV+Ts+uL+KRDUCA@mail.gmail.com>

Forgot to add the main point - that would be AWESOME! =)

-- 
anatoly t.


On Wed, Mar 20, 2013 at 11:46 AM, anatoly techtonik <techtonik at gmail.com>wrote:

> On Wed, Mar 20, 2013 at 10:41 AM, Christian Tismer <tismer at stackless.com>wrote:
>
>> Hey friends, it struck me, and I want to share before it's gone.
>>
>> I am writing this in the spirit of the PyCon US pyside BOF:
>>
>> Besides the technical issues and the things we discussed to create a real
>> PySide community, I would like to add a hew goal.
>>
>> Make PySide the new standard Gui toolkit for Python!
>>
>> I see a lot of my core Python friends sharing my impression that PySide
>> Is a great thing. If we can push it enough, it could even be an
>> officially supported toolkit for python-dev!
>>
>> Either as a replacement or a supported alternative to Tcl/Tk, it could
>> quite rapidly grow a pretty large community!
>>
>> This is a very rough and fresh idea, and I would like to know what would
>> be
>> Stopping us from doing that?
>>
>> I see a lot of advantages by going this far. We could even move away from
>> PySide's object layout and invent a really pythonic new implementation.
>>
>> Comments are welcome -- chris
>>
>
> Few concerns.
> 1. Security
> - all Qt security bugs are actual for PySide (all?)
> - Python release cycle is longer than PySide
>   = there should be a mechanism to have faster release cycle for PySide
> than for the Python
>      - this means shipping Python with PySide in site-packages/
>        - which creates problems with all operating systems except Windows
>          - and requires Python to invent its guidelines for those systems
>            - which means it should have an understanding how different
> systems handle it
>              - which means there that some guidelines for OS developers
> from Python should appear
>                to help people *understand* Python distribution model and
> *why* it is important
>                - because often docs fail to explain why, and it is
> essential
>      - this also means ability to detect when PySide needs updating
>        - https://code.google.com/p/winpython/wiki/ControlPanel
>
> 2. Run-time size
> - i don't want my server process to accidentally load PySide and eat all
> the memory
>   - which means that PySide (and GUI stuff in general) should not be
> copied to virtualenv
>     - which means that stdlib probably needs a split into core and GUI
> things
>       - and scientific community probably knows the problem and can show
> some approaches
>   - probably virtualenv should have an ability to copy stdlib without
> heavy GUI or other stuff
>     - for that stdlib needs partitioning
>       - which means you can operate on stdlib module information
>       - and query different info (which partition a module belongs, which
> module is a file belongs, ..)
>         - https://bitbucket.org/techtonik/python-stdlib
>
> 3. OpenGL canvas can be more useful
> - direct access to hardware
> - cross-platform API without intermediates
> - requires a good user story based approach though, as it is not that
> simple
>
> There were more concerns here. I am not sure if they are actual. In fact,
> I have to go, so I can not even reread this.
> http://mail.python.org/pipermail/python-dev/2009-November/094011.html
>
> Some more ideas.
>
> - IPython folks should be interested - if they are at PyCon, please talk
> to them.
> - Hugo said that the code base in fading out from his memory. That's
> something that should be acted upon rather soon. We need to increase the
> bus factor, and that means put more effort in simplifying codebase or at
> least documenting it while it is still possible. Maybe some software
> preservation fund, I don't know. Never worked with funds.
> - A X/MIT-like license (not even PSF license) will definitely steer more
> interest.
>  --
> anatoly t.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130320/0031924c/attachment.html>

From robert.kern at gmail.com  Wed Mar 20 12:10:58 2013
From: robert.kern at gmail.com (Robert Kern)
Date: Wed, 20 Mar 2013 11:10:58 +0000
Subject: [PySide] Honkin Idea for PySide's thriving
In-Reply-To: <1F30AF68-F941-4786-B8D3-B65F1E1ABC97@stackless.com>
References: <1F30AF68-F941-4786-B8D3-B65F1E1ABC97@stackless.com>
Message-ID: <kic5fv$t34$1@ger.gmane.org>

On 2013-03-20 07:41, Christian Tismer wrote:
> Hey friends, it struck me, and I want to share before it's gone.
>
> I am writing this in the spirit of the PyCon US pyside BOF:
>
> Besides the technical issues and the things we discussed to create a real
> PySide community, I would like to add a hew goal.
>
> Make PySide the new standard Gui toolkit for Python!
>
> I see a lot of my core Python friends sharing my impression that PySide
> Is a great thing. If we can push it enough, it could even be an officially supported toolkit for python-dev!
>
> Either as a replacement or a supported alternative to Tcl/Tk, it could quite rapidly grow a pretty large community!
>
> This is a very rough and fresh idea, and I would like to know what would be
> Stopping us from doing that?

Do you mean putting PySide into the standard library like Tkinter? Legal and 
technical showstoppers aside, I do not think that will work to PySide's benefit. 
PySide needs much more frequent updates than the standard library's development 
cycle permits. Development of a library does not speed up by putting it into the 
standard library. Rather, development slows to a crawl of cautious bugfixes. One 
doesn't get a large community of users by being in the standard library; one 
*might* get into the standard library by already having a large community of 
users. I think PySide will flourish best outside of the standard library.

-- 
Robert Kern

"I have come to believe that the whole world is an enigma, a harmless enigma
  that is made terrible by our own mad attempt to interpret it as though it had
  an underlying truth."
   -- Umberto Eco



From toddrme2178 at gmail.com  Wed Mar 20 13:10:40 2013
From: toddrme2178 at gmail.com (todd rme)
Date: Wed, 20 Mar 2013 13:10:40 +0100
Subject: [PySide] Honkin Idea for PySide's thriving
In-Reply-To: <kic5fv$t34$1@ger.gmane.org>
References: <1F30AF68-F941-4786-B8D3-B65F1E1ABC97@stackless.com>
	<kic5fv$t34$1@ger.gmane.org>
Message-ID: <CADb7s=suDXNDhZVSBGFBnoHRWT6UVq4VrWLiVihNpRWX4rJmaA@mail.gmail.com>

On Wed, Mar 20, 2013 at 12:10 PM, Robert Kern <robert.kern at gmail.com> wrote:
> On 2013-03-20 07:41, Christian Tismer wrote:
>> Hey friends, it struck me, and I want to share before it's gone.
>>
>> I am writing this in the spirit of the PyCon US pyside BOF:
>>
>> Besides the technical issues and the things we discussed to create a real
>> PySide community, I would like to add a hew goal.
>>
>> Make PySide the new standard Gui toolkit for Python!
>>
>> I see a lot of my core Python friends sharing my impression that PySide
>> Is a great thing. If we can push it enough, it could even be an officially supported toolkit for python-dev!
>>
>> Either as a replacement or a supported alternative to Tcl/Tk, it could quite rapidly grow a pretty large community!
>>
>> This is a very rough and fresh idea, and I would like to know what would be
>> Stopping us from doing that?
>
> Do you mean putting PySide into the standard library like Tkinter? Legal and
> technical showstoppers aside, I do not think that will work to PySide's benefit.
> PySide needs much more frequent updates than the standard library's development
> cycle permits. Development of a library does not speed up by putting it into the
> standard library. Rather, development slows to a crawl of cautious bugfixes. One
> doesn't get a large community of users by being in the standard library; one
> *might* get into the standard library by already having a large community of
> users. I think PySide will flourish best outside of the standard library.


I would have to agree here.  I think the chances of pyside getting
accepted are essentially zero, and if it was accepted it would slow
the pace of development to a crawl and make it difficult, if not
impossible, to keep up with upstream Qt changes.

I also agree that this probably won't even help us.  How many people
really use the tk GUI backend for python?  Most python GUIs I see
around use PyQt.

So then what can be done to improve pyside's adoption?  You really
need something to make using pyside better for developers than using
pyqt4.

I am more on the science side, but I do a lot of python packaging and
most GUI programs I see rely on pyqwt, either directly or (more often
these days) through guiqwt+guidata, especially for things using plots
and graphs.  This is despite the fact that pyqwt is unmaintained and
will almost certainly never be ported to python3.  This is one key
area where pyqt4 has a major advantage over all other competing python
gui toolkits, including pyside.  I think as long as pyside does not
either have either the same bindings, or at least some sort of good
low-level plotting and data display system, it is going to be hard to
make a compelling case to switch.


From sdeibel at wingware.com  Wed Mar 20 15:54:57 2013
From: sdeibel at wingware.com (Stephan Deibel)
Date: Wed, 20 Mar 2013 10:54:57 -0400
Subject: [PySide] Honkin Idea for PySide's thriving
In-Reply-To: <1F30AF68-F941-4786-B8D3-B65F1E1ABC97@stackless.com>
References: <1F30AF68-F941-4786-B8D3-B65F1E1ABC97@stackless.com>
Message-ID: <5149CDC1.8080406@wingware.com>

Christian Tismer wrote:
> Make PySide the new standard Gui toolkit for Python!

I'm also a bit concerned it would slow things down and might be hard 
given the copyright ownership.  It seems like an idea to keep in mind 
for the future, but there is much to do before I would attempt this.

- Stephan



From heng at cantab.net  Wed Mar 20 16:04:01 2013
From: heng at cantab.net (Henry Gomersall)
Date: Wed, 20 Mar 2013 15:04:01 +0000
Subject: [PySide] Honkin Idea for PySide's thriving
In-Reply-To: <1F30AF68-F941-4786-B8D3-B65F1E1ABC97@stackless.com>
References: <1F30AF68-F941-4786-B8D3-B65F1E1ABC97@stackless.com>
Message-ID: <1363791841.13681.5.camel@farnsworth>

On Wed, 2013-03-20 at 00:41 -0700, Christian Tismer wrote:
> Besides the technical issues and the things we discussed to create a
> real
> PySide community, I would like to add a hew goal. 
> 
> Make PySide the new standard Gui toolkit for Python!

Given Ubuntu's recent noises about Qt and QML, in particular with
respect to Ubuntu Touch (http://en.wikipedia.org/wiki/Ubuntu_Touch),
would perhaps a better target be to derive some support from that
direction?

To quote from the Ubuntu developers resources
(http://developer.ubuntu.com/resources/programming-languages/python/):

"Many important parts of Ubuntu are already written directly in Python,
and we work to make every important API and framework within Ubuntu
available from Python."

Cheers,

Henry



From nathanjsmith at gmail.com  Wed Mar 20 16:31:40 2013
From: nathanjsmith at gmail.com (Nathan Smith)
Date: Wed, 20 Mar 2013 10:31:40 -0500
Subject: [PySide] Honkin Idea for PySide's thriving
In-Reply-To: <1363791841.13681.5.camel@farnsworth>
References: <1F30AF68-F941-4786-B8D3-B65F1E1ABC97@stackless.com>
	<1363791841.13681.5.camel@farnsworth>
Message-ID: <CAK1cDb33kF3F_qB4Q_pwa4SYJgPTB5aXFuus4b5xg7pk8AMoSg@mail.gmail.com>

Ubuntu seems like a really good candidate for PySide sponsorship,
especially if they are going after commercial developers for their
phones/tablets. PySide's licence could be a key selling point.

Nathan
On Mar 20, 2013 10:04 AM, "Henry Gomersall" <heng at cantab.net> wrote:

> On Wed, 2013-03-20 at 00:41 -0700, Christian Tismer wrote:
> > Besides the technical issues and the things we discussed to create a
> > real
> > PySide community, I would like to add a hew goal.
> >
> > Make PySide the new standard Gui toolkit for Python!
>
> Given Ubuntu's recent noises about Qt and QML, in particular with
> respect to Ubuntu Touch (http://en.wikipedia.org/wiki/Ubuntu_Touch),
> would perhaps a better target be to derive some support from that
> direction?
>
> To quote from the Ubuntu developers resources
> (http://developer.ubuntu.com/resources/programming-languages/python/):
>
> "Many important parts of Ubuntu are already written directly in Python,
> and we work to make every important API and framework within Ubuntu
> available from Python."
>
> Cheers,
>
> Henry
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130320/c6d1cf6a/attachment.html>

From heng at cantab.net  Wed Mar 20 16:34:04 2013
From: heng at cantab.net (Henry Gomersall)
Date: Wed, 20 Mar 2013 15:34:04 +0000
Subject: [PySide] Honkin Idea for PySide's thriving
In-Reply-To: <CAK1cDb33kF3F_qB4Q_pwa4SYJgPTB5aXFuus4b5xg7pk8AMoSg@mail.gmail.com>
References: <1F30AF68-F941-4786-B8D3-B65F1E1ABC97@stackless.com>
	<1363791841.13681.5.camel@farnsworth>
	<CAK1cDb33kF3F_qB4Q_pwa4SYJgPTB5aXFuus4b5xg7pk8AMoSg@mail.gmail.com>
Message-ID: <1363793644.13681.7.camel@farnsworth>

On Wed, 2013-03-20 at 10:31 -0500, Nathan Smith wrote:
> Ubuntu seems like a really good candidate for PySide sponsorship,
> especially if they are going after commercial developers for their
> phones/tablets. PySide's licence could be a key selling point.

Though Canonical striking out on a brand new project is not without
precedent.

hen



From toddrme2178 at gmail.com  Wed Mar 20 16:34:24 2013
From: toddrme2178 at gmail.com (todd rme)
Date: Wed, 20 Mar 2013 16:34:24 +0100
Subject: [PySide] Honkin Idea for PySide's thriving
In-Reply-To: <CAK1cDb33kF3F_qB4Q_pwa4SYJgPTB5aXFuus4b5xg7pk8AMoSg@mail.gmail.com>
References: <1F30AF68-F941-4786-B8D3-B65F1E1ABC97@stackless.com>
	<1363791841.13681.5.camel@farnsworth>
	<CAK1cDb33kF3F_qB4Q_pwa4SYJgPTB5aXFuus4b5xg7pk8AMoSg@mail.gmail.com>
Message-ID: <CADb7s=v98T1ZO6+SoYXVOV9hSy-4JrnbStFLrg3NOTxhORbS4w@mail.gmail.com>

On Wed, Mar 20, 2013 at 4:31 PM, Nathan Smith <nathanjsmith at gmail.com> wrote:
> On Mar 20, 2013 10:04 AM, "Henry Gomersall" <heng at cantab.net> wrote:
>>
>> On Wed, 2013-03-20 at 00:41 -0700, Christian Tismer wrote:
>> > Besides the technical issues and the things we discussed to create a
>> > real
>> > PySide community, I would like to add a hew goal.
>> >
>> > Make PySide the new standard Gui toolkit for Python!
>>
>> Given Ubuntu's recent noises about Qt and QML, in particular with
>> respect to Ubuntu Touch (http://en.wikipedia.org/wiki/Ubuntu_Touch),
>> would perhaps a better target be to derive some support from that
>> direction?
>>
>> To quote from the Ubuntu developers resources
>> (http://developer.ubuntu.com/resources/programming-languages/python/):
>>
>> "Many important parts of Ubuntu are already written directly in Python,
>> and we work to make every important API and framework within Ubuntu
>> available from Python."
>>
>> Cheers,
>>
>> Henry
>
> Ubuntu seems like a really good candidate for PySide sponsorship, especially
> if they are going after commercial developers for their phones/tablets.
> PySide's licence could be a key selling point.
>
> Nathan

Only if you want to sign Ubuntu's CLA.


From david at wireplant.com  Wed Mar 20 16:46:24 2013
From: david at wireplant.com (David Brandse)
Date: Wed, 20 Mar 2013 11:46:24 -0400
Subject: [PySide] Resurrecting PySide
In-Reply-To: <CAJ6WS8t1KCJTASo8_=QGL8gch_NCbZx9g2Zh=0qBFK7SQs+uqA@mail.gmail.com>
References: <CAJ6WS8tFZpScDnyYs12T+tnDZrEp+RHPLUW3J6VYBZFPyr98RA@mail.gmail.com>
	<5145EC8A.8080900@wingware.com>
	<CAJ6WS8szz_Df+XprBBUBkEM5KQb85vfEPu0yCE_xZrJM=PuZyA@mail.gmail.com>
	<CAHC6v6jYUW9k7SgeDJn2z6zGTBP9FgG+Xrt4=BVf2KoK+Cfq+A@mail.gmail.com>
	<CAJ6WS8tmY4dn0bU3-VFtRzsFO7fudApTFetnX-vWuDMO48Jf5Q@mail.gmail.com>
	<CAJqKL-suJnuCUw2gYh5p57F8R=cGzBkr3obnKwmLK8ECB39y1A@mail.gmail.com>
	<CAJ6WS8sQC3cSHZL8jKhkkdudV26N4V+MnzZS9V9r3jOPK_xK-g@mail.gmail.com>
	<CAJqKL-vGENVWiaZSVq9ewfuNPMZAd4KWQPbCh0NRKbJCHdrF1A@mail.gmail.com>
	<CAJ6WS8t1KCJTASo8_=QGL8gch_NCbZx9g2Zh=0qBFK7SQs+uqA@mail.gmail.com>
Message-ID: <CAFX=CeKCdqrOu6g+SztE3OB+H3S2ubZG7HUnGOn6X3YRf__bPQ@mail.gmail.com>

One of the things I've noticed about people posting the "PySide is dead"
threads seems to be that they will ask a question either here or in IRC and
wait a few days for an answer, in the event that they don't get an answer
the immediate response seems to be that the project is dead. Perhaps one of
the areas that should be focused on is helping out users on the mailing
list with problems.
 - David


On Tue, Mar 19, 2013 at 6:18 PM, lndn <lndndev at gmail.com> wrote:

> Yeah, that email thread and the link I posted are one and the same thing.
>  I haven't gone through the tutorial to check for errors yet, but I used
> the thread to update the tutorial with useful info.
>
> http://www.mail-archive.com/pyside at qt-project.org/msg00976.html
> http://qt-project.org/wiki/PySide_Shiboken_Tutorial
>
>
>
> Best regards,
>
> Long Duong
> UC Irvine School of Medicine
> long at uci.edu
> Cell:  949-872-1052
>
> ------------------------------
> This message contains confidential information and is intended only for
> the individual named. If you are not the named addressee you should not
> disseminate, distribute or copy this e-mail. Please notify the sender
> immediately by e-mail if you have received this e-mail by mistake and
> delete this e-mail from your system. E-mail transmission cannot be
> guaranteed to be secure or error-free as information could be intercepted,
> corrupted, lost, destroyed, arrive late or incomplete, or contain viruses.
> The sender therefore does not accept liability for any errors or omissions
> in the contents of this message, which arise as a result of e-mail
> transmission.
>
>
> On Tue, Mar 19, 2013 at 7:32 AM, Sébastien Sablé <
> sable at users.sourceforge.net> wrote:
>
>> I am talking about the one mentioned in this email thread:
>> http://www.mail-archive.com/pyside at qt-project.org/msg00976.html
>>
>> It is close to what is in the wiki, but providing the actual full project
>> and the build steps really helps a lot.
>>
>> Your wiki page is a nice start to get the environment; at least it goes
>> into the right direction, great!
>>
>>
>> 2013/3/19 lndn <lndndev at gmail.com>
>>
>>> Are you talking about Roman's tutorial right here:
>>> http://qt-project.org/wiki/PySide_Shiboken_Tutorial
>>>
>>> If you have time to write the step-by-step tutorial, that would be
>>> phenomenal.  I also started doing something similar, but it's a getting
>>> started guide for new developers.  Check it out here:
>>> http://qt-project.org/wiki/PySide_Development_Getting_Started.  Just
>>> started yesterday, so its far from done.
>>>
>>> Thanks for helping out, we need more people to contribute!
>>>
>>>
>>>
>>>
>>> On Tue, Mar 19, 2013 at 4:11 AM, Sébastien Sablé <
>>> sable at users.sourceforge.net> wrote:
>>>
>>>> Hi,
>>>>
>>>> thanks for help!
>>>> If you have time, it would be nice to put online the tutorial that
>>>> Roman posted a few weeks ago.
>>>> That is what got me started binding my own library.
>>>>
>>>> I also did a bit of cleanup in the documentation a couple weeks ago
>>>> (fixing and moving to the right page the paths to git repositories, and
>>>> explaining that you need to go through gerrit to submit code for PySide).
>>>> If I can find some time, I will take a look at what you did and try to
>>>> help. I recently started to contribute to the project, so the limitations
>>>> of the doc are still fresh in my mind.
>>>> I would like to build a step by step tutorial on how to setup a linux
>>>> environment to checkout the git sources for pyside, build it, run the unit
>>>> tests, add some more tests, run a test in the debugger to fix it. This
>>>> could help to get more developers to contribute to the project rather than
>>>> just opening tickets.
>>>>
>>>> regards
>>>>
>>>> Sébastien
>>>>
>>>>
>>>>
>>>> 2013/3/19 lndn <lndndev at gmail.com>
>>>>
>>>>> Hi Roman,
>>>>> Thanks for the reply!
>>>>>
>>>>> The PyPI link is now on:
>>>>> http://qt-project.org/wiki/Get-PySide
>>>>>
>>>>> The prebuilt windows packages link is now on:
>>>>> http://qt-project.org/wiki/PySide_Binaries_Windows
>>>>>
>>>>>
>>>>> If later I see other pages that require these links, I'll update it at
>>>>> that time.
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Mar 19, 2013 at 12:14 AM, Roman Lacko <backup.rlacko at gmail.com
>>>>> > wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> 2013/3/19 lndn <lndndev at gmail.com>
>>>>>>
>>>>>>> I just spent the weekend organizing some of the pyside wiki pages (
>>>>>>> http://qt-project.org/wiki/PySide) and making small updates to the
>>>>>>> content here and there.
>>>>>>>
>>>>>>> Still needs a lot of work, but if someone can take a look and tell
>>>>>>> me what you think so far, I can start focusing on important areas.
>>>>>>>
>>>>>>> Thanks!
>>>>>>>
>>>>>>> Thanks for doing this!
>>>>>>
>>>>>> It would be great to put somewhere information about the PyPI page
>>>>>> [1].
>>>>>> It contains the installation instructions (for windows and linux) and
>>>>>> full source code of PySide, Shiboken, PySideTool, examples and build
>>>>>> scripts bundled in standard distutils package. Also here is the downloads
>>>>>> page for prebuild windows packages and source budles [2]. I should put the
>>>>>> information on wiki myself but never had time to do it.
>>>>>>
>>>>>> Thanks
>>>>>> R.
>>>>>>
>>>>>> [1] https://pypi.python.org/pypi/PySide
>>>>>> [2] http://releases.qt-project.org/pyside/
>>>>>>
>>>>>>
>>>>>>> On Sun, Mar 17, 2013 at 9:17 AM, Stephan Deibel <
>>>>>>> sdeibel at wingware.com> wrote:
>>>>>>>
>>>>>>>> lndn wrote:
>>>>>>>>
>>>>>>>>> All the recent scary "PySide is Dead" emails really prompted me to
>>>>>>>>> think about what we can do to improve the situation.  Not being familiar
>>>>>>>>> with the PySide/Shiboken internals, I thought it would be a good idea to
>>>>>>>>> start by cleaning up the wiki pages on qt-project.
>>>>>>>>>
>>>>>>>>> However, as I combed through these pages, I noticed that many of
>>>>>>>>> the links were broken and pointing to old pyside.org <
>>>>>>>>> http://pyside.org> pages that no longer exist and the content
>>>>>>>>> contains outdated and incomplete information.  What is really needed is a
>>>>>>>>> major overhaul in updating the content.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> So what's the official word on a massive re-organizing of these
>>>>>>>>> pages?  Can I just take the initiative and do it?  I'd like to start off by
>>>>>>>>> just putting the wiki pages in some order so things are easy to find and
>>>>>>>>> then later go through the content and update the content one page at a
>>>>>>>>> time.  My goal is just to help users and developers easily navigate to the
>>>>>>>>> pages they need.
>>>>>>>>>
>>>>>>>>> Any thoughts or people interested in helping would be great.
>>>>>>>>>
>>>>>>>>
>>>>>>>> This would be very helpful!
>>>>>>>>
>>>>>>>> I have in the past found some of the missing pages on archive.org.
>>>>>>>>  You can paste urls there in the WayBackMachine box and see dated archives
>>>>>>>> of the page.  It would be great to put back some of that lost content
>>>>>>>> (which I think was lost in the Nokia -> Digia transition).
>>>>>>>>
>>>>>>>> For outdated docs, it seems best to keep them somewhere (an archive
>>>>>>>> area?) or clearly label them, rather than removing them for now.  I suspect
>>>>>>>> some of these may be helpful to people trying to understand and move PySide
>>>>>>>> forward.
>>>>>>>>
>>>>>>>> Thanks for offering to do this!
>>>>>>>>
>>>>>>>> - Stephan
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> PySide mailing list
>>>>>>> PySide at qt-project.org
>>>>>>> http://lists.qt-project.org/mailman/listinfo/pyside
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> PySide mailing list
>>>>> PySide at qt-project.org
>>>>> http://lists.qt-project.org/mailman/listinfo/pyside
>>>>>
>>>>>
>>>>
>>>
>>
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130320/7849f6ab/attachment.html>

From heng at cantab.net  Wed Mar 20 16:48:19 2013
From: heng at cantab.net (Henry Gomersall)
Date: Wed, 20 Mar 2013 15:48:19 +0000
Subject: [PySide] Honkin Idea for PySide's thriving
In-Reply-To: <1363791841.13681.5.camel@farnsworth>
References: <1F30AF68-F941-4786-B8D3-B65F1E1ABC97@stackless.com>
	<1363791841.13681.5.camel@farnsworth>
Message-ID: <1363794499.13681.16.camel@farnsworth>

On Wed, 2013-03-20 at 15:04 +0000, Henry Gomersall wrote:
> Given Ubuntu's recent noises about Qt and QML, in particular with
> respect to Ubuntu Touch (http://en.wikipedia.org/wiki/Ubuntu_Touch),
> would perhaps a better target be to derive some support from that
> direction?
> 
> To quote from the Ubuntu developers resources
> (http://developer.ubuntu.com/resources/programming-languages/python/):
> 
> "Many important parts of Ubuntu are already written directly in
> Python,
> and we work to make every important API and framework within Ubuntu
> available from Python."

I emailed the Ubuntu Touch list to ask if there is a plan.

cheers,

Henry





From a.richi at bluewin.ch  Wed Mar 20 16:52:12 2013
From: a.richi at bluewin.ch (Aaron Richiger)
Date: Wed, 20 Mar 2013 16:52:12 +0100
Subject: [PySide] Honkin Idea for PySide's thriving
In-Reply-To: <5149CDC1.8080406@wingware.com>
References: <1F30AF68-F941-4786-B8D3-B65F1E1ABC97@stackless.com>
	<5149CDC1.8080406@wingware.com>
Message-ID: <5149DB2C.3090403@bluewin.ch>

Am 20.03.2013 15:54, schrieb Stephan Deibel:
> Christian Tismer wrote:
>> Make PySide the new standard Gui toolkit for Python!
> I'm also a bit concerned it would slow things down and might be hard
> given the copyright ownership.  It seems like an idea to keep in mind
> for the future, but there is much to do before I would attempt this.
>
> - Stephan
Great idea in theory, but I have to agree with the others, that I prefer 
PySide available via site-packages for the named reasons. But I'm very 
glad, that we are moving and that there seems to be already a little bit 
of effort towards PySide for Qt5 and bug fixing / code review 
improvements. We are still working a lot on PySide for Android and will 
provide you with more information as soon as we have taken the most 
important first steps!

Aaron
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside



From serpulga at gmail.com  Wed Mar 20 17:11:04 2013
From: serpulga at gmail.com (=?ISO-8859-1?Q?Sergio_Pulgar=EDn?=)
Date: Wed, 20 Mar 2013 11:11:04 -0500
Subject: [PySide] PySide Digest, Vol 14, Issue 18
In-Reply-To: <mailman.9700.1363794387.32284.pyside@qt-project.org>
References: <mailman.9700.1363794387.32284.pyside@qt-project.org>
Message-ID: <CAKiRVASUoV2fJXku3tnvARQbUfwnCoQuz31xU7oXe3RYk3APkw@mail.gmail.com>

Hi, I might be late to the discussion here, but I would like to
share my thoughts anyways.
It is no secret that PySide and PyQt4 are highly compatible
with each other; with a few modifications you can port back
and forth easly, and even create cross-compatible sources.
So basically, at a end user level, there are no (or a few) arguments
to chose one or the other. The real advantage the PySide has over
PyQt4 are the licensing options. PySide has the LGPL option, while
PyQt4 only GPL, last time I checked. I think this alone, makes people
want to use/port to PySide.
Another potential advantage is PySide's visibility through the Qt-Project,
which I don't think it's exploited at its potential.

About being included in the Python standard library, I agree that it's not
a viable option, however, I don't think that PySide needs to be in the
standard,
in order for it to be the defacto GUI toolkit for Python, it needs to
install easily across OSs and distros, be well documented, be active
as a project, have a newbie friendly community, etc.

Finally, I would like to mention GitHub. GitHub currently has a huge
momentum, and PySide can take advantage of that, to gain activeness and
user contribution.



Sergio
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130320/032a8f69/attachment.html>

From toddrme2178 at gmail.com  Wed Mar 20 17:35:04 2013
From: toddrme2178 at gmail.com (todd rme)
Date: Wed, 20 Mar 2013 17:35:04 +0100
Subject: [PySide] PySide Digest, Vol 14, Issue 18
In-Reply-To: <CAKiRVASUoV2fJXku3tnvARQbUfwnCoQuz31xU7oXe3RYk3APkw@mail.gmail.com>
References: <mailman.9700.1363794387.32284.pyside@qt-project.org>
	<CAKiRVASUoV2fJXku3tnvARQbUfwnCoQuz31xU7oXe3RYk3APkw@mail.gmail.com>
Message-ID: <CADb7s=uG7hywRN5LyWoTqC6nHGD-eLgnidJO=KFWhdYd2yH9TQ@mail.gmail.com>

On Wed, Mar 20, 2013 at 5:11 PM, Sergio Pulgarín <serpulga at gmail.com> wrote:
>
> Hi, I might be late to the discussion here, but I would like to
> share my thoughts anyways.
> It is no secret that PySide and PyQt4 are highly compatible
> with each other; with a few modifications you can port back
> and forth easly, and even create cross-compatible sources.
> So basically, at a end user level, there are no (or a few) arguments
> to chose one or the other. The real advantage the PySide has over
> PyQt4 are the licensing options. PySide has the LGPL option, while
> PyQt4 only GPL, last time I checked. I think this alone, makes people
> want to use/port to PySide.

That only helps if you are writing a closed-source application.
Anyone who want to create an open-source end-user application is not
going to care.  They are going to base it on things like features,
support, how active the community is, what is being used by other
projects, and what middle-level python modules they want to use
support.  For these people, PyQt4 is currently the better choice on
all fronts.  And these people are exactly the ones who are most likely
to want to get involved in and contribute back to pyside if they use
it.

If pyside is going to succeed, it will have to do so based on
something other than license alone.  Community, support, and what is
being used by other projects is a chicken-and-egg problem, pyside will
not have these until it gains some momentum.  And it will be hard to
get middle-level toolkits to work with pyside exclusively precisely
because it is not much harder than supporting both pyqt4 and pyside at
the same time, and without much user interest there is no reason to
support pyside at all.

So if pyside is going to get ahead it I think it needs to have some
sort of compelling features that are lacked by PyQt4.  I think that is
the only way open-source projects are going to use it.


From sdeibel at wingware.com  Wed Mar 20 18:17:01 2013
From: sdeibel at wingware.com (Stephan Deibel)
Date: Wed, 20 Mar 2013 13:17:01 -0400
Subject: [PySide] Summary of PySide BoF at PyCon
Message-ID: <5149EF0D.9060107@wingware.com>

Hi,

Here is a summary of the PySide BoF that was held on Saturday March 
16that PyCon 2013 in Santa Clara, CA.  We found there is a lot of 
interest at companies that chose PySide for its licensing.  Several 
companies that were present started a collaboration in order to move 
towards a work plan and coordinated funding and further development of 
PySide.  If you are interested in joining this effort, please contact me.

Introductions
-------------

The purpose of this BoF was to gather together users invested in PySide, 
review the status of PySide, and move towards revitalizing the project.  
Twelve individuals attended, including representatives of Wingware, 
Enthought, Valve, Disney, and several other companies.

The meeting started with each individual introducing themselves and 
describing their use of PySide and any concerns that they have.  
Licensing issues were the reason most of the users present (representing 
at least 5 companies) chose PySide over PyQt.  All of those citing 
licensing as a problem have a scripting API for their users, which 
requires royalties to be paid on revenues if PyQt is used.

Experiences with stability of PySide varied.  Though most had run into 
some issues, some were able to work around them while most others felt 
that fixes are needed for significant bugs.  Several present indicated a 
concern for the overall future of PySide, particularly in the context of 
supporting Qt5, making PySide more maintainable, and reestablishing a 
team of reviewers and committers.

Several attendees expressed gratitude to the previous developers of 
PySide, especially Hugo for remaining involved as approver/committer.

Discussion of Issues
--------------------

A discussion of the major issues to be solved followed.  Issues brought 
up included stability, Qt5 support, lack of reviewers and committers, 
problems with the current review process, need for doing a release from 
latest revision, and need to process the accumulated list of bug reports 
that have not received any action.

It was noted that Digia is not returning calls or emails concerning 
PySide.  The possibility of forking PySide and moving it out of the Qt 
Project development toolset was brought up but consensus was established 
that this was not desirable if it could be avoided.  If a fork is 
considered later, legal consul would be asked about trademark, licensing 
considerations, and the potential for re-merging changes into the Qt 
Project at a later date.

Some specific bugs were discussed, including causes of life cycle 
issues, and whether bugs are fixable without rewriting parts of PySide.

Plan of Action
--------------

Several attending stated that it may be possible for their companies to 
providing funds or staff, given an acceptable development plan and 
process.  This will be investigated further by each potential 
contributor, and some additional companies were identified and will be 
approached.

Representatives of Enthought stated that they could host a week-long 
meeting aimed at creating a work plan and kick-starting work on PySide.

[The one-hour time available in the open space slot ended here and a 
subset of the attendees adjourned to a nearby bar :-]

Several attendees offered to act as future reviewers and committers for 
PySide:  John Ehresman (contributor to PyGTK) from Wingware, Christian 
Tismer (author of Stackless Python), along with Enthought staff:  Robin 
Dunn (author of wxPython), Jason McCampbell, and Robert Kern.

Discussion followed concerning development approaches.  Those present 
agreed that rewriting PySide from scratch is a large task and would lose 
the special cases already worked through and dealt with by PySide.  The 
possibility of a partial rewrite in Python was raised.  Another 
possibility raised was to convert the XML encoding of special cases into 
some more readable and maintainable form, similar to the one used in 
PyGTK and PyScintilla2.  Expanded developer documentation is also needed.

A discussion of the amount and cost of work involved followed.  
Estimates ranged from about 1 to 4 FTE years to cover bug fixes, Qt5 
support, and sheparding the project towards a sustainable future.

Action Items
------------

The meeting attendees will work together to arrange a week in the next 
few months, to be held at Enthought in Austin TX, in order to develop a 
work plan to serve as the foundation for collaboration among interested 
companies.  Possible attendees include John Ehresman, Robin Dunn, 
Christian Tismer and any others interested and able to attend.

Several individuals will further investigate the possibility of their 
companies contributing development funds and/or effort.

Enthought will look into any legal issues that need to be addressed.

Several attendees will try to contact other companies identified at the 
meeting, that might be able to participate in drafting and 
implementation of a work plan.  This could include using the recent 
PySide survey on this mailing list to find potential contributors.

A PySide sprint will be held at SciPy 2013 in June.



From thoromyr at mac.com  Wed Mar 20 20:30:30 2013
From: thoromyr at mac.com (Tim Doty)
Date: Wed, 20 Mar 2013 14:30:30 -0500
Subject: [PySide] PySide Digest, Vol 14, Issue 18
In-Reply-To: <CADb7s=uG7hywRN5LyWoTqC6nHGD-eLgnidJO=KFWhdYd2yH9TQ@mail.gmail.com>
References: <mailman.9700.1363794387.32284.pyside@qt-project.org>
	<CAKiRVASUoV2fJXku3tnvARQbUfwnCoQuz31xU7oXe3RYk3APkw@mail.gmail.com>
	<CADb7s=uG7hywRN5LyWoTqC6nHGD-eLgnidJO=KFWhdYd2yH9TQ@mail.gmail.com>
Message-ID: <305F0703-E4A0-49BE-B18D-D3C566CDABED@mac.com>

For what its worth, the reason I switched from PyQt to PySide was not the license. At the time it looked like it was being supported (Nokia) and was finally stable. The push for me was that PyQt isn't really very friendly -- if someone wants to use your app they have to get PyQt installed -- and the site is geared toward developers, not end users.

I had no end of arguments from people insisting they couldn't use the app because they couldn't get SIP installed and besides which they didn't have a compiler. And as if that wasn't enough PyQt isn't particularly easy to get setup on OS X. It only works well on linux, or Windows if you create a self-contained installer.

Although in principle PyQt is cross platform, my experience is that it is cross platform only if your platform is linux or you create an installer for Windows. PySide has been easier in that regard, though it has had some snafus. I still prefer it because I want to remain platform agnostic. I used to be solely linux myself, but I've been using OS X more and more. And most people who would use anything I write are on some flavor of windows.

From that perspective having an easy way to bundle needed components is a must. Admittedly, if the applications are in-house or focused on linux this is less of an issue but for broad use it really is a must. End users need simple.

Tim Doty

On Mar 20, 2013, at 11:35 AM, todd rme <toddrme2178 at gmail.com> wrote:

> On Wed, Mar 20, 2013 at 5:11 PM, Sergio Pulgarín <serpulga at gmail.com> wrote:
>> 
>> Hi, I might be late to the discussion here, but I would like to
>> share my thoughts anyways.
>> It is no secret that PySide and PyQt4 are highly compatible
>> with each other; with a few modifications you can port back
>> and forth easly, and even create cross-compatible sources.
>> So basically, at a end user level, there are no (or a few) arguments
>> to chose one or the other. The real advantage the PySide has over
>> PyQt4 are the licensing options. PySide has the LGPL option, while
>> PyQt4 only GPL, last time I checked. I think this alone, makes people
>> want to use/port to PySide.
> 
> That only helps if you are writing a closed-source application.
> Anyone who want to create an open-source end-user application is not
> going to care.  They are going to base it on things like features,
> support, how active the community is, what is being used by other
> projects, and what middle-level python modules they want to use
> support.  For these people, PyQt4 is currently the better choice on
> all fronts.  And these people are exactly the ones who are most likely
> to want to get involved in and contribute back to pyside if they use
> it.
> 
> If pyside is going to succeed, it will have to do so based on
> something other than license alone.  Community, support, and what is
> being used by other projects is a chicken-and-egg problem, pyside will
> not have these until it gains some momentum.  And it will be hard to
> get middle-level toolkits to work with pyside exclusively precisely
> because it is not much harder than supporting both pyqt4 and pyside at
> the same time, and without much user interest there is no reason to
> support pyside at all.
> 
> So if pyside is going to get ahead it I think it needs to have some
> sort of compelling features that are lacked by PyQt4.  I think that is
> the only way open-source projects are going to use it.
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside



From tismer at stackless.com  Thu Mar 21 03:09:14 2013
From: tismer at stackless.com (Christian Tismer)
Date: Wed, 20 Mar 2013 19:09:14 -0700
Subject: [PySide] Honkin Idea for PySide's thriving
In-Reply-To: <5149DB2C.3090403@bluewin.ch>
References: <1F30AF68-F941-4786-B8D3-B65F1E1ABC97@stackless.com>
	<5149CDC1.8080406@wingware.com> <5149DB2C.3090403@bluewin.ch>
Message-ID: <514A6BCA.2010308@stackless.com>

On 3/20/13 8:52 AM, Aaron Richiger wrote:
> Am 20.03.2013 15:54, schrieb Stephan Deibel:
>> Christian Tismer wrote:
>>> Make PySide the new standard Gui toolkit for Python!
>> I'm also a bit concerned it would slow things down and might be hard
>> given the copyright ownership.  It seems like an idea to keep in mind
>> for the future, but there is much to do before I would attempt this.
>>
>> - Stephan
> Great idea in theory, but I have to agree with the others, that I prefer
> PySide available via site-packages for the named reasons. But I'm very
> glad, that we are moving and that there seems to be already a little bit
> of effort towards PySide for Qt5 and bug fixing / code review
> improvements. We are still working a lot on PySide for Android and will
> provide you with more information as soon as we have taken the most
> important first steps!

Well, thanks for all the input!

I'm essentially also in favor to have PySide in site-packages.
My enthusiastic mail was more expressing what I like to see
PySide perceived as, without necessarily having it as a super-large
battery. (As a side, the Python Batteries have actually grown too large
already and we need way to strip that down...).

So what I want is to make PySide a very supported, very well acknowledged
package that gets its #1 recommendation from Python, something like that.
I don't want to slow down the development and avoid licensing issues.

But getting many people interested in working on PySide could be a
benefit if it would get its place in Python.org.

Maybe we can move the mailing list there, and or have some announcement
on python-announce that we want to improve PySide and spread the word?

cheers - chris

-- 
Christian Tismer             :^)   <mailto:tismer at stackless.com>
Software Consulting          :     Have a break! Take a ride on Python's
Karl-Liebknecht-Str. 121     :    *Starship* http://starship.python.net/
14482 Potsdam                :     PGP key -> http://pgp.uni-mainz.de
phone +49 173 24 18 776  fax +49 (30) 700143-0023
PGP 0x57F3BF04       9064 F4E1 D754 C2FF 1619  305B C09C 5A3B 57F3 BF04
       whom do you want to sponsor today?   http://www.stackless.com/



From serpulga at gmail.com  Thu Mar 21 03:31:45 2013
From: serpulga at gmail.com (=?ISO-8859-1?Q?Sergio_Pulgar=EDn?=)
Date: Wed, 20 Mar 2013 21:31:45 -0500
Subject: [PySide] PySide Digest, Vol 14, Issue 19
In-Reply-To: <mailman.9738.1363831765.32284.pyside@qt-project.org>
References: <mailman.9738.1363831765.32284.pyside@qt-project.org>
Message-ID: <CAKiRVASub8NLeacae6VLwMoJEWbHzX8CD8bysOJ6eJsk+neg8Q@mail.gmail.com>

> Message: 1
> Date: Wed, 20 Mar 2013 15:48:19 +0000
> From: Henry Gomersall <heng at cantab.net>
> Subject: Re: [PySide] Honkin Idea for PySide's thriving
> To: Christian Tismer <tismer at stackless.com>
> Cc: pyside at qt-project.org, "Samual M. Rushing" <rushing at ironport.com>
> Message-ID: <1363794499.13681.16.camel at farnsworth>
> Content-Type: text/plain; charset="UTF-8"
>
> On Wed, 2013-03-20 at 15:04 +0000, Henry Gomersall wrote:
> > Given Ubuntu's recent noises about Qt and QML, in particular with
> > respect to Ubuntu Touch (http://en.wikipedia.org/wiki/Ubuntu_Touch),
> > would perhaps a better target be to derive some support from that
> > direction?
> >
> > To quote from the Ubuntu developers resources
> > (http://developer.ubuntu.com/resources/programming-languages/python/):
> >
> > "Many important parts of Ubuntu are already written directly in
> > Python,
> > and we work to make every important API and framework within Ubuntu
> > available from Python."
>
> I emailed the Ubuntu Touch list to ask if there is a plan.
>
> cheers,
>
> Henry
>
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 20 Mar 2013 16:52:12 +0100
> From: Aaron Richiger <a.richi at bluewin.ch>
> Subject: Re: [PySide] Honkin Idea for PySide's thriving
> To: pyside at qt-project.org
> Message-ID: <5149DB2C.3090403 at bluewin.ch>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Am 20.03.2013 15:54, schrieb Stephan Deibel:
> > Christian Tismer wrote:
> >> Make PySide the new standard Gui toolkit for Python!
> > I'm also a bit concerned it would slow things down and might be hard
> > given the copyright ownership.  It seems like an idea to keep in mind
> > for the future, but there is much to do before I would attempt this.
> >
> > - Stephan
> Great idea in theory, but I have to agree with the others, that I prefer
> PySide available via site-packages for the named reasons. But I'm very
> glad, that we are moving and that there seems to be already a little bit
> of effort towards PySide for Qt5 and bug fixing / code review
> improvements. We are still working a lot on PySide for Android and will
> provide you with more information as soon as we have taken the most
> important first steps!
>
> Aaron
> >
> > _______________________________________________
> > PySide mailing list
> > PySide at qt-project.org
> > http://lists.qt-project.org/mailman/listinfo/pyside
>
>
>
> ------------------------------
>
> Message: 3
> Date: Wed, 20 Mar 2013 11:11:04 -0500
> From: Sergio Pulgar?n <serpulga at gmail.com>
> Subject: Re: [PySide] PySide Digest, Vol 14, Issue 18
> To: pyside at qt-project.org
> Message-ID:
>         <
> CAKiRVASUoV2fJXku3tnvARQbUfwnCoQuz31xU7oXe3RYk3APkw at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi, I might be late to the discussion here, but I would like to
> share my thoughts anyways.
> It is no secret that PySide and PyQt4 are highly compatible
> with each other; with a few modifications you can port back
> and forth easly, and even create cross-compatible sources.
> So basically, at a end user level, there are no (or a few) arguments
> to chose one or the other. The real advantage the PySide has over
> PyQt4 are the licensing options. PySide has the LGPL option, while
> PyQt4 only GPL, last time I checked. I think this alone, makes people
> want to use/port to PySide.
> Another potential advantage is PySide's visibility through the Qt-Project,
> which I don't think it's exploited at its potential.
>
> About being included in the Python standard library, I agree that it's not
> a viable option, however, I don't think that PySide needs to be in the
> standard,
> in order for it to be the defacto GUI toolkit for Python, it needs to
> install easily across OSs and distros, be well documented, be active
> as a project, have a newbie friendly community, etc.
>
> Finally, I would like to mention GitHub. GitHub currently has a huge
> momentum, and PySide can take advantage of that, to gain activeness and
> user contribution.
>
>
>
> Sergio
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://lists.qt-project.org/pipermail/pyside/attachments/20130320/032a8f69/attachment-0001.html
>
> ------------------------------
>
> Message: 4
> Date: Wed, 20 Mar 2013 17:35:04 +0100
> From: todd rme <toddrme2178 at gmail.com>
> Subject: Re: [PySide] PySide Digest, Vol 14, Issue 18
> To: pyside at qt-project.org
> Message-ID:
>         <CADb7s=uG7hywRN5LyWoTqC6nHGD-eLgnidJO=
> KFWhdYd2yH9TQ at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Wed, Mar 20, 2013 at 5:11 PM, Sergio Pulgar?n <serpulga at gmail.com>
> wrote:
> >
> > Hi, I might be late to the discussion here, but I would like to
> > share my thoughts anyways.
> > It is no secret that PySide and PyQt4 are highly compatible
> > with each other; with a few modifications you can port back
> > and forth easly, and even create cross-compatible sources.
> > So basically, at a end user level, there are no (or a few) arguments
> > to chose one or the other. The real advantage the PySide has over
> > PyQt4 are the licensing options. PySide has the LGPL option, while
> > PyQt4 only GPL, last time I checked. I think this alone, makes people
> > want to use/port to PySide.
>
> That only helps if you are writing a closed-source application.
> Anyone who want to create an open-source end-user application is not
> going to care.  They are going to base it on things like features,
> support, how active the community is, what is being used by other
> projects, and what middle-level python modules they want to use
> support.  For these people, PyQt4 is currently the better choice on
> all fronts.  And these people are exactly the ones who are most likely
> to want to get involved in and contribute back to pyside if they use
> it.
>
> If pyside is going to succeed, it will have to do so based on
> something other than license alone.  Community, support, and what is
> being used by other projects is a chicken-and-egg problem, pyside will
> not have these until it gains some momentum.  And it will be hard to
> get middle-level toolkits to work with pyside exclusively precisely
> because it is not much harder than supporting both pyqt4 and pyside at
> the same time, and without much user interest there is no reason to
> support pyside at all.
>
> So if pyside is going to get ahead it I think it needs to have some
> sort of compelling features that are lacked by PyQt4.  I think that is
> the only way open-source projects are going to use it.
>

> ------------------------------
>
> Message: 5
> Date: Wed, 20 Mar 2013 13:17:01 -0400
> From: Stephan Deibel <sdeibel at wingware.com>
> Subject: [PySide] Summary of PySide BoF at PyCon
> To: "pyside at qt-project.org" <pyside at qt-project.org>
> Message-ID: <5149EF0D.9060107 at wingware.com>
> Content-Type: text/plain; charset=UTF-8; format=flowed
>
> Hi,
>
> Here is a summary of the PySide BoF that was held on Saturday March
> 16that PyCon 2013 in Santa Clara, CA.  We found there is a lot of
> interest at companies that chose PySide for its licensing.  Several
> companies that were present started a collaboration in order to move
> towards a work plan and coordinated funding and further development of
> PySide.  If you are interested in joining this effort, please contact me.
>
> Introductions
> -------------
>
> The purpose of this BoF was to gather together users invested in PySide,
> review the status of PySide, and move towards revitalizing the project.
> Twelve individuals attended, including representatives of Wingware,
> Enthought, Valve, Disney, and several other companies.
>
> The meeting started with each individual introducing themselves and
> describing their use of PySide and any concerns that they have.
> Licensing issues were the reason most of the users present (representing
> at least 5 companies) chose PySide over PyQt.  All of those citing
> licensing as a problem have a scripting API for their users, which
> requires royalties to be paid on revenues if PyQt is used.
>
> Experiences with stability of PySide varied.  Though most had run into
> some issues, some were able to work around them while most others felt
> that fixes are needed for significant bugs.  Several present indicated a
> concern for the overall future of PySide, particularly in the context of
> supporting Qt5, making PySide more maintainable, and reestablishing a
> team of reviewers and committers.
>
> Several attendees expressed gratitude to the previous developers of
> PySide, especially Hugo for remaining involved as approver/committer.
>
> Discussion of Issues
> --------------------
>
> A discussion of the major issues to be solved followed.  Issues brought
> up included stability, Qt5 support, lack of reviewers and committers,
> problems with the current review process, need for doing a release from
> latest revision, and need to process the accumulated list of bug reports
> that have not received any action.
>
> It was noted that Digia is not returning calls or emails concerning
> PySide.  The possibility of forking PySide and moving it out of the Qt
> Project development toolset was brought up but consensus was established
> that this was not desirable if it could be avoided.  If a fork is
> considered later, legal consul would be asked about trademark, licensing
> considerations, and the potential for re-merging changes into the Qt
> Project at a later date.
>
> Some specific bugs were discussed, including causes of life cycle
> issues, and whether bugs are fixable without rewriting parts of PySide.
>
> Plan of Action
> --------------
>
> Several attending stated that it may be possible for their companies to
> providing funds or staff, given an acceptable development plan and
> process.  This will be investigated further by each potential
> contributor, and some additional companies were identified and will be
> approached.
>
> Representatives of Enthought stated that they could host a week-long
> meeting aimed at creating a work plan and kick-starting work on PySide.
>
> [The one-hour time available in the open space slot ended here and a
> subset of the attendees adjourned to a nearby bar :-]
>
> Several attendees offered to act as future reviewers and committers for
> PySide:  John Ehresman (contributor to PyGTK) from Wingware, Christian
> Tismer (author of Stackless Python), along with Enthought staff:  Robin
> Dunn (author of wxPython), Jason McCampbell, and Robert Kern.
>
> Discussion followed concerning development approaches.  Those present
> agreed that rewriting PySide from scratch is a large task and would lose
> the special cases already worked through and dealt with by PySide.  The
> possibility of a partial rewrite in Python was raised.  Another
> possibility raised was to convert the XML encoding of special cases into
> some more readable and maintainable form, similar to the one used in
> PyGTK and PyScintilla2.  Expanded developer documentation is also needed.
>
> A discussion of the amount and cost of work involved followed.
> Estimates ranged from about 1 to 4 FTE years to cover bug fixes, Qt5
> support, and sheparding the project towards a sustainable future.
>
> Action Items
> ------------
>
> The meeting attendees will work together to arrange a week in the next
> few months, to be held at Enthought in Austin TX, in order to develop a
> work plan to serve as the foundation for collaboration among interested
> companies.  Possible attendees include John Ehresman, Robin Dunn,
> Christian Tismer and any others interested and able to attend.
>
> Several individuals will further investigate the possibility of their
> companies contributing development funds and/or effort.
>
> Enthought will look into any legal issues that need to be addressed.
>
> Several attendees will try to contact other companies identified at the
> meeting, that might be able to participate in drafting and
> implementation of a work plan.  This could include using the recent
> PySide survey on this mailing list to find potential contributors.
>
> A PySide sprint will be held at SciPy 2013 in June.
>
>
>
This is very good news, it sounds very promising to me.
I still see branching off as an option, if it would help move
things more quickly. If Digia is indeed looking the other way regarding
PySide, maybe they will everything easy, legal aspects, keeping
the brand, etc.







>
> ------------------------------
>
> Message: 6
> Date: Wed, 20 Mar 2013 14:30:30 -0500
> From: Tim Doty <thoromyr at mac.com>
> Subject: Re: [PySide] PySide Digest, Vol 14, Issue 18
> To: todd rme <toddrme2178 at gmail.com>
> Cc: pyside at qt-project.org
> Message-ID: <305F0703-E4A0-49BE-B18D-D3C566CDABED at mac.com>
> Content-Type: text/plain; charset=iso-8859-1
>
> For what its worth, the reason I switched from PyQt to PySide was not the
> license. At the time it looked like it was being supported (Nokia) and was
> finally stable. The push for me was that PyQt isn't really very friendly --
> if someone wants to use your app they have to get PyQt installed -- and the
> site is geared toward developers, not end users.
>
> I had no end of arguments from people insisting they couldn't use the app
> because they couldn't get SIP installed and besides which they didn't have
> a compiler. And as if that wasn't enough PyQt isn't particularly easy to
> get setup on OS X. It only works well on linux, or Windows if you create a
> self-contained installer.
>
> Although in principle PyQt is cross platform, my experience is that it is
> cross platform only if your platform is linux or you create an installer
> for Windows. PySide has been easier in that regard, though it has had some
> snafus. I still prefer it because I want to remain platform agnostic. I
> used to be solely linux myself, but I've been using OS X more and more. And
> most people who would use anything I write are on some flavor of windows.
>
> >From that perspective having an easy way to bundle needed components is a
> must. Admittedly, if the applications are in-house or focused on linux this
> is less of an issue but for broad use it really is a must. End users need
> simple.
>
> Tim Doty
>
> On Mar 20, 2013, at 11:35 AM, todd rme <toddrme2178 at gmail.com> wrote:
>
> > On Wed, Mar 20, 2013 at 5:11 PM, Sergio Pulgar?n <serpulga at gmail.com>
> wrote:
> >>
> >> Hi, I might be late to the discussion here, but I would like to
> >> share my thoughts anyways.
> >> It is no secret that PySide and PyQt4 are highly compatible
> >> with each other; with a few modifications you can port back
> >> and forth easly, and even create cross-compatible sources.
> >> So basically, at a end user level, there are no (or a few) arguments
> >> to chose one or the other. The real advantage the PySide has over
> >> PyQt4 are the licensing options. PySide has the LGPL option, while
> >> PyQt4 only GPL, last time I checked. I think this alone, makes people
> >> want to use/port to PySide.
> >
> > That only helps if you are writing a closed-source application.
> > Anyone who want to create an open-source end-user application is not
> > going to care.  They are going to base it on things like features,
> > support, how active the community is, what is being used by other
> > projects, and what middle-level python modules they want to use
> > support.  For these people, PyQt4 is currently the better choice on
> > all fronts.  And these people are exactly the ones who are most likely
> > to want to get involved in and contribute back to pyside if they use
> > it.
> >
> > If pyside is going to succeed, it will have to do so based on
> > something other than license alone.  Community, support, and what is
> > being used by other projects is a chicken-and-egg problem, pyside will
> > not have these until it gains some momentum.  And it will be hard to
> > get middle-level toolkits to work with pyside exclusively precisely
> > because it is not much harder than supporting both pyqt4 and pyside at
> > the same time, and without much user interest there is no reason to
> > support pyside at all.
> >
> > So if pyside is going to get ahead it I think it needs to have some
> > sort of compelling features that are lacked by PyQt4.  I think that is
> > the only way open-source projects are going to use it.
> > _______________________________________________
> > PySide mailing list
> > PySide at qt-project.org
> > http://lists.qt-project.org/mailman/listinfo/pyside
>
>
>
> ------------------------------
>
> Message: 7
> Date: Wed, 20 Mar 2013 19:09:14 -0700
> From: Christian Tismer <tismer at stackless.com>
> Subject: Re: [PySide] Honkin Idea for PySide's thriving
> To: Aaron Richiger <a.richi at bluewin.ch>
> Cc: pyside at qt-project.org
> Message-ID: <514A6BCA.2010308 at stackless.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> On 3/20/13 8:52 AM, Aaron Richiger wrote:
> > Am 20.03.2013 15:54, schrieb Stephan Deibel:
> >> Christian Tismer wrote:
> >>> Make PySide the new standard Gui toolkit for Python!
> >> I'm also a bit concerned it would slow things down and might be hard
> >> given the copyright ownership.  It seems like an idea to keep in mind
> >> for the future, but there is much to do before I would attempt this.
> >>
> >> - Stephan
> > Great idea in theory, but I have to agree with the others, that I prefer
> > PySide available via site-packages for the named reasons. But I'm very
> > glad, that we are moving and that there seems to be already a little bit
> > of effort towards PySide for Qt5 and bug fixing / code review
> > improvements. We are still working a lot on PySide for Android and will
> > provide you with more information as soon as we have taken the most
> > important first steps!
>
> Well, thanks for all the input!
>
> I'm essentially also in favor to have PySide in site-packages.
> My enthusiastic mail was more expressing what I like to see
> PySide perceived as, without necessarily having it as a super-large
> battery. (As a side, the Python Batteries have actually grown too large
> already and we need way to strip that down...).
>
> So what I want is to make PySide a very supported, very well acknowledged
> package that gets its #1 recommendation from Python, something like that.
> I don't want to slow down the development and avoid licensing issues.
>
> But getting many people interested in working on PySide could be a
> benefit if it would get its place in Python.org.
>
> Maybe we can move the mailing list there, and or have some announcement
> on python-announce that we want to improve PySide and spread the word?
>
> cheers - chris
>
> --
> Christian Tismer             :^)   <mailto:tismer at stackless.com>
> Software Consulting          :     Have a break! Take a ride on Python's
> Karl-Liebknecht-Str. 121     :    *Starship* http://starship.python.net/
> 14482 Potsdam                :     PGP key -> http://pgp.uni-mainz.de
> phone +49 173 24 18 776  fax +49 (30) 700143-0023
> PGP 0x57F3BF04       9064 F4E1 D754 C2FF 1619  305B C09C 5A3B 57F3 BF04
>        whom do you want to sponsor today?   http://www.stackless.com/
>
>
>
> ------------------------------
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>
>
> End of PySide Digest, Vol 14, Issue 19
> **************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130320/30120a48/attachment.html>

From david.trem at gmail.com  Thu Mar 21 06:33:46 2013
From: david.trem at gmail.com (=?ISO-8859-1?Q?Tr=E9mouilles_David?=)
Date: Thu, 21 Mar 2013 06:33:46 +0100
Subject: [PySide] Honkin Idea for PySide's thriving
In-Reply-To: <514A6BCA.2010308@stackless.com>
References: <1F30AF68-F941-4786-B8D3-B65F1E1ABC97@stackless.com>
	<5149CDC1.8080406@wingware.com> <5149DB2C.3090403@bluewin.ch>
	<514A6BCA.2010308@stackless.com>
Message-ID: <514A9BBA.5090501@gmail.com>

Hi,

"Make PySide the *next* Gui toolkit for Python !"
is a Great goal.

Even if including PySide in python, is not the
best thing to do now, the issues related to its
possible inclusion should be consider as soon as
possible. Especially this one raised by Matti Airas:
"However, I believe they would require a license change from LGPL to 
PSL. I think this would be doable for the individual contributors, but a 
bigger question mark would be the Nokia-copyrighted contributions. I'm 
not sure whether they were sold to Digia when they bought Qt. If so, 
we'd need to convince Digia to let go of their commercial prospects 
towards PySide. They haven't shown much practical interest so far, so I 
don't know whether it would be feasible or not. However, if the 
copyright is still owned by Nokia, it might get hairy - you'd need to 
find a person within the current, heavily pruned organization and 
negotiate the licence change. It could still be doable, but not 
necessarily straightforward."


David


Le 21/03/13 03:09, Christian Tismer a écrit :
> On 3/20/13 8:52 AM, Aaron Richiger wrote:
>> Am 20.03.2013 15:54, schrieb Stephan Deibel:
>>> Christian Tismer wrote:
>>>> Make PySide the new standard Gui toolkit for Python!
>>> I'm also a bit concerned it would slow things down and might be hard
>>> given the copyright ownership.  It seems like an idea to keep in mind
>>> for the future, but there is much to do before I would attempt this.
>>>
>>> - Stephan
>> Great idea in theory, but I have to agree with the others, that I prefer
>> PySide available via site-packages for the named reasons. But I'm very
>> glad, that we are moving and that there seems to be already a little bit
>> of effort towards PySide for Qt5 and bug fixing / code review
>> improvements. We are still working a lot on PySide for Android and will
>> provide you with more information as soon as we have taken the most
>> important first steps!
> Well, thanks for all the input!
>
> I'm essentially also in favor to have PySide in site-packages.
> My enthusiastic mail was more expressing what I like to see
> PySide perceived as, without necessarily having it as a super-large
> battery. (As a side, the Python Batteries have actually grown too large
> already and we need way to strip that down...).
>
> So what I want is to make PySide a very supported, very well acknowledged
> package that gets its #1 recommendation from Python, something like that.
> I don't want to slow down the development and avoid licensing issues.
>
> But getting many people interested in working on PySide could be a
> benefit if it would get its place in Python.org.
>
> Maybe we can move the mailing list there, and or have some announcement
> on python-announce that we want to improve PySide and spread the word?
>
> cheers - chris
>



From heng at cantab.net  Thu Mar 21 07:37:13 2013
From: heng at cantab.net (Henry Gomersall)
Date: Thu, 21 Mar 2013 06:37:13 +0000
Subject: [PySide] Honkin Idea for PySide's thriving
In-Reply-To: <1363794499.13681.16.camel@farnsworth>
References: <1F30AF68-F941-4786-B8D3-B65F1E1ABC97@stackless.com>
	<1363791841.13681.5.camel@farnsworth>
	<1363794499.13681.16.camel@farnsworth>
Message-ID: <1363847833.3476.0.camel@farnsworth>

On Wed, 2013-03-20 at 15:48 +0000, Henry Gomersall wrote:
> On Wed, 2013-03-20 at 15:04 +0000, Henry Gomersall wrote:
> > Given Ubuntu's recent noises about Qt and QML, in particular with
> > respect to Ubuntu Touch (http://en.wikipedia.org/wiki/Ubuntu_Touch),
> > would perhaps a better target be to derive some support from that
> > direction?
> > 
> > To quote from the Ubuntu developers resources
> >
> (http://developer.ubuntu.com/resources/programming-languages/python/):
> > 
> > "Many important parts of Ubuntu are already written directly in
> > Python,
> > and we work to make every important API and framework within Ubuntu
> > available from Python."
> 
> I emailed the Ubuntu Touch list to ask if there is a plan.

See the debate here:

https://lists.launchpad.net/ubuntu-phone/msg01235.html

Henry



From khertan at khertan.net  Thu Mar 21 11:05:05 2013
From: khertan at khertan.net (=?ISO-8859-1?Q?Beno=EEt_HERVIER?=)
Date: Thu, 21 Mar 2013 11:05:05 +0100
Subject: [PySide] Honkin Idea for PySide's thriving
In-Reply-To: <1363847833.3476.0.camel@farnsworth>
References: <1F30AF68-F941-4786-B8D3-B65F1E1ABC97@stackless.com>
	<1363791841.13681.5.camel@farnsworth>
	<1363794499.13681.16.camel@farnsworth>
	<1363847833.3476.0.camel@farnsworth>
Message-ID: <514ADB51.7010109@khertan.net>

On 21/03/2013 07:37, Henry Gomersall wrote:
> On Wed, 2013-03-20 at 15:48 +0000, Henry Gomersall wrote:
>> On Wed, 2013-03-20 at 15:04 +0000, Henry Gomersall wrote:
>>> Given Ubuntu's recent noises about Qt and QML, in particular with
>>> respect to Ubuntu Touch (http://en.wikipedia.org/wiki/Ubuntu_Touch),
>>> would perhaps a better target be to derive some support from that
>>> direction?
>>>
>>> To quote from the Ubuntu developers resources
>>>
>> (http://developer.ubuntu.com/resources/programming-languages/python/):
>>> "Many important parts of Ubuntu are already written directly in
>>> Python,
>>> and we work to make every important API and framework within Ubuntu
>>> available from Python."
>> I emailed the Ubuntu Touch list to ask if there is a plan.
> See the debate here:
>
> https://lists.launchpad.net/ubuntu-phone/msg01235.html
>
> Henry
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside

"It's currently *not even possible* to write a phone app in python."

When i see such statement, all i can say is, we didn't need them ...
Many phone apps are made in Python + a gui toolkit, even on Android, iPhone, Maemo/MeeGo ...

--
Benoît HERVIER - http://khertan.net



From sdeibel at wingware.com  Thu Mar 21 14:39:58 2013
From: sdeibel at wingware.com (Stephan Deibel)
Date: Thu, 21 Mar 2013 09:39:58 -0400
Subject: [PySide] Honkin Idea for PySide's thriving
In-Reply-To: <514ADB51.7010109@khertan.net>
References: <1F30AF68-F941-4786-B8D3-B65F1E1ABC97@stackless.com>
	<1363791841.13681.5.camel@farnsworth>
	<1363794499.13681.16.camel@farnsworth>
	<1363847833.3476.0.camel@farnsworth> <514ADB51.7010109@khertan.net>
Message-ID: <514B0DAE.8060009@wingware.com>

Benoît HERVIER wrote:
> "It's currently*not even possible*  to write a phone app in python."
>
> When i see such statement, all i can say is, we didn't need them ...
> Many phone apps are made in Python + a gui toolkit, even on Android, iPhone, Maemo/MeeGo ...

What's even more suspect in that thread is the blanket prohibition 
against Python for being too slow.  That's, like, so 1990's. ;-)

Also seems to show that they don't understand that when you write a line 
in Python 99% of the work is actually done in C code.  Arguing this 
stuff can be pretty futile, however.

Thanks, Henry, for bringing it up on Ubuntu's list.  Since Barry Warsaw 
(one of the original Python core developers) is on there I think there 
probably is hope of something coming out of it despite the negative 
comments in the thread.

- Stephan



From adrian.klaver at gmail.com  Thu Mar 21 15:43:16 2013
From: adrian.klaver at gmail.com (Adrian Klaver)
Date: Thu, 21 Mar 2013 07:43:16 -0700
Subject: [PySide] Honkin Idea for PySide's thriving
In-Reply-To: <514B0DAE.8060009@wingware.com>
References: <1F30AF68-F941-4786-B8D3-B65F1E1ABC97@stackless.com>
	<1363791841.13681.5.camel@farnsworth>
	<1363794499.13681.16.camel@farnsworth>
	<1363847833.3476.0.camel@farnsworth>
	<514ADB51.7010109@khertan.net> <514B0DAE.8060009@wingware.com>
Message-ID: <514B1C84.3000707@gmail.com>

On 03/21/2013 06:39 AM, Stephan Deibel wrote:
> Benoît HERVIER wrote:
>> "It's currently*not even possible*  to write a phone app in python."
>>
>> When i see such statement, all i can say is, we didn't need them ...
>> Many phone apps are made in Python + a gui toolkit, even on Android, iPhone, Maemo/MeeGo ...
>
> What's even more suspect in that thread is the blanket prohibition
> against Python for being too slow.  That's, like, so 1990's. ;-)
>
> Also seems to show that they don't understand that when you write a line
> in Python 99% of the work is actually done in C code.  Arguing this
> stuff can be pretty futile, however.
>
> Thanks, Henry, for bringing it up on Ubuntu's list.  Since Barry Warsaw
> (one of the original Python core developers) is on there I think there
> probably is hope of something coming out of it despite the negative
> comments in the thread.

I would not count on it. Canonical seems bent on creating a new path for 
themselves with as little reference to what exists now as possible.

>
> - Stephan
>



-- 
Adrian Klaver
adrian.klaver at gmail.com


From sable at users.sourceforge.net  Thu Mar 21 16:30:49 2013
From: sable at users.sourceforge.net (=?ISO-8859-1?Q?S=E9bastien_Sabl=E9?=)
Date: Thu, 21 Mar 2013 16:30:49 +0100
Subject: [PySide] Summary of PySide BoF at PyCon
In-Reply-To: <5149EF0D.9060107@wingware.com>
References: <5149EF0D.9060107@wingware.com>
Message-ID: <CAJqKL-sMP_umac8K2c-46eVGTiHH83LmFgTEDrqbvAhhFWhfLQ@mail.gmail.com>

Thanks a lot Stephan for the detailed summary of those discussions at
PyCon. And nice to see so much activity around PySide.

I won't be able to travel to Austin in coming months, but I would be really
interested in getting the minutes of those meetings as well.

Best regards

Sébastien


2013/3/20 Stephan Deibel <sdeibel at wingware.com>

> Hi,
>
> Here is a summary of the PySide BoF that was held on Saturday March
> 16that PyCon 2013 in Santa Clara, CA.  We found there is a lot of
> interest at companies that chose PySide for its licensing.  Several
> companies that were present started a collaboration in order to move
> towards a work plan and coordinated funding and further development of
> PySide.  If you are interested in joining this effort, please contact me.
>
> Introductions
> -------------
>
> The purpose of this BoF was to gather together users invested in PySide,
> review the status of PySide, and move towards revitalizing the project.
> Twelve individuals attended, including representatives of Wingware,
> Enthought, Valve, Disney, and several other companies.
>
> The meeting started with each individual introducing themselves and
> describing their use of PySide and any concerns that they have.
> Licensing issues were the reason most of the users present (representing
> at least 5 companies) chose PySide over PyQt.  All of those citing
> licensing as a problem have a scripting API for their users, which
> requires royalties to be paid on revenues if PyQt is used.
>
> Experiences with stability of PySide varied.  Though most had run into
> some issues, some were able to work around them while most others felt
> that fixes are needed for significant bugs.  Several present indicated a
> concern for the overall future of PySide, particularly in the context of
> supporting Qt5, making PySide more maintainable, and reestablishing a
> team of reviewers and committers.
>
> Several attendees expressed gratitude to the previous developers of
> PySide, especially Hugo for remaining involved as approver/committer.
>
> Discussion of Issues
> --------------------
>
> A discussion of the major issues to be solved followed.  Issues brought
> up included stability, Qt5 support, lack of reviewers and committers,
> problems with the current review process, need for doing a release from
> latest revision, and need to process the accumulated list of bug reports
> that have not received any action.
>
> It was noted that Digia is not returning calls or emails concerning
> PySide.  The possibility of forking PySide and moving it out of the Qt
> Project development toolset was brought up but consensus was established
> that this was not desirable if it could be avoided.  If a fork is
> considered later, legal consul would be asked about trademark, licensing
> considerations, and the potential for re-merging changes into the Qt
> Project at a later date.
>
> Some specific bugs were discussed, including causes of life cycle
> issues, and whether bugs are fixable without rewriting parts of PySide.
>
> Plan of Action
> --------------
>
> Several attending stated that it may be possible for their companies to
> providing funds or staff, given an acceptable development plan and
> process.  This will be investigated further by each potential
> contributor, and some additional companies were identified and will be
> approached.
>
> Representatives of Enthought stated that they could host a week-long
> meeting aimed at creating a work plan and kick-starting work on PySide.
>
> [The one-hour time available in the open space slot ended here and a
> subset of the attendees adjourned to a nearby bar :-]
>
> Several attendees offered to act as future reviewers and committers for
> PySide:  John Ehresman (contributor to PyGTK) from Wingware, Christian
> Tismer (author of Stackless Python), along with Enthought staff:  Robin
> Dunn (author of wxPython), Jason McCampbell, and Robert Kern.
>
> Discussion followed concerning development approaches.  Those present
> agreed that rewriting PySide from scratch is a large task and would lose
> the special cases already worked through and dealt with by PySide.  The
> possibility of a partial rewrite in Python was raised.  Another
> possibility raised was to convert the XML encoding of special cases into
> some more readable and maintainable form, similar to the one used in
> PyGTK and PyScintilla2.  Expanded developer documentation is also needed.
>
> A discussion of the amount and cost of work involved followed.
> Estimates ranged from about 1 to 4 FTE years to cover bug fixes, Qt5
> support, and sheparding the project towards a sustainable future.
>
> Action Items
> ------------
>
> The meeting attendees will work together to arrange a week in the next
> few months, to be held at Enthought in Austin TX, in order to develop a
> work plan to serve as the foundation for collaboration among interested
> companies.  Possible attendees include John Ehresman, Robin Dunn,
> Christian Tismer and any others interested and able to attend.
>
> Several individuals will further investigate the possibility of their
> companies contributing development funds and/or effort.
>
> Enthought will look into any legal issues that need to be addressed.
>
> Several attendees will try to contact other companies identified at the
> meeting, that might be able to participate in drafting and
> implementation of a work plan.  This could include using the recent
> PySide survey on this mailing list to find potential contributors.
>
> A PySide sprint will be held at SciPy 2013 in June.
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130321/ce12d445/attachment.html>

From lndndev at gmail.com  Fri Mar 22 10:00:37 2013
From: lndndev at gmail.com (lndn)
Date: Fri, 22 Mar 2013 02:00:37 -0700
Subject: [PySide] How to Generate PySide Documentation
Message-ID: <CAJ6WS8uH50C6XXs3as3FiGB84is-eBYOxwFwPv9i2QQfRYMHPQ@mail.gmail.com>

Does anybody know how the PySide documentation was generated?  I can't
imagine this being a straight forward task.  I want to take a look at how
feasible it is to reconstruct the 1.1.0 and maybe get a 1.1.2 documentation
created as well.

I think we badly need documentation for the latest version of PySide and
keep this momentum going forward if PySide is going to receive new updates
in the future.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130322/a2f78096/attachment.html>

From backup.rlacko at gmail.com  Fri Mar 22 15:59:57 2013
From: backup.rlacko at gmail.com (Roman Lacko)
Date: Fri, 22 Mar 2013 15:59:57 +0100
Subject: [PySide] How to Generate PySide Documentation
In-Reply-To: <CAJ6WS8uH50C6XXs3as3FiGB84is-eBYOxwFwPv9i2QQfRYMHPQ@mail.gmail.com>
References: <CAJ6WS8uH50C6XXs3as3FiGB84is-eBYOxwFwPv9i2QQfRYMHPQ@mail.gmail.com>
Message-ID: <CAHC6v6hx0WoeMD6hqrPM9phjRBv=XsUcfbA6652KGWCAjBVy2w@mail.gmail.com>

I'm trying to generate the latest documentation for version 1.1.2 (on
windows). I will send here the mini-howto when it's ready.

R.


2013/3/22 lndn <lndndev at gmail.com>

> Does anybody know how the PySide documentation was generated?  I can't
> imagine this being a straight forward task.  I want to take a look at how
> feasible it is to reconstruct the 1.1.0 and maybe get a 1.1.2 documentation
> created as well.
>
> I think we badly need documentation for the latest version of PySide and
> keep this momentum going forward if PySide is going to receive new updates
> in the future.
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130322/b6136cd0/attachment.html>

From sean at seanfisk.com  Fri Mar 22 16:49:48 2013
From: sean at seanfisk.com (Sean Fisk)
Date: Fri, 22 Mar 2013 11:49:48 -0400
Subject: [PySide] How to Generate PySide Documentation
In-Reply-To: <CAHC6v6hx0WoeMD6hqrPM9phjRBv=XsUcfbA6652KGWCAjBVy2w@mail.gmail.com>
References: <CAJ6WS8uH50C6XXs3as3FiGB84is-eBYOxwFwPv9i2QQfRYMHPQ@mail.gmail.com>
	<CAHC6v6hx0WoeMD6hqrPM9phjRBv=XsUcfbA6652KGWCAjBVy2w@mail.gmail.com>
Message-ID: <304CA0FF8E57419E8C6AA19307E6D70A@gmail.com>

The PySide docs use Sphinx, correct? Could setting up automatic generation with Read the Docs (https://readthedocs.org/) be a viable option?

-- 
Sean Fisk


On Friday, March 22, 2013 at 10:59 AM, Roman Lacko wrote:

> I'm trying to generate the latest documentation for version 1.1.2 (on windows). I will send here the mini-howto when it's ready.
> 
> R.
> 
> 
> 2013/3/22 lndn <lndndev at gmail.com (mailto:lndndev at gmail.com)>
> > Does anybody know how the PySide documentation was generated?  I can't imagine this being a straight forward task.  I want to take a look at how feasible it is to reconstruct the 1.1.0 and maybe get a 1.1.2 documentation created as well.
> > 
> > I think we badly need documentation for the latest version of PySide and keep this momentum going forward if PySide is going to receive new updates in the future. 
> > _______________________________________________
> > PySide mailing list
> > PySide at qt-project.org (mailto:PySide at qt-project.org)
> > http://lists.qt-project.org/mailman/listinfo/pyside
> > 
> 
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org (mailto:PySide at qt-project.org)
> http://lists.qt-project.org/mailman/listinfo/pyside
> 
> 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130322/8a6f4c9a/attachment.html>

From projetmbc at gmail.com  Fri Mar 22 18:28:34 2013
From: projetmbc at gmail.com (Christophe BAL)
Date: Fri, 22 Mar 2013 18:28:34 +0100
Subject: [PySide] Problem - Painter and TableWidget
Message-ID: <CAAb4jGkXbnFJC-UTeLceLr=pL0o3Pnd+XD5AOwg2b5f_051joA@mail.gmail.com>

Hello,
I would like to draw some shapes upon some cells of tablewidget. One
solution was proposed to me on
the site stackoverflow.

The following code works with *PySide 1.0.1-1* in *Ubuntu 0.1* but not with
*PySide 1.1.0.* in *Enthought*
*Python Distribution (EPD) Free **version - Version: 7.3-2 (32-bit)*. I
have the following message :

QPainter::begin: A paint device can only be painted by one painter at a
time.

What is the problem ?


Best regards.
Christophe


*===**===** CODE **===**===*
*
*
*#! /usr/bin/env python2.7*
*# -*- coding: utf-8 -*-*
*
*
*import sys*
*
*
*from PySide import QtCore, QtGui*
*
*
*
*
*class PaintTable(QtGui.QTableWidget):*
*    def __init__(self, parent):*
*        QtGui.QTableWidget.__init__(self, parent)*
*        self.center = QtCore.QPoint(-10,-10)*
*
*
*    def paintEvent(self, event):*
*        painter = QtGui.QPainter(self.viewport()) #See:
http://stackoverflow.com/questions/12226930/overriding-qpaintevents-in-pyqt*
*        painter.drawEllipse(self.center,10,10)*
*        QtGui.QTableWidget.paintEvent(self,event)*
*        painter.end()*
*
*
*    def mousePressEvent(self, event):*
*        if event.buttons() == QtCore.Qt.RightButton:*
*            self.center = QtCore.QPoint(event.pos().x(),  event.pos().y())*
*            print self.center*
*            self.viewport().repaint()*
*
*
*        elif event.buttons() == QtCore.Qt.LeftButton:*
*            QtGui.QTableWidget.mousePressEvent(self,event)*
*
*
*class MainWindow(PaintTable):*
*    def __init__(*
*        self,*
*        parent = None*
*    ):*
*        super(MainWindow, self).__init__(parent)*
*
*
*# General grid*
*        self.table = PaintTable(self)*
*        self.nbrow, self.nbcol = 9, 9*
*        self.table.setRowCount(self.nbrow)*
*        self.table.setColumnCount(self.nbcol)*
*        for row in range(0, self.nbrow):*
*            self.table.setRowHeight(row, 50)*
*
*
*            for col in range(0, self.nbcol):*
*                self.table.setColumnWidth(col, 50)*
*
*
*# Each cell contains one single QTableWidgetItem*
*        for row in range(0, self.nbrow):*
*            for col in range(0, self.nbcol):*
*                item = QtGui.QTableWidgetItem()*
*                item.setTextAlignment(*
*                    QtCore.Qt.AlignHCenter | QtCore.Qt.AlignVCenter*
*                )*
*
*
*                self.table.setItem(row, col, item)*
*
*
*# Header formatting*
*        font = QtGui.QFont()*
*        font.setFamily(u"DejaVu Sans")*
*        font.setPointSize(12)*
*        self.table.horizontalHeader().setFont(font)*
*        self.table.verticalHeader().setFont(font)*
*
*
*# Font used*
*        font = QtGui.QFont()*
*        font.setFamily(u"DejaVu Sans")*
*        font.setPointSize(20)*
*        self.table.setFont(font)*
*
*
*# Global Size*
*        self.resize(60*9, 60*9 + 20)*
*
*
*# Layout of the table*
*        layout = QtGui.QGridLayout()*
*        layout.addWidget(self.table, 0, 0)*
*        self.setLayout(layout)*
*
*
*# Set the focus in the first cell*
*        self.table.setFocus()*
*        self.table.setCurrentCell(0, 0)*
*
*
*
*
*
*
*if __name__ == "__main__":*
*    app = QtGui.QApplication(sys.argv)*
*    fen = MainWindow()*
*    fen.show()*
*    sys.exit(app.exec_())*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130322/2aa75b1b/attachment.html>

From nmelchior at seegrid.com  Fri Mar 22 22:34:22 2013
From: nmelchior at seegrid.com (Nik Melchior)
Date: Fri, 22 Mar 2013 17:34:22 -0400
Subject: [PySide] Additional pyside reviewers
In-Reply-To: <514750BD.7060504@wingware.com>
References: <CAJyon0vanPWaucHhhrq5wDnS-Tg91eMTdtfsS7172w4v0Eo=SA@mail.gmail.com>
	<CAHfg+FPpYG+-TYzpAUJGKi6w_netfEQodr0cgn6G_5wzmukrcw@mail.gmail.com>
	<50CB38FC.6000807@wingware.com> <1592310.DtA18LIKW2@hugodesktop>
	<514750BD.7060504@wingware.com>
Message-ID: <20130322213421.GA26252@a367.seegrid.com>

On Mon, Mar 18, 2013 at 10:37:01AM -0700, John Ehresman wrote:
> On 12/14/12 9:01 AM, Hugo Parente Lima wrote:
> > To be reviewer, I propose John Ehresman or John Cummings, some of
> > the last useful commits in months were made by them.
>
> I'd like to pick up this thread from a few months ago and ask if we
> can add more approvers to the pyside project.  If I'm reading the qt
> rules at http://qt-project.org/wiki/The_Qt_Governance_Model correctly,
> we need a nomination and a second from current approvers.
>
> I ask now because I want to move towards a new shiboken & pyside
> release.  There are a few bugs fixed in the current sources and we
> should push those fixes out.  Is there any documentation of what is
> needed to make a new release?

I've finally submitted a pull request to what I believe is the official
PySide/Tools repository on github:

https://github.com/PySide/Tools/

If a new release is in the works, I'd like to see these changes reviewed and
included.  But I see another pull request next to mine that is 9 months old.
What else can I do to help?

--
Nik Melchior
Sr. Roboticist       | 412-379-4500 x147
Seegrid Corporation  | www.seegrid.com
216 Park West Drive, Pittsburgh, PA 15275
Email Confidentiality Notice

The information contained in this transmission is confidential, proprietary or privileged and may be subject to protection under the law. This message is intended for the sole use of the individual or entity to whom it's addressed. If you are not the intended recipient, you are notified that any use, distribution or copying of the message is strictly prohibited and may subject you to criminal or civil penalties. If you received this transmission in error, please contact the sender immediately by replying to this email and delete the material from any computer.


From hugo.lima at openbossa.org  Fri Mar 22 22:39:33 2013
From: hugo.lima at openbossa.org (Hugo Parente Lima)
Date: Fri, 22 Mar 2013 18:39:33 -0300
Subject: [PySide] Additional pyside reviewers
In-Reply-To: <20130322213421.GA26252@a367.seegrid.com>
References: <CAJyon0vanPWaucHhhrq5wDnS-Tg91eMTdtfsS7172w4v0Eo=SA@mail.gmail.com>
	<514750BD.7060504@wingware.com>
	<20130322213421.GA26252@a367.seegrid.com>
Message-ID: <2712400.vL0sA1f4FC@hugodesktop>

On Friday, March 22, 2013 05:34:22 PM Nik Melchior wrote:
> On Mon, Mar 18, 2013 at 10:37:01AM -0700, John Ehresman wrote:
> > On 12/14/12 9:01 AM, Hugo Parente Lima wrote:
> > > To be reviewer, I propose John Ehresman or John Cummings, some of
> > > the last useful commits in months were made by them.
> > 
> > I'd like to pick up this thread from a few months ago and ask if we
> > can add more approvers to the pyside project.  If I'm reading the qt
> > rules at http://qt-project.org/wiki/The_Qt_Governance_Model correctly,
> > we need a nomination and a second from current approvers.
> > 
> > I ask now because I want to move towards a new shiboken & pyside
> > release.  There are a few bugs fixed in the current sources and we
> > should push those fixes out.  Is there any documentation of what is
> > needed to make a new release?
> 
> I've finally submitted a pull request to what I believe is the official
> PySide/Tools repository on github:
> 
> https://github.com/PySide/Tools/
> 
> If a new release is in the works, I'd like to see these changes reviewed and
> included.  But I see another pull request next to mine that is 9 months
> old. What else can I do to help?

I need the github user name of the new people in charge to add them as admin 
on github.
 
> --
> Nik Melchior
> Sr. Roboticist       | 412-379-4500 x147
> Seegrid Corporation  | www.seegrid.com
> 216 Park West Drive, Pittsburgh, PA 15275
> Email Confidentiality Notice
> 
> The information contained in this transmission is confidential, proprietary
> or privileged and may be subject to protection under the law. This message
> is intended for the sole use of the individual or entity to whom it's
> addressed. If you are not the intended recipient, you are notified that any
> use, distribution or copying of the message is strictly prohibited and may
> subject you to criminal or civil penalties. If you received this
> transmission in error, please contact the sender immediately by replying to
> this email and delete the material from any computer.
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130322/3ea277b4/attachment.sig>

From lndndev at gmail.com  Sat Mar 23 02:04:51 2013
From: lndndev at gmail.com (lndn)
Date: Fri, 22 Mar 2013 18:04:51 -0700
Subject: [PySide] How to Generate PySide Documentation
In-Reply-To: <CAHC6v6hx0WoeMD6hqrPM9phjRBv=XsUcfbA6652KGWCAjBVy2w@mail.gmail.com>
References: <CAJ6WS8uH50C6XXs3as3FiGB84is-eBYOxwFwPv9i2QQfRYMHPQ@mail.gmail.com>
	<CAHC6v6hx0WoeMD6hqrPM9phjRBv=XsUcfbA6652KGWCAjBVy2w@mail.gmail.com>
Message-ID: <CAJ6WS8tgKyyeHsH+j5TvZETpMVQz9S_Uc1UvEOUTvAWhuFoiuw@mail.gmail.com>

Thats great!  If you get a mini-howto, I'll post it on the PySide wiki.
 That way we'll have a method of getting the documentation back if it ever
gets lost again.


On Fri, Mar 22, 2013 at 7:59 AM, Roman Lacko <backup.rlacko at gmail.com>wrote:

> I'm trying to generate the latest documentation for version 1.1.2 (on
> windows). I will send here the mini-howto when it's ready.
>
> R.
>
>
> 2013/3/22 lndn <lndndev at gmail.com>
>
>>  Does anybody know how the PySide documentation was generated?  I can't
>> imagine this being a straight forward task.  I want to take a look at how
>> feasible it is to reconstruct the 1.1.0 and maybe get a 1.1.2 documentation
>> created as well.
>>
>> I think we badly need documentation for the latest version of PySide and
>> keep this momentum going forward if PySide is going to receive new updates
>> in the future.
>>
>> _______________________________________________
>> PySide mailing list
>> PySide at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/pyside
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130322/020eceec/attachment.html>

From backup.rlacko at gmail.com  Sat Mar 23 08:47:33 2013
From: backup.rlacko at gmail.com (Roman Lacko)
Date: Sat, 23 Mar 2013 08:47:33 +0100
Subject: [PySide] Additional pyside reviewers
In-Reply-To: <2712400.vL0sA1f4FC@hugodesktop>
References: <CAJyon0vanPWaucHhhrq5wDnS-Tg91eMTdtfsS7172w4v0Eo=SA@mail.gmail.com>
	<514750BD.7060504@wingware.com>
	<20130322213421.GA26252@a367.seegrid.com>
	<2712400.vL0sA1f4FC@hugodesktop>
Message-ID: <CAHC6v6iafdKsehEJ5W4NZRAxnJ8-jc_+SaB320XWeR=e7NQmEw@mail.gmail.com>

Hi Hugo, I thought that the official repository is here
https://qt.gitorious.org/pyside/pyside-tools
or is the github repos synchronized with https://qt.gitorious.org/pyside ?
Thanks
R.

2013/3/22 Hugo Parente Lima <hugo.lima at openbossa.org>

> On Friday, March 22, 2013 05:34:22 PM Nik Melchior wrote:
> > On Mon, Mar 18, 2013 at 10:37:01AM -0700, John Ehresman wrote:
> > > On 12/14/12 9:01 AM, Hugo Parente Lima wrote:
> > > > To be reviewer, I propose John Ehresman or John Cummings, some of
> > > > the last useful commits in months were made by them.
> > >
> > > I'd like to pick up this thread from a few months ago and ask if we
> > > can add more approvers to the pyside project.  If I'm reading the qt
> > > rules at http://qt-project.org/wiki/The_Qt_Governance_Model correctly,
> > > we need a nomination and a second from current approvers.
> > >
> > > I ask now because I want to move towards a new shiboken & pyside
> > > release.  There are a few bugs fixed in the current sources and we
> > > should push those fixes out.  Is there any documentation of what is
> > > needed to make a new release?
> >
> > I've finally submitted a pull request to what I believe is the official
> > PySide/Tools repository on github:
> >
> > https://github.com/PySide/Tools/
> >
> > If a new release is in the works, I'd like to see these changes reviewed
> and
> > included.  But I see another pull request next to mine that is 9 months
> > old. What else can I do to help?
>
> I need the github user name of the new people in charge to add them as
> admin
> on github.
>
> > --
> > Nik Melchior
> > Sr. Roboticist       | 412-379-4500 x147
> > Seegrid Corporation  | www.seegrid.com
> > 216 Park West Drive, Pittsburgh, PA 15275
> > Email Confidentiality Notice
> >
> > The information contained in this transmission is confidential,
> proprietary
> > or privileged and may be subject to protection under the law. This
> message
> > is intended for the sole use of the individual or entity to whom it's
> > addressed. If you are not the intended recipient, you are notified that
> any
> > use, distribution or copying of the message is strictly prohibited and
> may
> > subject you to criminal or civil penalties. If you received this
> > transmission in error, please contact the sender immediately by replying
> to
> > this email and delete the material from any computer.
> > _______________________________________________
> > PySide mailing list
> > PySide at qt-project.org
> > http://lists.qt-project.org/mailman/listinfo/pyside
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130323/5856b856/attachment.html>

From chigga101 at gmail.com  Sun Mar 24 19:37:45 2013
From: chigga101 at gmail.com (Matthew Ngaha)
Date: Sun, 24 Mar 2013 18:37:45 +0000
Subject: [PySide] bin folder
Message-ID: <CACzNyA2F0Mgg6cJQDNLdpAard5Fx6eagJxRxjV-pf3wkBSVHjA@mail.gmail.com>

hi i was doing a tutorial and it said:

To view what you have created, run the QML Viewer tool (located in the
bin directory of your Qt installation) with your filename as the first
argument. For example, to run the provided completed Tutorial 1
example from the install location, you would type:

1. bin/qmlviewer tutorial1.qml


i cant find any bin folder, i ran a search also, nothing returned. Can
anyone help?
also where exactly does it want me to type that? the command line?

Thanks


From akabaila at pcug.org.au  Sun Mar 24 22:08:18 2013
From: akabaila at pcug.org.au (Algis Kabaila)
Date: Mon, 25 Mar 2013 08:08:18 +1100
Subject: [PySide] bin folder
In-Reply-To: <CACzNyA2F0Mgg6cJQDNLdpAard5Fx6eagJxRxjV-pf3wkBSVHjA@mail.gmail.com>
References: <CACzNyA2F0Mgg6cJQDNLdpAard5Fx6eagJxRxjV-pf3wkBSVHjA@mail.gmail.com>
Message-ID: <1480235.Zm64tu7yRG@supremo>

Hi,

What OS are you using?  

It would appear that the instructions are for a linux system CLI (Command 
Line Interface).  Often ~bin is the place for executable files. 

I think it is generally advisable to give as much information about your 
problem and your system before asking a question - it makes it easier for 
people to help you.

OldAl.

On Sunday 24 March 2013 18:37:45 Matthew Ngaha wrote:
> hi i was doing a tutorial and it said:
> 
> To view what you have created, run the QML Viewer tool (located in the
> bin directory of your Qt installation) with your filename as the first
> argument. For example, to run the provided completed Tutorial 1
> example from the install location, you would type:
> 
> 1. bin/qmlviewer tutorial1.qml
> 
> 
> i cant find any bin folder, i ran a search also, nothing returned. Can
> anyone help?
> also where exactly does it want me to type that? the command line?
> 
> Thanks
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130325/35b4334d/attachment.html>

From chigga101 at gmail.com  Sun Mar 24 22:36:51 2013
From: chigga101 at gmail.com (Matthew Ngaha)
Date: Sun, 24 Mar 2013 21:36:51 +0000
Subject: [PySide] bin folder
In-Reply-To: <1480235.Zm64tu7yRG@supremo>
References: <CACzNyA2F0Mgg6cJQDNLdpAard5Fx6eagJxRxjV-pf3wkBSVHjA@mail.gmail.com>
	<1480235.Zm64tu7yRG@supremo>
Message-ID: <CACzNyA2Mm2gkCFUToqYCe5MSERHGMpYXHD96TEGpqa5Dt0Xraw@mail.gmail.com>

> What OS are you using?
>
>
>
> It would appear that the instructions are for a linux system CLI (Command
> Line Interface). Often ~bin is the place for executable files.
>
>
>
> I think it is generally advisable to give as much information about your
> problem and your system before asking a question - it makes it easier for
> people to help you.
>
>

yes sorry about that, i believe its because i am using windows (vista)
i do not have access to a bin folder. I will just run it directly for
windows. Thanks


From rladwig3 at hotmail.com  Mon Mar 25 04:04:52 2013
From: rladwig3 at hotmail.com (Roberto Ladwig)
Date: Mon, 25 Mar 2013 03:04:52 +0000
Subject: [PySide] bug report at installer
Message-ID: <SNT002-W216242A701FFAA5293260D49ED70@phx.gbl>

found a bug at install time with the package  PySlide1.1.2.tgz. i also go the same error using  pip install.
this error occurs in an AMD 64 bit system running  opensuse linux 12.3 but it is highly probable it will occur in any 64bit system.

after the software finishes compiling and linking all the llibraties and gets ready to copy them to the proper location;
the package errors out stating that the address in question does not exist.

this address is 
~/PySide-1.1.2/pyside_install/py2.7-qt4.8.4-64bit-relese/lib/python2.7/site-packages/
the address does exist  but the installer somehow gets the wrong path value at copy time
the problem resides at this level.
~/PySide-1.1.2/pyside_install/py2.7-qt4.8.4-64bit-relese/lib
there are two libraries one is 32bit the other one is 64bit 
since i don't know what variable controls the path name  i had to make a symbolic link to the 64bit version  an only at that point the installer worked.
mv  ~/PySide-1.1.2/pyside_install/py2.7-qt4.8.4-64bit-relese/lib ~/PySide-1.1.2/pyside_install/py2.7-qt4.8.4-64bit-relese/lib32
ln -s ~/PySide-1.1.2/pyside_install/py2.7-qt4.8.4-64bit-relese/lib64 ~/PySide-1.1.2/pyside_install/py2.7-qt4.8.4-64bit-relese/lib

only at that point the installer ran correctly.


thanks all
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130325/a0d9ca30/attachment.html>

From backup.rlacko at gmail.com  Mon Mar 25 08:44:47 2013
From: backup.rlacko at gmail.com (Roman Lacko)
Date: Mon, 25 Mar 2013 08:44:47 +0100
Subject: [PySide] bug report at installer
In-Reply-To: <SNT002-W216242A701FFAA5293260D49ED70@phx.gbl>
References: <SNT002-W216242A701FFAA5293260D49ED70@phx.gbl>
Message-ID: <CAHC6v6is1=QVYDnUQe2x_W9zTARMPsHfvQUzbR2D-g8432UqsA@mail.gmail.com>

Hi, can you send my full build output ?

I have not SUSE but have successfully compiled and installed PySide from
source package on Ubuntu 12.04 64bit.

Thanks
R.


2013/3/25 Roberto Ladwig <rladwig3 at hotmail.com>

> found a bug at install time with the package  PySlide1.1.2.tgz. i also go
> the same error using  pip install.
> this error occurs in an AMD 64 bit system running  opensuse linux 12.3 but
> it is highly probable it will occur in any 64bit system.
>
> after the software finishes compiling and linking all the llibraties and
> gets ready to copy them to the proper location;
> the package errors out stating that the address in question does not exist.
>
> this address is
>
> ~/PySide-1.1.2/pyside_install/py2.7-qt4.8.4-64bit-relese/lib/python2.7/site-packages/
> the address does exist  but the installer somehow gets the wrong path
> value at copy time
> the problem resides at this level.
> ~/PySide-1.1.2/pyside_install/py2.7-qt4.8.4-64bit-relese/lib
> there are two libraries one is 32bit the other one is 64bit
> since i don't know what variable controls the path name  i had to make a
> symbolic link to the 64bit version  an only at that point the installer
> worked.
> mv  ~/PySide-1.1.2/pyside_install/py2.7-qt4.8.4-64bit-relese/lib
> ~/PySide-1.1.2/pyside_install/py2.7-qt4.8.4-64bit-relese/lib32
> ln -s ~/PySide-1.1.2/pyside_install/py2.7-qt4.8.4-64bit-relese/lib64
> ~/PySide-1.1.2/pyside_install/py2.7-qt4.8.4-64bit-relese/lib
>
> only at that point the installer ran correctly.
>
>
> thanks all
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130325/98712544/attachment.html>

From backup.rlacko at gmail.com  Mon Mar 25 13:11:58 2013
From: backup.rlacko at gmail.com (Roman Lacko)
Date: Mon, 25 Mar 2013 13:11:58 +0100
Subject: [PySide] How to Generate PySide Documentation
In-Reply-To: <CAJ6WS8tgKyyeHsH+j5TvZETpMVQz9S_Uc1UvEOUTvAWhuFoiuw@mail.gmail.com>
References: <CAJ6WS8uH50C6XXs3as3FiGB84is-eBYOxwFwPv9i2QQfRYMHPQ@mail.gmail.com>
	<CAHC6v6hx0WoeMD6hqrPM9phjRBv=XsUcfbA6652KGWCAjBVy2w@mail.gmail.com>
	<CAJ6WS8tgKyyeHsH+j5TvZETpMVQz9S_Uc1UvEOUTvAWhuFoiuw@mail.gmail.com>
Message-ID: <CAHC6v6gUQx-kv-8F_QKcqJPjS6A9Kjy51g0-ySf3N8iUdQLDQA@mail.gmail.com>

Hi,
I made some progress on doc generation. here is is what will be available
(if everything goes well):

- doc generation will be included in python-setup build scripts so everyone
can build the documentation when needed

- Starting from next version PySide prebuild packages will contain full
shiboken and pyside documentation out-of-the-box for offline reading

- PySide and Shiboken documentation will be available on Read The Docs
(allraedy reserved the site here https://readthedocs.org/projects/pyside/)

R.


2013/3/23 lndn <lndndev at gmail.com>

> Thats great!  If you get a mini-howto, I'll post it on the PySide wiki.
>  That way we'll have a method of getting the documentation back if it ever
> gets lost again.
>
>
> On Fri, Mar 22, 2013 at 7:59 AM, Roman Lacko <backup.rlacko at gmail.com>wrote:
>
>> I'm trying to generate the latest documentation for version 1.1.2 (on
>> windows). I will send here the mini-howto when it's ready.
>>
>> R.
>>
>>
>> 2013/3/22 lndn <lndndev at gmail.com>
>>
>>>  Does anybody know how the PySide documentation was generated?  I can't
>>> imagine this being a straight forward task.  I want to take a look at how
>>> feasible it is to reconstruct the 1.1.0 and maybe get a 1.1.2 documentation
>>> created as well.
>>>
>>> I think we badly need documentation for the latest version of PySide and
>>> keep this momentum going forward if PySide is going to receive new updates
>>> in the future.
>>>
>>> _______________________________________________
>>> PySide mailing list
>>> PySide at qt-project.org
>>> http://lists.qt-project.org/mailman/listinfo/pyside
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130325/53deeb90/attachment.html>

From hugo.lima at openbossa.org  Mon Mar 25 15:05:38 2013
From: hugo.lima at openbossa.org (Hugo Parente Lima)
Date: Mon, 25 Mar 2013 11:05:38 -0300
Subject: [PySide] Additional pyside reviewers
In-Reply-To: <CAHC6v6iafdKsehEJ5W4NZRAxnJ8-jc_+SaB320XWeR=e7NQmEw@mail.gmail.com>
References: <CAJyon0vanPWaucHhhrq5wDnS-Tg91eMTdtfsS7172w4v0Eo=SA@mail.gmail.com>
	<2712400.vL0sA1f4FC@hugodesktop>
	<CAHC6v6iafdKsehEJ5W4NZRAxnJ8-jc_+SaB320XWeR=e7NQmEw@mail.gmail.com>
Message-ID: <4564296.v6o7eXkor7@hugodesktop>

On Saturday, March 23, 2013 08:47:33 AM Roman Lacko wrote:
> Hi Hugo, I thought that the official repository is here
> https://qt.gitorious.org/pyside/pyside-tools
> or is the github repos synchronized with https://qt.gitorious.org/pyside ?
> Thanks
> R.

PySide-tools isn't on Qt-Project for unknown reasons, so any sync was made by 
hand until now and the official repository would be anyone, gitorious or github, 
your choice, or you may request a move to Qt-Project.
 
> 2013/3/22 Hugo Parente Lima <hugo.lima at openbossa.org>
> 
> > On Friday, March 22, 2013 05:34:22 PM Nik Melchior wrote:
> > > On Mon, Mar 18, 2013 at 10:37:01AM -0700, John Ehresman wrote:
> > > > On 12/14/12 9:01 AM, Hugo Parente Lima wrote:
> > > > > To be reviewer, I propose John Ehresman or John Cummings, some of
> > > > > the last useful commits in months were made by them.
> > > > 
> > > > I'd like to pick up this thread from a few months ago and ask if we
> > > > can add more approvers to the pyside project.  If I'm reading the qt
> > > > rules at http://qt-project.org/wiki/The_Qt_Governance_Model correctly,
> > > > we need a nomination and a second from current approvers.
> > > > 
> > > > I ask now because I want to move towards a new shiboken & pyside
> > > > release.  There are a few bugs fixed in the current sources and we
> > > > should push those fixes out.  Is there any documentation of what is
> > > > needed to make a new release?
> > > 
> > > I've finally submitted a pull request to what I believe is the official
> > > PySide/Tools repository on github:
> > > 
> > > https://github.com/PySide/Tools/
> > > 
> > > If a new release is in the works, I'd like to see these changes reviewed
> > 
> > and
> > 
> > > included.  But I see another pull request next to mine that is 9 months
> > > old. What else can I do to help?
> > 
> > I need the github user name of the new people in charge to add them as
> > admin
> > on github.
> > 
> > > --
> > > Nik Melchior
> > > Sr. Roboticist       | 412-379-4500 x147
> > > Seegrid Corporation  | www.seegrid.com
> > > 216 Park West Drive, Pittsburgh, PA 15275
> > > Email Confidentiality Notice
> > > 
> > > The information contained in this transmission is confidential,
> > 
> > proprietary
> > 
> > > or privileged and may be subject to protection under the law. This
> > 
> > message
> > 
> > > is intended for the sole use of the individual or entity to whom it's
> > > addressed. If you are not the intended recipient, you are notified that
> > 
> > any
> > 
> > > use, distribution or copying of the message is strictly prohibited and
> > 
> > may
> > 
> > > subject you to criminal or civil penalties. If you received this
> > > transmission in error, please contact the sender immediately by replying
> > 
> > to
> > 
> > > this email and delete the material from any computer.
> > > _______________________________________________
> > > PySide mailing list
> > > PySide at qt-project.org
> > > http://lists.qt-project.org/mailman/listinfo/pyside
> > 
> > _______________________________________________
> > PySide mailing list
> > PySide at qt-project.org
> > http://lists.qt-project.org/mailman/listinfo/pyside
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130325/eb2d5f8a/attachment.sig>

From akabaila at pcug.org.au  Mon Mar 25 23:59:39 2013
From: akabaila at pcug.org.au (Algis Kabaila)
Date: Tue, 26 Mar 2013 09:59:39 +1100
Subject: [PySide] How to Generate PySide Documentation
In-Reply-To: <CAHC6v6gUQx-kv-8F_QKcqJPjS6A9Kjy51g0-ySf3N8iUdQLDQA@mail.gmail.com>
References: <CAJ6WS8uH50C6XXs3as3FiGB84is-eBYOxwFwPv9i2QQfRYMHPQ@mail.gmail.com>
	<CAJ6WS8tgKyyeHsH+j5TvZETpMVQz9S_Uc1UvEOUTvAWhuFoiuw@mail.gmail.com>
	<CAHC6v6gUQx-kv-8F_QKcqJPjS6A9Kjy51g0-ySf3N8iUdQLDQA@mail.gmail.com>
Message-ID: <50530085.cxpgNjHI3l@supremo>

Roman,

Excellent news! Good documentation is so important - it can make or break 
any development effort.

Have you thought of getting users to write ir rst (Restructured Text 
format).? It is easy and the "raw drafts" can be quite readable.  Then, of 
course, Sphinx will translate them to pdf or html format.

I saw this method successfully used in the development of "Bazaar".  
Unfortunately, the man leading the development of this documentation 
method passed away, though his work still lingers on.

OldAl.

On Monday 25 March 2013 13:11:58 Roman Lacko wrote:

Hi,
I made some progress on doc generation. here is is what will be available 
(if everything goes well):


- doc generation will be included in python-setup build scripts so 
everyone can build the documentation when needed

- Starting from next version PySide prebuild packages will contain full 
shiboken and pyside documentation out-of-the-box for offline reading


- PySide and Shiboken documentation will be available on Read The Docs 
(allraedy reserved the site here https://readthedocs.org/projects/pyside/)


R.




2013/3/23 lndn <lndndev at gmail.com>

Thats great!  If you get a mini-howto, I'll post it on the PySide wiki. 
 That way we'll have a method of getting the documentation back if it ever 
gets lost again.



On Fri, Mar 22, 2013 at 7:59 AM, Roman Lacko <backup.rlacko at gmail.com> 
wrote:

I'm trying to generate the latest documentation for version 1.1.2 (on 
windows). I will send here the mini-howto when it's ready.


R.




2013/3/22 lndn <lndndev at gmail.com>

Does anybody know how the PySide documentation was generated?  I can't 
imagine this being a straight forward task.  I want to take a look at how 
feasible it is to reconstruct the 1.1.0 and maybe get a 1.1.2 
documentation created as well.


I think we badly need documentation for the latest version of PySide and 
keep this momentum going forward if PySide is going to receive new updates 
in the future.


_______________________________________________
PySide mailing list
PySide at qt-project.org
http://lists.qt-project.org/mailman/listinfo/pyside










-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130326/9a4383ae/attachment.html>

From backup.rlacko at gmail.com  Tue Mar 26 17:15:50 2013
From: backup.rlacko at gmail.com (Roman Lacko)
Date: Tue, 26 Mar 2013 17:15:50 +0100
Subject: [PySide] How to Generate PySide Documentation
In-Reply-To: <CAHC6v6gUQx-kv-8F_QKcqJPjS6A9Kjy51g0-ySf3N8iUdQLDQA@mail.gmail.com>
References: <CAJ6WS8uH50C6XXs3as3FiGB84is-eBYOxwFwPv9i2QQfRYMHPQ@mail.gmail.com>
	<CAHC6v6hx0WoeMD6hqrPM9phjRBv=XsUcfbA6652KGWCAjBVy2w@mail.gmail.com>
	<CAJ6WS8tgKyyeHsH+j5TvZETpMVQz9S_Uc1UvEOUTvAWhuFoiuw@mail.gmail.com>
	<CAHC6v6gUQx-kv-8F_QKcqJPjS6A9Kjy51g0-ySf3N8iUdQLDQA@mail.gmail.com>
Message-ID: <CAHC6v6iCoFSmV3bAL+TLpZ1N06-BX7fLaW0-XXokm3+mm73vBw@mail.gmail.com>

Shiboken docs are online [1]

PySide doc generation have problems, so please be patient...

[1] https://shiboken.readthedocs.org/en/latest/

R.

2013/3/25 Roman Lacko <backup.rlacko at gmail.com>

> Hi,
> I made some progress on doc generation. here is is what will be available
> (if everything goes well):
>
> - doc generation will be included in python-setup build scripts so
> everyone can build the documentation when needed
>
> - Starting from next version PySide prebuild packages will contain full
> shiboken and pyside documentation out-of-the-box for offline reading
>
> - PySide and Shiboken documentation will be available on Read The Docs
> (allraedy reserved the site here https://readthedocs.org/projects/pyside/)
>
> R.
>
>
> 2013/3/23 lndn <lndndev at gmail.com>
>
>> Thats great!  If you get a mini-howto, I'll post it on the PySide wiki.
>>  That way we'll have a method of getting the documentation back if it ever
>> gets lost again.
>>
>>
>> On Fri, Mar 22, 2013 at 7:59 AM, Roman Lacko <backup.rlacko at gmail.com>wrote:
>>
>>> I'm trying to generate the latest documentation for version 1.1.2 (on
>>> windows). I will send here the mini-howto when it's ready.
>>>
>>> R.
>>>
>>>
>>> 2013/3/22 lndn <lndndev at gmail.com>
>>>
>>>>  Does anybody know how the PySide documentation was generated?  I
>>>> can't imagine this being a straight forward task.  I want to take a look at
>>>> how feasible it is to reconstruct the 1.1.0 and maybe get a 1.1.2
>>>> documentation created as well.
>>>>
>>>> I think we badly need documentation for the latest version of PySide
>>>> and keep this momentum going forward if PySide is going to receive new
>>>> updates in the future.
>>>>
>>>> _______________________________________________
>>>> PySide mailing list
>>>> PySide at qt-project.org
>>>> http://lists.qt-project.org/mailman/listinfo/pyside
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130326/2677037d/attachment.html>

From jpe at wingware.com  Tue Mar 26 18:19:53 2013
From: jpe at wingware.com (John Ehresman)
Date: Tue, 26 Mar 2013 13:19:53 -0400
Subject: [PySide] Near term plans for pyside
Message-ID: <5151D8B9.20600@wingware.com>

I'd like to outline what I'd like to see happen regarding pyside in the
near-term:

* Getting a new minor release out -- there are fixes in the git
repository that should be more widely used so I'm interested in making a
release of the current code, with perhaps a few other minor fixes.  The
release will come from a new team of developers (including myself) and
we'll be learning how to do it along the way.

* Improving documentation for Python developers -- Roman and Indn have
started working on the wiki and the generated documentation and my hope
is that we can generate / update docs in the future as releases occur.

* Cleaning up the bug tracker -- numerous bugs have been filed and I
need to get a sense of them and their relative importance.  Some can be
closed (at least one of my bugs is fixed but I don't currently have the
privileges to close it) and perhaps others are easy fixes.  I'd also
like to get more people looking at the tracker and triaging reports.

* Getting more people up to speed on pyside internals -- the more people
that know how the C++ core of pyside works, the more people who can fix
bugs and improve it.  I plan on helping C++ developers as they dive into
the code as well as trying to document the internals.  My hope is that
we can get a few more developers involved and to the point where they
can be added as reviewers.

Further down the road (but not that far) is improving things at the C++
level and working on supporting qt5.

If you can help with any of this, please consider contributing to
pyside.  You can ask here if you have questions or on #pyside on
freenode (I would like to see the irc channel become more active).

Cheers,

John


From lndndev at gmail.com  Tue Mar 26 21:58:26 2013
From: lndndev at gmail.com (lndn)
Date: Tue, 26 Mar 2013 13:58:26 -0700
Subject: [PySide] Near term plans for pyside
In-Reply-To: <5151D8B9.20600@wingware.com>
References: <5151D8B9.20600@wingware.com>
Message-ID: <CAJ6WS8vjmXuYb3j+nvVLPc_MPPYUuioWn8h-8OESvQSfD-ARKA@mail.gmail.com>

I've been patiently waiting for an email like this, thank you!

I'll continue working on the wiki and documentation and update the roadmap
to include the points you mentioned.  I'm also on the #pyside IRC channel
so if anybody is on, find me.


On Tue, Mar 26, 2013 at 10:19 AM, John Ehresman <jpe at wingware.com> wrote:

> I'd like to outline what I'd like to see happen regarding pyside in the
> near-term:
>
> * Getting a new minor release out -- there are fixes in the git
> repository that should be more widely used so I'm interested in making a
> release of the current code, with perhaps a few other minor fixes.  The
> release will come from a new team of developers (including myself) and
> we'll be learning how to do it along the way.
>
> * Improving documentation for Python developers -- Roman and Indn have
> started working on the wiki and the generated documentation and my hope
> is that we can generate / update docs in the future as releases occur.
>
> * Cleaning up the bug tracker -- numerous bugs have been filed and I
> need to get a sense of them and their relative importance.  Some can be
> closed (at least one of my bugs is fixed but I don't currently have the
> privileges to close it) and perhaps others are easy fixes.  I'd also
> like to get more people looking at the tracker and triaging reports.
>
> * Getting more people up to speed on pyside internals -- the more people
> that know how the C++ core of pyside works, the more people who can fix
> bugs and improve it.  I plan on helping C++ developers as they dive into
> the code as well as trying to document the internals.  My hope is that
> we can get a few more developers involved and to the point where they
> can be added as reviewers.
>
> Further down the road (but not that far) is improving things at the C++
> level and working on supporting qt5.
>
> If you can help with any of this, please consider contributing to
> pyside.  You can ask here if you have questions or on #pyside on
> freenode (I would like to see the irc channel become more active).
>
> Cheers,
>
> John
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130326/b5600e41/attachment.html>

From robin at alldunn.com  Thu Mar 28 18:22:49 2013
From: robin at alldunn.com (Robin Dunn)
Date: Thu, 28 Mar 2013 10:22:49 -0700
Subject: [PySide] Near term plans for pyside
In-Reply-To: <5151D8B9.20600@wingware.com>
References: <5151D8B9.20600@wingware.com>
Message-ID: <51547C69.9000301@alldunn.com>

John Ehresman wrote:
> I'd like to outline what I'd like to see happen regarding pyside in the
> near-term:

...

> * Getting more people up to speed on pyside internals -- the more people
> that know how the C++ core of pyside works, the more people who can fix
> bugs and improve it.  I plan on helping C++ developers as they dive into
> the code as well as trying to document the internals.  My hope is that
> we can get a few more developers involved and to the point where they
> can be added as reviewers.

I am definitely interested in helping out here. (Or at least my 
enthought.com persona is ;-) )  Hopefully many of my experiences with 
wxPython will carry over well and will be useful here.

One thing that would be helpful for new contributors is a getting 
started doc of some sort.  There are bits and pieces of this all over, 
but having it all in one spot would be good.  If it does already exist 
somewhere then let's make it more prominent.  Some things it should 
include are:

  * Which of the source repositories should be considered the master copy.

  * Which repos should collectively be considered to be PySide.  (PySide 
+ Shiboken + PySide-Tools ???  Are there others?)

  * Where is the issue tracker?

  * How should contributions be submitted?  Pull requests?  Patches 
attached to tracked issues? Something else?

  * What coding standards should be followed?

  * How to build PySide

  * etc.


>
> Further down the road (but not that far) is improving things at the C++
> level and working on supporting qt5.
>
> If you can help with any of this, please consider contributing to
> pyside.  You can ask here if you have questions or on #pyside on
> freenode (I would like to see the irc channel become more active).

I'm there as RobinD.


-- 
Robin Dunn
Software Craftsman
http://wxPython.org


From robin at alldunn.com  Thu Mar 28 18:40:36 2013
From: robin at alldunn.com (Robin Dunn)
Date: Thu, 28 Mar 2013 10:40:36 -0700
Subject: [PySide] Near term plans for pyside
In-Reply-To: <51547C69.9000301@alldunn.com>
References: <5151D8B9.20600@wingware.com> <51547C69.9000301@alldunn.com>
Message-ID: <51548094.9020000@alldunn.com>

Robin Dunn wrote:
> One thing that would be helpful for new contributors is a getting
> started doc of some sort. There are bits and pieces of this all over,
> but having it all in one spot would be good. If it does already exist
> somewhere then let's make it more prominent. Some things it should
> include are:

Of course right after I sent this I found 
http://qt-project.org/wiki/PySideDevelopment


-- 
Robin Dunn
Software Craftsman
http://wxPython.org


From jpe at wingware.com  Thu Mar 28 20:54:03 2013
From: jpe at wingware.com (John Ehresman)
Date: Thu, 28 Mar 2013 15:54:03 -0400
Subject: [PySide] Near term plans for pyside
In-Reply-To: <51548094.9020000@alldunn.com>
References: <5151D8B9.20600@wingware.com> <51547C69.9000301@alldunn.com>
	<51548094.9020000@alldunn.com>
Message-ID: <51549FDB.5010207@wingware.com>

On 3/28/13 1:40 PM, Robin Dunn wrote:
> Robin Dunn wrote:
>> One thing that would be helpful for new contributors is a getting
>> started doc of some sort. There are bits and pieces of this all over,
>> but having it all in one spot would be good. If it does already exist
>> somewhere then let's make it more prominent. Some things it should
>> include are:
> 
> Of course right after I sent this I found
> http://qt-project.org/wiki/PySideDevelopment

Good to see you here Robin!  I also have the scripts I use to build
pyside and its dependencies at https://bitbucket.org/jpe/buildruntimes
I'm someone that likes to build everything from source with debug
options enabled during development and to script the build process as
much as possible.

Cheers,

John



From lndndev at gmail.com  Thu Mar 28 21:06:52 2013
From: lndndev at gmail.com (lndn)
Date: Thu, 28 Mar 2013 13:06:52 -0700
Subject: [PySide] Near term plans for pyside
In-Reply-To: <51547C69.9000301@alldunn.com>
References: <5151D8B9.20600@wingware.com> <51547C69.9000301@alldunn.com>
Message-ID: <CAJ6WS8tgGTPPztKkPgm3KtLA-zziuB2KWxGgkkDKcS2_Dwy3jg@mail.gmail.com>

> One thing that would be helpful for new contributors is a getting
> started doc of some sort.  There are bits and pieces of this all over,
> but having it all in one spot would be good.  If it does already exist
> somewhere then let's make it more prominent.  Some things it should
> include are:
>
>   * Which of the source repositories should be considered the master copy.
>
>   * Which repos should collectively be considered to be PySide.  (PySide
> + Shiboken + PySide-Tools ???  Are there others?)
>
>   * Where is the issue tracker?
>
>   * How should contributions be submitted?  Pull requests?  Patches
> attached to tracked issues? Something else?
>
>   * What coding standards should be followed?
>
>   * How to build PySide
>
>   * etc.



> Of course right after I sent this I found
> http://qt-project.org/wiki/PySideDevelopment



Also on this page is a "Getting Started with PySide Development" [1].  I
started this guide about a week ago and its far from complete but I'll use
your questions above as a guide to include more information.  The guide is
targeting new and beginners who are not familiar with PySide.


[1] http://qt-project.org/wiki/PySide_Development_Getting_Started
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130328/60062eee/attachment.html>

From robin at alldunn.com  Thu Mar 28 22:26:22 2013
From: robin at alldunn.com (Robin Dunn)
Date: Thu, 28 Mar 2013 14:26:22 -0700
Subject: [PySide] Near term plans for pyside
In-Reply-To: <51549FDB.5010207@wingware.com>
References: <5151D8B9.20600@wingware.com> <51547C69.9000301@alldunn.com>
	<51548094.9020000@alldunn.com> <51549FDB.5010207@wingware.com>
Message-ID: <5154B57E.7050603@alldunn.com>

John Ehresman wrote:
> On 3/28/13 1:40 PM, Robin Dunn wrote:
>> Robin Dunn wrote:
>>> One thing that would be helpful for new contributors is a getting
>>> started doc of some sort. There are bits and pieces of this all over,
>>> but having it all in one spot would be good. If it does already exist
>>> somewhere then let's make it more prominent. Some things it should
>>> include are:
>> Of course right after I sent this I found
>> http://qt-project.org/wiki/PySideDevelopment
>
> Good to see you here Robin!  I also have the scripts I use to build
> pyside and its dependencies at https://bitbucket.org/jpe/buildruntimes
> I'm someone that likes to build everything from source with debug
> options enabled during development and to script the build process as
> much as possible.

Thanks, I'll take a look at those.  I'm pretty much the same way usually.


-- 
Robin Dunn
Software Craftsman
http://wxPython.org


From sean at seanfisk.com  Sun Mar 31 09:36:03 2013
From: sean at seanfisk.com (Sean Fisk)
Date: Sun, 31 Mar 2013 03:36:03 -0400
Subject: [PySide] Centered image while maintaining aspect ratio
Message-ID: <906DA85D535C405BBD810A40F85ED77D@gmail.com>

Hello all, 

This took me a while to figure out, so I thought I would share it with the list for others needing similar functionality.

I was working on a small program in which I wanted two panes: the left should contain a QTextEdit and a QPushButton and the right should contain an image generated from the input on the left. I wanted the image on the right to be as large as possible while maintaining the original aspect ratio. The image is an SVG generated by Graphviz (http://graphviz.org/) and pydot (https://code.google.com/p/pydot/). Here is a link to a screenshot (http://seanfisk.github.com/database-serializability-graph/screenshot.png) of how it looks.

After messing around with layouts quite a bit, I realized that the right way to do it was to render the SVG on a restricted part of the canvas. QSvgWidget, which is a thin wrapper around QSvgRenderer, renders the SVG as large as possible without aspect ratio by default. This code does the trick to keep the SVG at the default aspect ratio:
from __future__ import division from PySide import QtCore, QtGui, QtSvg class AspectRatioSvgWidget(QtSvg.QSvgWidget): def paintEvent(self, paint_event): painter = QtGui.QPainter(self) default_width, default_height = self.renderer().defaultSize().toTuple() widget_width, widget_height = self.size().toTuple() ratio_x = widget_width / default_width ratio_y = widget_height / default_height if ratio_x < ratio_y: new_width = widget_width new_height = widget_width * default_height / default_width new_left = 0 new_top = (widget_height - new_height) / 2 else: new_width = widget_height * default_width / default_height new_height = widget_height new_left = (widget_width - new_width) / 2 new_top = 0 self.renderer().render( painter, QtCore.QRectF(new_left, new_top, new_width, new_height))

The key to this was realizing the default width of the SVG (which implicitly indicates the aspect ratio) can be accessed using self.renderer().defaultSize(). Now when the window is resized the SVG is as large as possible while maintaing the ratio.
I also have code laying around for a centered bitmap (e.g., PNG) which maintains its original aspect ratio. Given the choice between SVG and PNG, though, SVG was the clear winner. Kudos to Qt and PySide for having awesome SVG support too!
The full code is available on Github (https://github.com/seanfisk/database-serializability-graph) under serial_graph/gui.py. Hope this helps someone out!

Sincerely,

-- 
Sean Fisk

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130331/6fad687f/attachment.html>

From schampailler at skynet.be  Sun Mar 31 17:40:10 2013
From: schampailler at skynet.be (Stefan Champailler)
Date: Sun, 31 Mar 2013 17:40:10 +0200
Subject: [PySide] Resurrecting PySide
In-Reply-To: <CAJ6WS8tFZpScDnyYs12T+tnDZrEp+RHPLUW3J6VYBZFPyr98RA@mail.gmail.com>
References: <CAJ6WS8tFZpScDnyYs12T+tnDZrEp+RHPLUW3J6VYBZFPyr98RA@mail.gmail.com>
Message-ID: <515858DA.3030606@skynet.be>

Hi Indn, good work !
Stefan


On 03/17/2013 12:10 PM, lndn wrote:
> All the recent scary "PySide is Dead" emails really prompted me to think
> about what we can do to improve the situation.  Not being familiar with the
> PySide/Shiboken internals, I thought it would be a good idea to start by
> cleaning up the wiki pages on qt-project.
>
> However, as I combed through these pages, I noticed that many of the links
> were broken and pointing to old pyside.org pages that no longer exist and
> the content contains outdated and incomplete information.  What is really
> needed is a major overhaul in updating the content.
>
> So what's the official word on a massive re-organizing of these pages?  Can
> I just take the initiative and do it?  I'd like to start off by just
> putting the wiki pages in some order so things are easy to find and then
> later go through the content and update the content one page at a time.  My
> goal is just to help users and developers easily navigate to the pages they
> need.
>
> Any thoughts or people interested in helping would be great.
>
> Thanks,
> lndn
>
>
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside

-- 
Timeo Danaos et dona ferentes

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20130331/166364f1/attachment.html>