[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [mylar-dev] Task Context Visualization
|
Title: Message
Hi
Eugene,
Yes,
the current provider shows contexts across projects and supports a package view
where the vertical bars represent packages rather than individual classes. The
provider shows the context that is currently selected in the task list and
it will show the context for multiple tasks if you activate several at a
time. Note that currently it is necessary to turn on activation of multiple
tasks in the task list preference page.
Thanks
for pointing out the enhancement request for a horizontal rendering of the bars.
I think this would make the visualisation look less like an
intuitive abstraction of files and lines of code but would make better
use of screen real estate for advanced users.
Thanks
for your comments,
Wesley
Wesley,
Does current data
provider allows to see task context groupped across projects and project
packages (affected by current context and over all)?
I also
found that current rendering is not very efficient from the usage of the
screen estate point of view and there is an enhancement request for visualizer
filled in back in February. https://bugs.eclipse.org/bugs/show_bug.cgi?id=85624
Thanks
Eugene
On 10/25/05, Wesley
Coelho <wes.coelho@xxxxxxxxx> wrote:
I've been working on a visualization for
Mylar contexts and could use some feedback on the UI. The visualization is
implemented as a data provider for the Visualiser view that was created by
the AJDT team. For a given task context, it shows vertical bars representing
classes in the context and horizontal stripes that represent members of
those classes that are interesting. The visualization updates as
you interact with your project, and highlights elements in the context of
each active task according to the highlight color of that task. It is
intended to provide an overview of large task contexts. Here's a
screen shot of the visualization prototype:
We want to determine the right way for
presenting this information given the way people might intend to use it. For
example, if people find it useful to view as they code, the visualization
could appear in a separate view as in the prototype. If the visualization is
used primarily for getting an overview of an existing context before working
on it, then the visualization might appear in an additional tab in the task
editor.
Thanks,
Wesley
Coelho
