Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [platform-debug-dev] extending VariablesView? 
Samantha,

Thanks for the response, and sorry for my delay - busy implementing!
What I want is an *additional* memoryview that just displays my custom renderings. I want to allow the user to continue to use the existing memoryview, as they wish. 

So, I actually want to do both things that you suggested! Is this possible?

Thanks,

---
Derek

Samantha Chan wrote:

Hi Derek -

If you need to write a new view to host renderings, your view need to
implement the IMemoryRenderingSite.  A memory rendering site consists of
one or more memory rendering containers.  Therefore, your view also needs
to implement the IMemoryRenderingContainer interface.  These interfaces
will allow you to add renderings to your view programmatically.

The Memory View implementation is internal and is not an API.  Therefore,
the code is subject to change from release to release.  It is not
recommended that you subclass your new view from the Memory View.

I understand that you do want your custom renderings to be displayed in the
Memory View.  Is it because you do not want your users to use the existing
renderings provided by the platform  (i.e. the table renderings)?  What you
want is a Memory View that displays your custom renderings only and nothing
else?

Thanks...
Samantha
Derek Morris <dmsubs@consertum .com> To Sent by: "Eclipse Platform Debug component platform-debug-de developers list." v-bounces@eclipse <platform-debug-dev@xxxxxxxxxxx> .org cc Subject 08/04/2006 07:35 Re: [platform-debug-dev] extending AM VariablesView? Please respond to "Eclipse Platform Debug component developers list." <platform-debug-d ev@xxxxxxxxxxx> 



Samantha,

Having look through the code, I see that it provides an additional
rendering (HexTree) into the existing memory monitor.

What I would like to do, is create a new (additional) view, based on the
Memory View, but with some new functionality (renderings). I do not want
to add a new rendering to the existing memory view. Is this possible
with the new infrastructure?

Thanks,
---
Derek

Samantha Chan wrote:

Hi  Derek,

You can find the exercises from the same bugzilla entry.  Look for

"Source

for exercises related to "memory view" ".

Here's a quick link to the source for the Memory View exercise.
http://eclipsezilla.eclipsecon.org/attachment.cgi?id=188

Thanks...
Samantha







             Derek Morris



             <dmsubs@consertum



             .com>

To

             Sent by:                  "Eclipse Platform Debug component



             platform-debug-de         developers list."



             v-bounces@eclipse         <platform-debug-dev@xxxxxxxxxxx>



             .org

cc

Subject

             08/03/2006 10:31          Re: [platform-debug-dev] extending



             AM                        VariablesView?





             Please respond to



             "Eclipse Platform



              Debug component



             developers list."



             <platform-debug-d



              ev@xxxxxxxxxxx>








Darin,

The tutorial is very interesting. I might be able to do what I want with
the memory renderings, however, the source for the
example.debug.memoryview exercise is missing. I've done a quick google
and can't find it anywhere. Do you have a pointer to it?

Thanks,

---
Derek

Darin Wright wrote:

 > Darin,
 >
 > Thanks for your quick reply.
 >
 > Am am writing the plugin for an embedded system. This system has some
 > hardware registers (for peripherals) in the processors memory map.

These

 > can be viewed using a Memory view, but this is very clunky.
 >
 > Typically, each peripheral will have a small number of memory-mapped
 > registers (<16), they may not be contiguous in the memory map, they

may

 > be 8-, 16- or 32-bits wide and very often they consist of separate
 > bit-fields. Therefore, each peripheral, in effect, needs it own
custom view.
 >
 > None of the current views even comes close...

In 3.2, we added experimental support for 'flexible content'. Basically,
a model can present and drive the update of any hierarchy of elements in
a debug view. However, the presentation (controls - tree/table) remains
as is. We hope to make the 3.2 support public API in 3.3. There was a
tutorial covering this material at EclipseCon 2006 - you can review the
presentation here:
http://eclipsezilla.eclipsecon.org/php/attachment.php?bugid=58.

Hopefully you are familiar with the DSDP project which is aimed at
embedded developers - http://www.eclipse.org/dsdp/

Darin


------------------------------------------------------------------------

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

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


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


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


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

Back to the top