Hi Pawel ,
Thanks for your crystal clear answers
which ensures that I could move ahead confidently.
Regards,
Rejeesh.
From: cdt-dev-bounces@xxxxxxxxxxx
[mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Pawel Piech
Sent: Friday, June 03, 2011 9:35 AM
To: cdt-dev@xxxxxxxxxxx
Subject: Re: [cdt-dev] DSF Table View for Embedded Debugging.
On 05/27/2011 05:21 AM, Rejeesh S. Babu wrote:
Hi Powel,
Thanks for updating me on the
latest developments and progresses happening with DSF-GDB.
Going through your comments, I
get the impression that I should move on to flexible
hierarchy viewer for table view as well. Till date, I assume that
flexible hierarchy viewer was implemented for
Tree Viewer alone and by some work around (Tree nodes with no children,
but with attributes will do) , we could implement table view as well. Could you
please comment on this?
I'm
not sure about your particular need, but in general yes, pretty much all
debugger views use the flexible hierarchy viewer. The flexible hierarchy
viewer with no children does look exactly like a table (it's a table-tree view)
so there's not much difference there.
Now sticking on to my
method(Slow/Lazy content provider),is there any disadvantage if I continue
following the white paper and use the examples you dug out for me? By
disadvantages, I mean any performance hindrance or any API usage
issues(deprecations) in future CDT (CDT 8.0) releases?
No,
there's no disatvantage in writing your own table viewer except that it's more
work. The flexible hierarchy viewer has been extended to support all
kinds of features, but it really depends on your need. There actually is
a tutorial that was written after the white paper, which is probably more
helpful as an introduction: http://www.eclipsecon.org/2008/?page=sub/&id=43.
P.S: Of the two basic patterns
in Coalescing, what exactly I need is local
cache. i.e. my debugger back end provides an interface for
retrieving data in large chunks ONLY. So when the service
implementation receives a request for a single item, I want to retrieve whole
chunk of data, return the single item, and stores the rest of the data in a
local cache.\
I
suggest you look at cache implentations GDB integration, specifically the
memory service. I also started experimenting with new cache
implementations last year but I didn't get to the point where I could apply
them. See org.eclipse.dsf.concurrent: ICache, AbstractCache, RangeCache.
Cheers,
Pawel
Regards,
Rejeesh.
Hi Rejeesh,
It's interesting to look back at this original white paper and see how things
turned out :-) Coalescing of data requests is one of the optimizations in
the system which did not get implemented in DSF-GDB, because it wasn't needed
to achieve the desired performance. So when writing the examples that are
now in org.eclipse.cdt.examples.dsf, we didn't bother with it.
There are other kinds of coalescing still being used, specifically the platform
flexible hierarchy viewer coalesces requests before issuing them, and the DSF
viewer integration coalesces events from the model to avoid overwhelming the UI
with resume/suspended events.
Still I dug up the code you're looking for, it is in dev.eclipse.org:/cvsroot/dsdp/org.eclipse.dd.archive/0.9/plugins/org.eclipse.dd.dsf.examples/src/org/eclipse/dd/dsf/examples/concurrent.
Cheers,
Pawel
On 05/25/2011 11:48 PM, Rejeesh S. Babu wrote:
Hi Pawel,
I am following Debugger Services Framework (DSF) White
Paper Version 1.0 to design a table view
for embedded debugging based on DSF.
Though this white paper was written way back in 2006,I still
expect this document to be a solid reference for embedded UI design in DSF.
I could successfully develop the view using DSF concurrency
model(Slow/Lazy content provider),however, Coalescing
feature could not be implemented in this view for the reason that
example(InputCoalescingSlowDataProvider.java)
plug-in links provided in the white paper are no more available in website.
I hope the reason for this is the fact that all DSF plug-ins
were moved from DSDP/DD project and into CDT.
Could you please guide me to
exact link of the example plug-ins mentioned in the white paper or could you
please circulate (if any) latest version of this paper?
P.S: Currently, I am porting AsyncDataViewer.java
available with org.eclipse.cdt.examples.dsf plugin, found in the /cvsroot/tools
CVS repository under the org.eclipse.cdt/dsf directory.
Thanking in Anticipation,
Regards,
Rejeesh
*****
Confidentiality Statement/Disclaimer *****
This message and any attachments is intended for the sole use of the intended
recipient. It may contain confidential information. Any unauthorized use,
dissemination or modification is strictly prohibited. If you are not the
intended recipient, please notify the sender immediately then delete it from
all your systems, and do not copy, use or print. Internet communications are
not secure and it is the responsibility of the recipient to make sure that it
is virus/malicious code exempt.
The company/sender cannot be responsible for any unauthorized alterations or
modifications made to the contents. If you require any form of confirmation of
the contents, please contact the company/sender. The company/sender is not
liable for any errors or omissions in the content of this message.
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
*****
Confidentiality Statement/Disclaimer *****
This message and any attachments is intended for the sole use of the intended
recipient. It may contain confidential information. Any unauthorized use,
dissemination or modification is strictly prohibited. If you are not the
intended recipient, please notify the sender immediately then delete it from
all your systems, and do not copy, use or print. Internet communications are
not secure and it is the responsibility of the recipient to make sure that it
is virus/malicious code exempt.
The company/sender cannot be responsible for any unauthorized alterations or
modifications made to the contents. If you require any form of confirmation of
the contents, please contact the company/sender. The company/sender is not
liable for any errors or omissions in the content of this message.
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev