RE: [ajdt-dev] Overhaul AJDT EventTrace facilities (bug 136132)

["Ron Bodkin" <rbodkin@xxxxxxxxxxxxxx>]

Matt,

Since AJDT is using AspectJ it would be good to have the tracing facility
implemented with some aspects instead of scattered "added to the codebase
using AJLog.log()"

Otherwise having this kind of tool sounds really valuable.

-----Original Message-----
From: ajdt-dev-bounces@xxxxxxxxxxx [mailto:ajdt-dev-bounces@xxxxxxxxxxx] On
Behalf Of Matt Chapman
Sent: Thursday, April 13, 2006 9:31 AM
To: AspectJ Development Tools developer discussions
Subject: [ajdt-dev] Overhaul AJDT EventTrace facilities (bug 136132)

The AJDT Event Trace view is used by developers and experienced users
to help narrow down and diagnose problems. However, the old
implementation has performance and memory usage limitations. The new
version, available in the latest 1.4 dev builds, aims to address this
and also improve the usefulness of the view. It works as follows:
   - tracing is disabled by default
   - it is only active when the Event Trace view is open
   - debug strings are only stored in the view - clear or close the
view, and the strings become available for GC
   - trace statements are grouped by category, and colour-coded to
distinguish them
   - the categories to be traced can be selected via the filter button
on the view 
   - the default ones provide similar output to before, with
additional categories available (and scope for more in the future)
   - trace statements are added to the codebase using AJLog.log()

Let me know if you think the view should behave differently, or offer
any additional capabilities.

Regards,

Matt.
_______________________________________________
ajdt-dev mailing list
ajdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ajdt-dev