[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [dsdp-dd-dev] Memory View Technology Subgroup Discussion
|
Mikhail -
One of the features of a memory rendering is that it is designed to be
portable, meaning that it could be displayed in places other than the
Memory View. As long as a workbench part / view part implements the
require IMemoryRenderingContainer and IMemoryRenderingSite interfaces, a
part could potentially display a memory rendering. For example, if the
details pane of the Variables View implements these two interfaces, we can
display the Hex rendering in the details pane of the Variables View.
What I meant was that if the editor that we use implements the
IMemoryRenderingContainer and IMemoryRenderingSite interfaces, an editor
can potentially display a memory rendering. In this case, the disassembly
rendering can be shown in the editor. We can resuse the code in a
disassembly rendering and do not have to come up with two different
solutions for showing disasembly in the Memory View and in an editor.
Thanks...
Samantha
"Mikhail
Khodjaiants"
<mikhailk@xxxxxxx To
> "Device Debugging developer
Sent by: discussions"
dsdp-dd-dev-bounc <dsdp-dd-dev@xxxxxxxxxxx>
es@xxxxxxxxxxx cc
Subject
05/17/2006 05:51 Re: [dsdp-dd-dev] Memory View
PM Technology Subgroup Discussion
Please respond to
Device Debugging
developer
discussions
<dsdp-dd-dev@ecli
pse.org>
Samantha, I don't know about you, but I'm lost in the editor/disassembly
discussion.
----- Original Message -----
From: "Samantha Chan" <chanskw@xxxxxxxxxx>
To: "Device Debugging developer discussions" <dsdp-dd-dev@xxxxxxxxxxx>
Sent: Wednesday, May 17, 2006 5:01 PM
Subject: Re: [dsdp-dd-dev] Memory View Technology Subgroup Discussion
> Thanks Mikhail. I added this feature to the wiki page.
>
> When addressing this feature, I think we also need to look at what's
being
> done in the Editor and Disassembly view subgroup discussions.
Hopefully
> we can reuse the same approach / designs when showing disassembly in
these
> different places.
>
> One idea I have about this is that in addition to having a disassembly
> rendering, we could also make the editor capable of hosting memory
> renderings. In this case, the disassembly rendering can be embedded and
> re-used in the editor. It also allows us to show disassembly along with
> source code.
>
> Thanks...
> Samantha
>
>
>
>
> "Mikhail
> Khodjaiants"
> <mikhailk@xxxxxxx To
> > "Device Debugging developer
> Sent by: discussions"
> dsdp-dd-dev-bounc <dsdp-dd-dev@xxxxxxxxxxx>
> es@xxxxxxxxxxx cc
>
> Subject
> 05/16/2006 01:12 Re: [dsdp-dd-dev] Memory View
> PM Technology Subgroup Discussion
>
>
> Please respond to
> Device Debugging
> developer
> discussions
> <dsdp-dd-dev@ecli
> pse.org>
>
>
>
>
>
>
> Hi Samantha,
>
> One of the our most popular requests (and a very old one) is "Show memory
> as disassembly" - https://bugs.eclipse.org/bugs/show_bug.cgi?id=27892.
> It's
> kind of a rendering but needs a disassembler. I think it makes sense to
> add
> it to your list.
>
> Mikhail Khodjaiants_______________________________________________
> dsdp-dd-dev mailing list
> dsdp-dd-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dsdp-dd-dev
>
>
> _______________________________________________
> dsdp-dd-dev mailing list
> dsdp-dd-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dsdp-dd-dev
_______________________________________________
dsdp-dd-dev mailing list
dsdp-dd-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dsdp-dd-dev
