Re: LPEX tasks & iSphere - just looking at this and some thoughts

Vern,

Unfortunately I cannot debug the problem, because I do not have the
source code of the IBM LPEX editor.

I am pretty sure, that the Eclipse framework calls the gotoMarker()
method of the LPEX editor after having opened the editor. But I do not
know what happens, then. Basically gotoMarker() should work fine,
because the second double-click takes me to the source line. But I
cannot figure out why it does not work for the first double-click.

Thomas.

Am 01.09.2015 um 14:15 schrieb Vernon Hamberg:

Hi Thomas

Thanks for your response - I had hoped that my question would open a
conversation, and it has. The distinction you make between 2 kinds of
tasks is helpful.

I want to be sure you mean what you say below, where you say "I use RDi
9.1.1.1..." and you say "...double-clicking a task entry twice..." - do
you mean double-clicking or (heh) quadruple-clicking? You also say it
DOES position you to the line, yet you say it is a problem - did you
mean to says it does NOT position you?

At any rate, you should know that I'm using iSphere a lot and recommend
it to whomever I can, both in our company and out of it.

Regards
Vern

On 9/1/2015 5:55 AM, Thomas Raddatz wrote:

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-Zwy7GipZuJhWk0Htik3J/w@xxxxxxxxxxxxxxxx] 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-Zwy7GipZuJhWk0Htik3J/w@xxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request-Zwy7GipZuJhWk0Htik3J/w@xxxxxxxxxxxxxxxx
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.