AW: [cdt-dev] bug #151005 - Error parser - cannot generatepropermarker f

["Ploett, Norbert" <norbert.ploett@xxxxxxxxxxx>]

Dobrin,

> Did you try to get an advice from the owner of the Problem View -

I have, now. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=155379 and join the discussion !


Norbert 

-----Ursprüngliche Nachricht-----
Von: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] Im Auftrag von Alexiev, Dobrin
Gesendet: Mittwoch, 23. August 2006 15:51
An: CDT General developers list.
Betreff: RE: [cdt-dev] bug #151005 - Error parser - cannot generatepropermarker for file outside of the workspace

Hi Norbert, 

Did you try to get an advice from the owner of the Problem View -
posting a message, filing an enhancement request? The functionality may
already be there or planned to go anytime soon. 

>From your e-mail "...double-click is hard-coded into the ProblemView..."
looks like something should be done at the framework level to enable the
functionally you need. 

I believe that close to zero works should be done in CDT to support
that. Opening an external file from a problem view is a common task and
it is not specific to CDT.  It should be handled at the Eclipse GUI
itself. Otherwise each tool on top on Eclipse will have its own
solution. That will be inconsistent. 

Regards
Dobrin

-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Ploett, Norbert
Sent: Wednesday, August 23, 2006 8:36 AM
To: CDT General developers list.
Subject: [cdt-dev] bug #151005 - Error parser - cannot generate
propermarker for file outside of the workspace

Hi all,
 
"innovative ideas" are called for to resolve
https://bugs.eclipse.org/bugs/show_bug.cgi?id=151005 (see there for an
introduction into the problem)
 
Well, here is one:
 
- If the error parser cannot create an IFile object for a given path
then it
attaches the problem marker to the project. That's why the file cannot
be
opened in a simple way from the problems view
- A new marker type could be defined which has an additional attribute
like
"externalLocation" (derived from the standard C/C++ problem marker)
- The error parser could be made to use the the new type, still use the
project
as resource but store the original path of the error in the marker's
externalLocation attribute
- An popup menu object contribution for the new marker type could be
created,
as an analogy of the Delete C/C++ Marker contribution which allows
manually
deleting C/C++ Markers. The new contribution would say: "Open External
File".
An action would be provided to open the external file in an editor and
place
the cursor in the appropriate position.

The main drawback of this is the fact that the user must know or guess
that
while double-clicking does not work, he can still get the file opened
via a
popup menu action. I would have liked to somehow override the default
double-click action for the Problems view but I could not figure out how
to do
this. The current action which is caused by the double-click is
hard-coded into
the ProblemView class and it's framework

Another drawback is that annotiations probably also won't work for the
external
file. I'll have to think about this some more, maybe we can configure
the
CEditors annotation access ...

Anyway I would like opinions on whether this is worth doing in spite of
the
drawbacks, or whether other, more elegant ways of doing this can be
imagined.

 
Thanks,
 
 
Norbert Ploett
 
 
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev