Re: GammaRay - Introspection/Debugging Tool for Qt Applications
On Sun, Oct 30, 2011 at 13:21, Volker Krause vkra...@kde.org wrote: Hi! During the Qt Dev Days in Munich last week we (KDAB) released a new Free Software introspection/debugging tool for Qt applications, called GammaRay: https://github.com/KDAB/GammaRay It hooks itself into a Qt application (at start-up or at runtime) using a variety of methods (ranging from assembler hacks to (ab)using Qt plug-ins) and uses the Qt meta object system for introspecting object, properties, signals, slots, signal/slot connections, etc. Nothing really new until here, tools like Qt Inspector or KSpy can do this already. On top of that GammaRay adds a bunch of higher level tools though, for example: - QWidget layout overlay, similar to designer - Inspecting a QGraphicsScene and various details of QGraphicsItems (visualizing shapes, bounding rects, transformation origins, etc) - Looking at the full (proxy) model hierarchy and all intermediate results in there - a live updating QStateMachine visualization - attaching of QScriptEngineDebugger and QWebInspector to the corresponding objects in the application - a QTextDocument document object model viewer Additionally, GammaRay has a plug-in interface for adding new tools, say a KJob tracker. GammaRay works on Linux, Mac and Windows (MSVC only so far), it needs to be compiled against the same Qt version used by the application you are about to debug though. There's also a Qt Creator plug-in for it (https://github.com/KDAB/KDAB-Creator). Some screenshots can be found here: http://www.kdab.com/gammaray GammaRay was originally developed in support for the Kontact Touch project, back when there wasn't a QML debugger yet. The proxy model debugger also proved quite helpful on KMail, maybe it can help some of you as well :) Needless to say that contributions are very much welcome. regards Volker I've asked this at the devdays but want to spread the idea amongst the larger KDE comunity: Can this tool, or it's technologies, be use to make inline translation of a running application possible? Would greatly simplify the process (and more fun!) and get better results since the string changes will be immediately visible, preventing wrong context assumptions and to long strings. Bart
Re: FW: Kleopatra Locking Clipboard
Hi Andrew, there haven't been any responses since your first email. Since you wrote Kleopatra.exe I would suggest you send to the kde-windows list instead. Cheers, Kevin On Wednesday, 2011-11-02, Andrew Birch wrote: Hi guys, I posted the below to kde-de...@kde.orgmailto:kde-de...@kde.org before I was a member of the list so I'm not sure whether it got through or not. Hence, I thought I re-post now I am a member - I would appreciate any advice. Thanks very much in anticipation, Andy Andrew Birch Junior Developer ___ [cid:imagebc90e7.png@6a6f7a50.ae0c4f22] Main: +44 20 7634 8500 Direct: +44 20 7634 8538 Email: andrew.bi...@tradar.com Web:www.tradar.comhttp://www.tradar.com/ This email is subject to the following disclaimer: Tradar disclaimerhttp://www.tradar.com/company/emaildisclaimer.htm. London Office - Old Change House. 128 Queen Victoria Street, London. EC4V 4BJ Tradar Limited is a limited company registered in England and Wales. Registered number: 3431380. Registered office: 20-21 Jockey's Fields, London. WC1R 4BW From: Andrew Birch Sent: 27 October 2011 12:06 To: 'kde-de...@kde.org' Cc: Mark Hazeldine Subject: Kleopatra Locking Clipboard Hi there, Application: Kleopatra (Certificate Manager and Unified Crypto GUI) Version: 2.1.0 KDE Version: 4.1.4 I am a developer who is working on a piece of software that accesses the Clipboard. I am experiencing a problem whereby when trying to access the Clipboard an ExternalException is thrown with the following error message: 'The requested clipboard operation did not succeed'. As a result, I did some diagnostic work to try to work out which application was locking the Clipboard. There seem to be a number of different applications that sometimes lock it (presumably whilst they have access to it). However, the worst offender seems to be Kleopatra.exe. By 'worst' I mean it seems to persistently lock the Clipboard and thus blocks our application from accessing it. We are not actively using Kleopatra when this problem occurs; it is just running in the background. Also, interestingly this problem does not always seem to happen; sometimes Kleopatra doesn't seem to access/lock the Clipboard. I was wondering if you might know why this is and if there is anything we can do to prevent Kleopatra.exe from persistently accessing the Clipboard? Thanks, Andy -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring signature.asc Description: This is a digitally signed message part.
Re: Review Request: Add fromTheme property to QIconItem in QtExtraComponents for theme icons in QML
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/103009/#review7879 --- Ship it! let's go for it ;) - Marco Martin On Nov. 1, 2011, 6:43 p.m., Mark Gaiser wrote: --- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/103009/ --- (Updated Nov. 1, 2011, 6:43 p.m.) Review request for KDE Runtime and Plasma. Description --- Hi, I found it very strange that QIcon::fromTheme was just working. Sadly in KDE's brand new PlasmaComponents it was simply impossible to use the system icons without using plasma to view the QML. This patch adds a property to QIconItem named: fromTheme which allows you to get the icons from the theme you currently use. This patch alone isn't helping a lot of people but i have a second patch ready for PlasmaComponents.Button to make use of this. Oke to commit? Diffs - plasma/declarativeimports/qtextracomponents/qiconitem.h 9972a98 plasma/declarativeimports/qtextracomponents/qiconitem.cpp d72381e Diff: http://git.reviewboard.kde.org/r/103009/diff/diff Testing --- Tested it with a bunch of different icons in and it all just seems to work fine. Thanks, Mark Gaiser
Re: GammaRay - Introspection/Debugging Tool for Qt Applications
On Wednesday 02 November 2011 11:10:17 Bart Cerneels wrote: On Sun, Oct 30, 2011 at 13:21, Volker Krause vkra...@kde.org wrote: Hi! During the Qt Dev Days in Munich last week we (KDAB) released a new Free Software introspection/debugging tool for Qt applications, called GammaRay: https://github.com/KDAB/GammaRay It hooks itself into a Qt application (at start-up or at runtime) using a variety of methods (ranging from assembler hacks to (ab)using Qt plug-ins) and uses the Qt meta object system for introspecting object, properties, signals, slots, signal/slot connections, etc. Nothing really new until here, tools like Qt Inspector or KSpy can do this already. On top of that GammaRay adds a bunch of higher level tools though, for example: - QWidget layout overlay, similar to designer - Inspecting a QGraphicsScene and various details of QGraphicsItems (visualizing shapes, bounding rects, transformation origins, etc) - Looking at the full (proxy) model hierarchy and all intermediate results in there - a live updating QStateMachine visualization - attaching of QScriptEngineDebugger and QWebInspector to the corresponding objects in the application - a QTextDocument document object model viewer Additionally, GammaRay has a plug-in interface for adding new tools, say a KJob tracker. GammaRay works on Linux, Mac and Windows (MSVC only so far), it needs to be compiled against the same Qt version used by the application you are about to debug though. There's also a Qt Creator plug-in for it (https://github.com/KDAB/KDAB-Creator). Some screenshots can be found here: http://www.kdab.com/gammaray GammaRay was originally developed in support for the Kontact Touch project, back when there wasn't a QML debugger yet. The proxy model debugger also proved quite helpful on KMail, maybe it can help some of you as well :) Needless to say that contributions are very much welcome. regards Volker I've asked this at the devdays but want to spread the idea amongst the larger KDE comunity: Can this tool, or it's technologies, be use to make inline translation of a running application possible? Would greatly simplify the process (and more fun!) and get better results since the string changes will be immediately visible, preventing wrong context assumptions and to long strings. I think GammaRay's core (injecting and accessing the object tree) would be a good start for such an inline translation tool. Actually, you can use GammaRay already to edit a lot of user visible strings by changing properties etc., just not fully inline in the UI. However, I see one big challenge with this approach: The strings we access there are already fully assembled, so no placeholders etc. are available anymore. For a real translation tool we would need to be able to query the corresponding unprocessed source string as well (and trigger a re-processing of it after translation, for live updates). regards Volker signature.asc Description: This is a digitally signed message part.
Re: GammaRay - Introspection/Debugging Tool for Qt Applications
On Wednesday 02 November 2011 20:39:02 Peter Kümmel wrote: What is the status of windll? It doesn't work here. Only a prove of principle? I can't test myself, but the GammaRay Windows team (Andreas Holzammer, Nicolas Arnaud-Cormos and Patrick Spendrin, most of whom you probably know from KDE Windows already) tells me it works with MSVC 2008/2010 on x86 32/64bit debug builds and sometimes 32bit release builds. At least it does in the 1.0 branch, there might be recent breakage in master of course. Why do you not use QProcess to start the process in launch? If you aren't already busy on windll I could have a look at it. And is this list the right list to discuss GammaRay, especially when it comes to win32? We don't have a dedicated list (yet), for Windows-specific issues it might be best to talk to the guys listed above directly (note that Andy (who did most of the work) just left for a 4 week Internet-free vacation, and Nicolas is probably not subscribed here). I'm not aware of any of them currently working on that injector, your help is of course very much welcome :) regards Volker signature.asc Description: This is a digitally signed message part.
Re: Review Request: Add fromTheme property to QIconItem in QtExtraComponents for theme icons in QML
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/103009/#review7883 --- This review has been submitted with commit 67b24ecc2694e462a913284c16f3679a2e6851ab by Mark Gaiser to branch master. - Commit Hook On Nov. 1, 2011, 6:43 p.m., Mark Gaiser wrote: --- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/103009/ --- (Updated Nov. 1, 2011, 6:43 p.m.) Review request for KDE Runtime and Plasma. Description --- Hi, I found it very strange that QIcon::fromTheme was just working. Sadly in KDE's brand new PlasmaComponents it was simply impossible to use the system icons without using plasma to view the QML. This patch adds a property to QIconItem named: fromTheme which allows you to get the icons from the theme you currently use. This patch alone isn't helping a lot of people but i have a second patch ready for PlasmaComponents.Button to make use of this. Oke to commit? Diffs - plasma/declarativeimports/qtextracomponents/qiconitem.h 9972a98 plasma/declarativeimports/qtextracomponents/qiconitem.cpp d72381e Diff: http://git.reviewboard.kde.org/r/103009/diff/diff Testing --- Tested it with a bunch of different icons in and it all just seems to work fine. Thanks, Mark Gaiser
Re: Review Request: Add fromTheme property to QIconItem in QtExtraComponents for theme icons in QML
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/103009/#review7884 --- plasma/declarativeimports/qtextracomponents/qiconitem.cpp http://git.reviewboard.kde.org/r/103009/#comment6814 Is there any specific reason why this isn't const QVariant icon? All used QVariant methods are const. - Christoph Feck On Nov. 1, 2011, 6:43 p.m., Mark Gaiser wrote: --- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/103009/ --- (Updated Nov. 1, 2011, 6:43 p.m.) Review request for KDE Runtime and Plasma. Description --- Hi, I found it very strange that QIcon::fromTheme was just working. Sadly in KDE's brand new PlasmaComponents it was simply impossible to use the system icons without using plasma to view the QML. This patch adds a property to QIconItem named: fromTheme which allows you to get the icons from the theme you currently use. This patch alone isn't helping a lot of people but i have a second patch ready for PlasmaComponents.Button to make use of this. Oke to commit? Diffs - plasma/declarativeimports/qtextracomponents/qiconitem.h 9972a98 plasma/declarativeimports/qtextracomponents/qiconitem.cpp d72381e Diff: http://git.reviewboard.kde.org/r/103009/diff/diff Testing --- Tested it with a bunch of different icons in and it all just seems to work fine. Thanks, Mark Gaiser
Re: Review Request: Add fromTheme property to QIconItem in QtExtraComponents for theme icons in QML
On Nov. 2, 2011, 9:58 p.m., Christoph Feck wrote: plasma/declarativeimports/qtextracomponents/qiconitem.cpp, line 37 http://git.reviewboard.kde.org/r/103009/diff/2/?file=40071#file40071line37 Is there any specific reason why this isn't const QVariant icon? All used QVariant methods are const. fixed and pushed. - Mark --- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/103009/#review7884 --- On Nov. 1, 2011, 6:43 p.m., Mark Gaiser wrote: --- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/103009/ --- (Updated Nov. 1, 2011, 6:43 p.m.) Review request for KDE Runtime and Plasma. Description --- Hi, I found it very strange that QIcon::fromTheme was just working. Sadly in KDE's brand new PlasmaComponents it was simply impossible to use the system icons without using plasma to view the QML. This patch adds a property to QIconItem named: fromTheme which allows you to get the icons from the theme you currently use. This patch alone isn't helping a lot of people but i have a second patch ready for PlasmaComponents.Button to make use of this. Oke to commit? Diffs - plasma/declarativeimports/qtextracomponents/qiconitem.h 9972a98 plasma/declarativeimports/qtextracomponents/qiconitem.cpp d72381e Diff: http://git.reviewboard.kde.org/r/103009/diff/diff Testing --- Tested it with a bunch of different icons in and it all just seems to work fine. Thanks, Mark Gaiser
Re: Review Request: kdoctools hard-codes the GNU FDL license and ignores dual-licensing
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/103011/#review7887 --- This review has been submitted with commit 24ae1ee5aaff73ec7faa1f586c90575a2bd29c47 by Robby Stephenson to branch KDE/4.7. - Commit Hook On Nov. 1, 2011, 3:19 a.m., Robby Stephenson wrote: --- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/103011/ --- (Updated Nov. 1, 2011, 3:19 a.m.) Review request for kdelibs. Description --- For documentation, the current KDE docbook customization hard-codes a link to the GNU-FDL for every legalnotice in the doc. While the KDE licensing policy requires documentation to be licensed under the FDL, it does not prohibit dual-licensing (or triple or whatever...). But the current docbook processing doesn't show the second license. This patch maintains current behavior when the legalnotice element includes the link to the FDL, but falls back to normal docbook processing for legal notices which do not reference the FDL. Diffs - kdoctools/customization/kde-chunk.xsl 096de1b Diff: http://git.reviewboard.kde.org/r/103011/diff/diff Testing --- Tested with Tellico's documentation, which is dual-licensed under the GNU FDL and the FreeBSD Documentation License. Also forwarded to the kde-docbook list http://lists.kde.org/?l=kde-docbookm=132004433310804w=2 Thanks, Robby Stephenson
