From jchris.fillionr at kitware.com Mon Apr 14 18:23:02 2014 From: jchris.fillionr at kitware.com (Jean-Christophe Fillion-Robin) Date: Mon, 14 Apr 2014 14:23:02 -0400 Subject: [Ctk-developers] Simplification of CTK PythonQt wrapping Message-ID: Hi Folks, Overview ------------ As some of you knows, CTK provides some CMake function and Qt classes to facilitate the scripting of Qt application using "PythonQt" [1][2] I propose to remove the unmaintained support for PythonQt full wrapping and optimize the existing light wrapping. If you never build CTK with wrapping enabled, you can archive this email. The proposed changes won't impact your existing projects. Details -------- Currently, there is a build option named "CTK_ENABLE_Python_Wrapping" allowing to enable the automatic wrapping of CTK classes and also expose the tool to "wrap" classes within your application. The wrapping exists in two flavors: * Light wrapping (the default) * Full wrapping Light wrapping: This basically check that Qt classes derives from QObject and then create "PythonQtDecorator" allowing to instantiate/delete your classes. Full wrapping: Attempt to make automatic use of the PythonQtGenerator (used to also wrap Qt for PythonQt). Proposed changes: ------------------------ - Removal of option related to "Full" wrapping. This never really worked. It would require us to maintain our set of "xml" files describing CTK classes. See [3] for an examples. Later one, we could also look at PySide[4] and see how it could be supported. - Simplification and optimization of the existing "Light" wrapping. In project like Slicer where there is a lot of library to "light wrap" .. the CMake configuration time is considerably impacted. - Associated issue: https://github.com/commontk/CTK/issues/449 - To learn more about the differences between PySide/PyQt/PythonQt. See "Comparison with PyQt/PySide" on [5] Let me know what you think, Thanks Jc [1] http://pythonqt.sourceforge.net/ [2] https://github.com/commontk/PythonQt#pythonqt [3] https://github.com/commontk/PythonQt/blob/patched-3/generator/typesystem_core.xml [4] https://qt-project.org/wiki/About-PySide [5] http://pythonqt.sourceforge.net/Features.html -- +1 919 869 8849 -------------- next part -------------- An HTML attachment was scrubbed... URL: From pieper at isomics.com Mon Apr 14 21:25:29 2014 From: pieper at isomics.com (Steve Pieper) Date: Mon, 14 Apr 2014 17:25:29 -0400 Subject: [Ctk-developers] Simplification of CTK PythonQt wrapping In-Reply-To: References: Message-ID: +1 On Apr 14, 2014 2:23 PM, "Jean-Christophe Fillion-Robin" < jchris.fillionr at kitware.com> wrote: > Hi Folks, > > Overview > ------------ > As some of you knows, CTK provides some CMake function and Qt classes to > facilitate the scripting of Qt application using "PythonQt" [1][2] > > > I propose to remove the unmaintained support for PythonQt full wrapping > and optimize the existing light wrapping. > > > If you never build CTK with wrapping enabled, you can archive this email. > The proposed changes won't impact your existing projects. > > > Details > -------- > > Currently, there is a build option named "CTK_ENABLE_Python_Wrapping" > allowing to enable the automatic wrapping of CTK classes and also expose > the tool to "wrap" classes within your application. > > > The wrapping exists in two flavors: > > * Light wrapping (the default) > * Full wrapping > > > Light wrapping: This basically check that Qt classes derives from QObject > and then create "PythonQtDecorator" allowing to instantiate/delete your > classes. > > Full wrapping: Attempt to make automatic use of the PythonQtGenerator > (used to also wrap Qt for PythonQt). > > > > Proposed changes: > ------------------------ > > - Removal of option related to "Full" wrapping. This never really worked. > It would require us to maintain our set of "xml" files describing CTK > classes. See [3] for an examples. Later one, we could also look at > PySide[4] and see how it could be supported. > > - Simplification and optimization of the existing "Light" wrapping. In > project like Slicer where there is a lot of library to "light wrap" .. the > CMake configuration time is considerably impacted. > > - Associated issue: https://github.com/commontk/CTK/issues/449 > > - To learn more about the differences between PySide/PyQt/PythonQt. See > "Comparison with PyQt/PySide" on [5] > > > > Let me know what you think, > > Thanks > Jc > > > [1] http://pythonqt.sourceforge.net/ > > [2] https://github.com/commontk/PythonQt#pythonqt > > [3] > https://github.com/commontk/PythonQt/blob/patched-3/generator/typesystem_core.xml > > [4] https://qt-project.org/wiki/About-PySide > > [5] http://pythonqt.sourceforge.net/Features.html > > -- > +1 919 869 8849 > > _______________________________________________ > Ctk-developers mailing list > Ctk-developers at commontk.org > http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pieper at isomics.com Tue Apr 22 14:04:34 2014 From: pieper at isomics.com (Steve Pieper) Date: Tue, 22 Apr 2014 10:04:34 -0400 Subject: [Ctk-developers] St Louis! Message-ID: Hi Folks - I hope everyone is getting their plans finalized for the upcoming hackfest. Personally I'm looking forward to a week focused on dicom, databases, CLIs, and related topics. http://www.commontk.org/index.php/CTK-Hackfest-May-2014 Be sure to update the participant list on the wiki with your plans, and let us know of any issues we should be addressing before the event. Best, Steve -------------- next part -------------- An HTML attachment was scrubbed... URL: From pieper at isomics.com Fri Apr 25 21:01:10 2014 From: pieper at isomics.com (Steve Pieper) Date: Fri, 25 Apr 2014 17:01:10 -0400 Subject: [Ctk-developers] St Louis! In-Reply-To: References: Message-ID: Hi Lawrence - We should fix your on the list :) - maybe it's just a variant email in the subscription compared to your From: field in the email header. You should be able to log in/subscribe/reset password at the mailman page [1]. Regarding QIDO/WADO/STOW I don't believe anyone has started working on it yet. For myself I've been very interested in the database side of things and have been working with nosql (couchdb) and would be interested in plugging in both legacy DIMSE and web services (at least restful) networking. I'm not convinced that C++ and Qt are the right tools for the web version of the networking though, and would probably lean towards python on javascript for that... Looking forward to a great hackfest! -Steve [1] http://public.kitware.com/cgi-bin/mailman/listinfo/ctk-developers On Fri, Apr 25, 2014 at 4:37 PM, Tarbox, Lawrence wrote: > Since I am not allowed to post to the list, I?ll ask you. Do you know > if anyone is working on adding support for the new restful variants of > DICOM services to either dcmtk or ctk? > > > > *From:* Ctk-developers [mailto:ctk-developers-bounces at commontk.org] *On > Behalf Of *Steve Pieper > *Sent:* Tuesday, April 22, 2014 9:05 AM > *To:* ctk-developers at commontk.org > *Subject:* [Ctk-developers] St Louis! > > > > Hi Folks - > > > > I hope everyone is getting their plans finalized for the upcoming > hackfest. Personally I'm looking forward to a week focused on dicom, > databases, CLIs, and related topics. > > > > http://www.commontk.org/index.php/CTK-Hackfest-May-2014 > > > > Be sure to update the participant list on the wiki with your plans, and > let us know of any issues we should be addressing before the event. > > > > Best, > > Steve > > ------------------------------ > > The material in this message is private and may contain Protected > Healthcare Information (PHI). If you are not the intended recipient, be > advised that any unauthorized use, disclosure, copying or the taking of any > action in reliance on the contents of this information is strictly > prohibited. If you have received this email in error, please immediately > notify the sender via telephone or return mail. > -------------- next part -------------- An HTML attachment was scrubbed... URL: