Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-debug-dev] CDT debugger features


Is anybody working on this?  It sounds like this would allow me to view the contents of an icu4c UnicodeString in the debugger, which would be extremely valueable for myself and several over developers in the office.  

thank you,

Gregery Adair
IBM DB2 Entity Analytic Solutions
Las Vegas, NV


----- Original Message ----- From: "John Cortell" <r4609c@xxxxxxxxxxxxx>
To: "CDT Debug developers list" <cdt-debug-dev@xxxxxxxxxxx>
Sent: Tuesday, June 14, 2005 6:58 PM
Subject: Re: [cdt-debug-dev] CDT debugger features


Samantha,

Ah, ok. Great. So the client can both provide specialized rendering and
the UI mechanism that allows the user to switch to that rendering. Thanks
for the details. I'm sure they'll save us some time when we implement this.

John

At 03:52 PM 6/14/2005, Samantha Chan wrote:

John -

I think this is achievable in the CDT layer. CDT can provide a custom

text
rendering by extending AbstractTextRendering. This rendering takes a
code
page when it is constructed. It also has an API to allow clients to
change
its code page after it is created.

In addition, CDT can contribute actions to this custom text rendering

via
object contrbution.  CDT can contribute an action that allows user to
switch between the different display modes on the fly.  When the user

has
switched to a different display mode, the action could change the code
page
on the custom text rendering. Finally, the action would have to tell
the
rendering to update by calling AbstractTableRendering#updateLabel().
This
would not cause the rendering to reget its content. It simply
re-renders
its current content.

Thanks..
Samantha




             John Cortell
            <r4609c@freescale
            .com>

To
             Sent by:                  "CDT Debug developers list"
            cdt-debug-dev-bou         <cdt-debug-dev@xxxxxxxxxxx>
            nces@xxxxxxxxxxx

cc


Subject
06/14/2005 06:23 Re: [cdt-debug-dev] CDT
debugger
             PM                        features


            Please respond to
                CDT Debug
             developers list






At 02:16 PM 6/14/2005, Samantha Chan wrote:
>Re:  d. View memory as UNICODE.
>CDT can provide custom rendering to support this.  It can override
>TextRendering and provide UNICODE as the code page for displaying

memory
>content.

Samantha,

One thing that occurs to me. While the physical rendering of the bytes

in
the Memory View as UNICODE (rather than ASCII) is doable from the CDT
layer, we would nonetheless need to give the user the ability to switch

to
this display mode. In other words, the Memory view doesn't know whether
a
block of memory represents UNICODE or not. It's up to the user to tell
the
Memory view to switch to this alternate rendering mode. So, unless the
client layer (CDT) can add this UI switch to the view, this feature

still
implies some work at the platform level, no?

John

_______________________________________________
cdt-debug-dev mailing list
cdt-debug-dev@xxxxxxxxxxx
<
https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev>https://dev.ecl

ipse.org/mailman/listinfo/cdt-debug-dev


_______________________________________________
cdt-debug-dev mailing list
cdt-debug-dev@xxxxxxxxxxx
<
https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev>https://dev.ecl

ipse.org/mailman/listinfo/cdt-debug-dev


_______________________________________________
cdt-debug-dev mailing list
cdt-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev

Back to the top