Re: [platform-debug-dev] extending VariablesView?

[Derek Morris <dmsubs@xxxxxxxxxxxxx>]

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...

Thanks
---
Derek

Darin Wright wrote:
> Hello,
>
> The debug views are internal and subject to change :-) They are 
> extensible in that you can contribute your own actions to the views via 
> regular workbench extension points. Generally, we hope/intend other 
> debug implementations to re-use the existing views. So we'd like to know 
> why you need your own views, and why the platform views are not sufficient.
>
>  >
>  > I am writing a plugin that contains a new debug view. The plugin is
>  > primarily for use with CDT.
>  >
>  > Having looked around the Callisto sources, it looks like extending
>  > VariablesView would be the way to go as it provides almost everything I
>  > need (except for my own unique functionality), but it is an internal API
>  > (so liable to change). I see the RegisterView and ExpressionView both
>  > extend it, but they are also internal. And it appears they are hardwired
>  > into the source (as opposed to plugin.xml style and so not suitable for
>  > a plugin).
>  >
>  > Is extending VariablesView the way to go (with associated risk of
>  > change)? If so, how do I plug it in?
>  >
>  > If not, what is the best way to write a debug view? I was hoping to
>  > avoid re-inventing the wheel (of VariablesView)...
>
> Darin
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> platform-debug-dev mailing list
> platform-debug-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/platform-debug-dev