From: Sami Wagiaalla <swagiaal@redhat.com>
To: frysk <frysk@sources.redhat.com>
Subject: EventViewer Rewrite
Date: Wed, 18 Oct 2006 21:14:00 -0000 [thread overview]
Message-ID: <45369937.30703@redhat.com> (raw)
As some of you may know I have been working on a complete
rewrite of the EventViewer widget.
I have committed my changes to the NEW_EVENTVIEWER branch
to check it out:
cvs co -r NEW_EVENTVIEWER frysk
The new EventViewer is not ready to be merged yet but you can take
a look to see the general look and feel.
It is written completely in Java using java-cairo.
It has a sofisticated drawing hiarchy of composing objects to suppor
unlimmited fancyness :).
Events are independent of time lines. They are kept track of by EventManager
to support reuse of objects and on the fly redistribution, filtering,
switching
between modes and whatever we may need in the future.
For example if the user wants to switch from having a time line per thread,
to having one per machine, or even a time line for all events of type X or
shared library Y, etc. This is made easier by EventManager.
Anyhow it should be up to speed and ready to be merged soon. I will aso need
Nurdin's help to put in Accessibility info :)
Happy hacking,
Sami Wagiaalla
next reply other threads:[~2006-10-18 21:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 21:14 Sami Wagiaalla [this message]
2006-11-07 1:46 ` Sami Wagiaalla
2007-01-10 19:17 ` Sami Wagiaalla
2007-01-10 19:35 ` Phil Muldoon
2007-01-10 19:41 ` Mike Cvet
2007-01-10 20:00 ` Sami Wagiaalla
2007-01-10 20:06 ` Mike Cvet
2007-01-10 20:09 ` Phil Muldoon
2007-01-10 20:29 ` Sami Wagiaalla
2007-01-10 19:52 ` Sami Wagiaalla
2007-01-10 22:13 ` Nurdin Premji
2007-01-11 13:25 ` Sami Wagiaalla
2007-01-11 13:38 ` Phil Muldoon
2007-01-10 22:20 ` Nurdin Premji
2007-01-10 22:27 ` Nickolay V. Shmyrev
2007-01-11 13:43 ` Sami Wagiaalla
2007-01-11 14:18 ` Sami Wagiaalla
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45369937.30703@redhat.com \
--to=swagiaal@redhat.com \
--cc=frysk@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).