Hi Praveen,
1)
We don’t have an extension point for this, so you would
either need to contribute that, or add a listener that would prevent the action
from happening (e.g., by listening to the pre-activation event). Either
way, this will be a sensitive enough part of the code that I highly recommend
you contribute a test case to Mylyn which exercises the behavior that you’re
depending on, since it will likely work outside of what we intended with the
API.
2)
There are no restrictions in the sorts of views that you can
create overtop of the TaskList. You can use the TaskListView class for
inspiration. However, if you’re doing this on Mylyn 3.0, note that
you are using internals and will want to comment on and vote for the following
bug:
239994: [api] provide access to task list
https://bugs.eclipse.org/bugs/show_bug.cgi?id=239994
In terms of getting these changes into Mylyn 3.1, the best way
to do so is by providing contributions and test cases for your particular requirements.
Cheers,
Mik
--
Mik Kersten
President & CTO, http://tasktop.com/blog
Project Lead, http://eclipse.org/mylyn
From:
mylyn-integrators-bounces@xxxxxxxxxxx
[mailto:mylyn-integrators-bounces@xxxxxxxxxxx] On Behalf Of Praveen
Kumar Subramanian
Sent: Friday, July 25, 2008 11:21 AM
To: mylyn-integrators@xxxxxxxxxxx
Subject: [mylyn-integrators] Question about integrating mylyn
Hi folks,
I am new to Mylyn. We are trying to develop a dashboard plugin. I have a couple
of questions before I can leverage Mylyn functionalities.
1. Can the "activating the task" and "attaching context to a
task" be restricted on tasks from a specific repository type.
2. Right now we have a mylyn connector for our bug repository. When we query
the repository, we see the bug id and headline for each result. I would like to
have the results also in another new view. Also it would be good if I can
specify what columns I need in the new view.
Currently, we are using Mylyn 2.3. Are the above requirements possible with
that version or with 3.0
Thanks,
Praveen