|
In fact there are two types of tasks:
a) Task that are added by predefined tags in the source code. These tasks are provided by the iSphere plug-in. These tasks cannot be marked as "completed". Intentionally the task tags should be removed when the task has been completed.
b) Task that are added by the context menu of the most left column of the LPEX editor. That tasks can be marked as completed. These tasks are provided by Eclipse or an IBM plug-in. I do not know the actual provider.
In order to distinguish between both task types we should call tasks of type a) "LPEX Task" and tasks of type b) just "Task".
"LPEX Tasks" (iSphere) are used to tie tasks to a specific source member whereas "Tasks" (Eclipse or IBM) are used to manage personal tasks. For example, when I look at a source member and I see something that could be improved, I add a "TODO" task tag, so that everybody can see it, when he/she opens the source member. Everybody is encouraged to fix the problem when he/she has time to do it.
"Tasks" are not stored inside a source member but in the workspace and hence do not show up for other developers. These tasks can be used to manage the daily work of a specific developer.
Problem: "Double clicking the task opens the source, but does not take you to the line".
I use RDi 9.1.1.1 and double clicking a task entry twice in the "Tasks" view opens the source member and takes me to the source line. I am not yet sure for 100% but since the LPEX editor is not opened by iSphere (but by Eclipse), I assume that this problem is a problem of the LPEX editor. When the source member is already open, double clicking a task tag once takes me to the source line.
In contrast to task tags, the iSphere plug-in opens the LPEX editor for example from the result view of a source file search. In that case iSphere first opens the LPEX editor and then calls the gotoLine(lineNumber) method. That works fine. I do not know what happens when Eclipse opens the LPEX editor from the tasks view.
Thomas.
-----Ursprüngliche Nachricht-----
Von: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] Im Auftrag von
Vernon Hamberg
Gesendet: Montag, 31. August 2015 16:51
An: Websphere Development Studio Client for iSeries
Betreff: [WDSCI-L] LPEX tasks & iSphere - just looking at this and
some thoughts
Hi
One of the things iSphere has is a Tasks component, which ties in with the Java and other task setup in RDi.
When turned on, it pulls lines with the text '// TODO', for example, and displays them in a Tasks view, from which you can double click the task and open the source it came from.
Seems nice enough - but you can't mark these auto-listed tasks as complete, therefore you can't remove completed ones from the list. This is apparently by design of Eclipse.
I'm wondering just how useful this is - for awhile this morning I thought it was not so good - then I just had the thought that maybe the idea is to remove the tag line from source when the thing is done.
Does that line up with anyone's thoughts here?
Now I do see online that one can add tasks directly from the marker
bar
- you know, that narrow thing on the left that sometimes has warning triangles and breakpoints and all. I've begun to use it a l lot when RDi detects a syntax error, then I see what's going on - pretty cool, IMO.
The tasks entered this way are not written into the source, I see, and they do show up in the Tasks view, with the ability to mark as complete, either by checking the checkbox you now see or using the context menu.
Now this is starting to get interesting, I think - so I'm curious about y'all's experiences with this.
Try it out by right-clicking the marker bar on the left of a source member - I don't think the iSphere stuff has anything to do with that, but Thomas can confirm.
Cheers
Vern
--
This is the Rational Developer for IBM i / Websphere Development
Studio Client for System i & iSeries (WDSCI-L) mailing list To post a
message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/wdsci-l.
--
IMPORTANT NOTICE:
This email is confidential, may be legally privileged, and is for the intended recipient only. Access, disclosure, copying, distribution, or reliance on any of it by anyone else is prohibited and may be a criminal offence. Please delete if obtained in error and email confirmation to the sender.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
