[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
CDT folks,
Access to target memory is a necessary feature for our users. We've been
deploying the platform Memory View ever since we contributed the
Traditional memory rendering. The combination provides a functional memory
view, but the experience is far from ideal for embedded development. In
the 90% case, I don't want to consider memory blocks, renderings, split
panes, pin or synchronized scrolling. I just want to browse memory with
minimal clicks. In reviewing some of the bugs I've filed against the
platform Memory View (214956, 214964, 214963, 215432, 244822, 257838,
257840, 257843, 257845) I've begun to speculate that there might be room
for another view. I've authored a prototype of what I call the "Memory
Browser". It's a lightweight (fewer than 700 line) memory rendering
container with streamlined user interface design.
screen video:
https://bugs.eclipse.org/bugs/attachment.cgi?id=128334 (.mov)
or
https://bugs.eclipse.org/bugs/attachment.cgi?id=128337 (.wmv)
source is attached to the bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=268031
I'm wondering whether others in the community might find this view useful.
Is it something we could maintain and enhance under CDT?
Ted Williams, Wind River