From tismer at stackless.com Tue Apr 12 19:09:17 2016 From: tismer at stackless.com (Christian Tismer) Date: Tue, 12 Apr 2016 19:09:17 +0200 Subject: [PySide] [pyside-dev] Bringing pyside back to Qt Project Message-ID: <570D2BBD.1000100@stackless.com> [copied from pyside-dev at googlegroups.com -- replies go there] Dear Pyside2 contributors, As you might know, Pyside was originally developed for Nokia while it was the owner of the Qt technology. When Nokia sold Qt to Digia (and now The Qt Company), all the copyrights over the original Pyside code for Qt 4 got transferred to The Qt Company as well. For different reasons, it was not possible for The Qt Company to push Pyside forward as much as we would have wished over the last few years. Fortunately this changed now, and The Qt Company is today in a position, where it can and will invest into Pyside. The goal is to ensure Pyside becomes a fully supported part of the Qt product family, with a similar development and licensing model as the rest of Qt. We want to make sure Pyside works on new Qt releases when they come out and are committed to invest long term into the technology. To do so, requires us to be able to license Pyside in the same way as Qt itself, ie. under both open-source (LGPLv3) and commercial licensing terms. As you probably know, the Qt Company is doing this for Qt by developing the product together with the community/ecosystem on qt-project.org. The reason that development happens on qt-project.org is that patches pushed to it fall under a contribution agreement (see http://www.qt.io/contributionagreement/) , allowing the Qt Company to also have a commercially supported version of Qt, which then funds a lot of the further development of the product. Please note that the contribution agreement is not a copyright assignment, so you as a contributor keep the full rights to the code you developed. Pyside1 has always been hosted on qt-project.org. To make Pyside available for Qt 5 and a fully supported part of the Qt family will require us to develop it on qt-project under the Qt Contribution Agreement. Including the Pyside2 work in this project, would be a great way to kick start it and create a good and open ecosystem around it from the start. We, Christian Tismer and the Qt Company, have already agreed to move Christian’s changes over and to work with the community to achieve this. We would like to ask you as a contributor to Pyside2 to also consider contributing your changes to this effort. We believe there will be many advantages to the Pyside community with this move: * The Qt Company will commit some developers full time, to help develop Pyside further. * The goal is to make Pyside an integral part of new Qt releases. * Pyside will get a lot more exposure to developers and end users when it becomes part of the officially supported Qt packages * The Qt Company will invest into the required testing, QA infrastructure and people * Full bug tracking through the Qt bug tracking system * The Qt Company will help to make sure that Pyside always works with the latest Qt releases * Of course we will keep Pyside available under open source licensing terms, just as free as Qt itself * Companies who require this can purchase a commercially licensed version of Pyside including commercial support * More exposure and visibility to the people working on and contributing to Pyside We sincerely hope you can help us by agreeing to contribute your changes to Pyside2 to this project, so that we can create the best Qt support for Python ever. Please don’t hesitate to ask on this list, if you have any further questions. We would appreciate if you could provide us with feedback on this list or in private. To show your support please create a Qt account under https://login.qt.io/register. Once the registration is complete you can use the Qt account credentials and log into Qt’s codereview tool where you have to accept the Contributor agreement. The acceptance process is described in http://www.qt.io/contributionagreement/. We will then contact each of you individually with details on how to sign off on your own work within Qt’s code review system. Thank you very much. With best regards, Lars Knoll Christian Tismer Qt Chief Maintainer Main Pyside 2 Contributor CTO, The Qt Company -- You received this message because you are subscribed to the Google Groups "pyside-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to pyside-dev+unsubscribe at googlegroups.com . For more options, visit https://groups.google.com/d/optout. -------------- next part -------------- An HTML attachment was scrubbed... URL: From robinsiebler at dslextreme.com Wed Apr 20 22:56:33 2016 From: robinsiebler at dslextreme.com (Robin Siebler) Date: Wed, 20 Apr 2016 13:56:33 -0700 Subject: [PySide] How to select an highlight a row in a QTreeView? Message-ID: <1461185794433-9b3442b1-84c9bca2-e44c2411@dslextreme.com> I am relatively new to Pyside/Qt. I am using a QTreeView with a QFileSystemModel to display a list of files. How can I programmatically select and highlight the 1st one? Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: From nathanjsmith at gmail.com Fri Apr 22 14:16:05 2016 From: nathanjsmith at gmail.com (Nathan Smith) Date: Fri, 22 Apr 2016 12:16:05 +0000 Subject: [PySide] How to select an highlight a row in a QTreeView? In-Reply-To: <1461185794433-9b3442b1-84c9bca2-e44c2411@dslextreme.com> References: <1461185794433-9b3442b1-84c9bca2-e44c2411@dslextreme.com> Message-ID: setCurrentIndex - see http://www.qtcentre.org/threads/15035-QTreeView-how-to-autoselect-first-row On Wed, Apr 20, 2016, 3:56 PM Robin Siebler wrote: > > I am relatively new to Pyside/Qt. > > I am using a QTreeView with a QFileSystemModel to display a list of files. > How can I programmatically select and highlight the 1st one? > > 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: From sean at seanfisk.com Sat Apr 23 00:47:38 2016 From: sean at seanfisk.com (Sean Fisk) Date: Fri, 22 Apr 2016 22:47:38 +0000 Subject: [PySide] PySide and py2app on a Mac OS X system. In-Reply-To: References: Message-ID: Hi Kevin, Some of that sounds similar to well-known problem that I have experienced before which is solved by putting in a widget.raise_(). How are you running the app bundle? Can you post the code? – Sean On Tue, Feb 16, 2016 at 12:03 PM Kevin Cole wrote: > I've been developing my PySide stuff on a Linux box, and happily > starting it from the command line. Things have been working fairly > well for months, barring a recent change that caused a dialog to be > closed too soon -- now corrected. > > However, when I moved to the Mac, and bundled stuff up as a .app/ > directory tree using py2app, I had a minor glitch which has now become > even more annoying: > > I have docked my icon for starting my app. When clicked, it opens the > first dialog which as a button that should open a second dialog. On > Linux, it does. On the Mac, one must go to the dock bar and click the > icon a second time to get the second dialog to show. (There's a dot on > the dock icon indicating the code is "already running" when clicked > the second time.) > > It has now become more annoying, because of my recent understanding > (or misunderstanding) of garbage collection problems. Instead of > merely closing the original dialog, I issue a .hide(). Well, it does > not appear to hide. Worse yet, moving to the dock bar no longer causes > the dock bar to un-hide so that I can click the icon a second time to > launch the second dialog. Instead, I have to click on some other app, > then move to the now-unhiding dock bar, then click the icon a second > time. > > What am I doing wrong? (Probably a lot, but what are the most obvious > candidates for fixing the immediate problem?) > > 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: