Re: [cdt-dev] Qt Support?

[<David.Dubrow@xxxxxxxxx>]

EDC has support for custom formatters at three levels including the value
column value, detail pane value and member tree elements. Formatted values
are also shown in the debug hover. The support allows for editing custom
formatted values, although we haven't added any formatters that take
advantage of that feature yet. The reason they have been added at the EDC
level is that they rely heavily on the EDC symbolics support.

For Qt, I've recently added custom formatters for QString, QByteArray, QSet,
QHash, QMap, QVector, QList, QLinkedList and Qvariant and created a lot of
abstract base classes to support further development. There are also default
formatters for composite types as well as arrays that are used when no other
formatters are found.

BR,
David

On 7/13/10 10:15 AM, "Paul Warren" <Warren.Paul@xxxxxxxxx> wrote:

> We've already added variable formatting to EDC for most of the common Qt
> types.  We plan to support debugging of Win32 Qt apps with EDC in our next
> product release, so you can expect that support to be commercial quality.  It
> should also work with EDC on Linux, though we don't currently have Linux
> hosted products so won't be doing any active testing of it.  I don't believe
> EDC currently works on Mac.  I think we've had a conversation on this list
> before about what it would take to do a Mac TCF agent, but I don't recall the
> details.  It's something I'd love to see, but since we have no plans for Mac
> hosted products I can't commit any resources to make it happen.  :(
> 
> Thanks,
> Warren
> 
> 
>> -----Original Message-----
>> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
>> On Behalf Of ext Marc Khouzam
>> Sent: Tuesday, July 13, 2010 10:02 AM
>> To: 'CDT General developers list.'
>> Subject: RE: [cdt-dev] Qt Support?
>> 
>>>> KDevelop has some pretty-printers for Qt types located here:
>>>> 
>>> http://gitorious.org/kdevelop/kdevelop/trees/master/debuggers/
>>> gdb/printers
>>>> 
>>>> They also work nicely with Eclipse, however for testing I used a
>>>> patched CDT with the patch from
>>>> Bug 302121, I don't know how well it works with 7.0
>>>> 
>>>> 
>>>> Alex Richardson
>>> 
>>> *sigh* and that is the solution that will probably be used. There is
>>> one single problem with that. Those pretty printers need GDB
>>> 7.x which
>>> does not really work on OS X. So I am stuck with the Apple supplied
>>> GDB.
>> 
>> Apparently, there has been some efforts by Tristan Gingold to make
>> GDB 7.1 work on Mac.  If someone wants to take the ball (I don't have
>> a Mac) and see if it truly works, I believe we could have a very
>> interesting debugging solution for Mac.
>> 
>> We can work with Tristan off-list if there are still issues
>> to be resolved.
>> 
>> Marc
>> 
>> 
>>> I was hoping that the CDT/Qt integration could implement the Qt
>>> Type formatting the same way as in QtCreator using some
>>> static library
>>> that gets compiled into the source.
>>>     I do agree with you though. Switching between QtCreator and
>>> Eclipse does throw off the efficiency of the workflow. I have stated
>>> shadowing QStrings with std::string for debugging where
>>> needed. Klunky
>>> but does work.
>>> 
>>> Mike Jackson
>>> _______________________________________________
>>> cdt-dev mailing list
>>> cdt-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>> _______________________________________________
>> cdt-dev mailing list
>> cdt-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev