Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 321257 - Double clicking on an error in Problem view opens Java editor as opposed to corresponding TS Editor
Summary: Double clicking on an error in Problem view opens Java editor as opposed to c...
Status: RESOLVED FIXED
Alias: None
Product: Tigerstripe
Classification: Technology
Component: UI (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: 0.5M0   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-29 13:57 EDT by Navid Mehregani CLA
Modified: 2010-09-21 00:53 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Navid Mehregani CLA 2010-07-29 13:57:56 EDT 
Build Identifier: 

If user double clicks on an error in Problems view, the Java editor is displayed for the problematic artifact.  We should display the appropriate TS editor instead and have the error displayed on top of the form.

Reproducible: Always

Steps to Reproduce:
1. Create a new TS Project with an Entity artifact
2. Open Entity editor and type in an invalid name under 'Extends' field. 
3. Save the file.  There should be an error displayed for the Entity file.
4. Collapse everything in TS Explorer and close all editors
5. Open Problems view > Double click on error > Notice that this opens the artifact in Java editor.  We should open the corresponding Entity editor instead.  The error should be displayed on top of the form.  User should also be given a hint on how they can resolve the issue.
Comment 1 Navid Mehregani CLA 2010-09-21 00:51:08 EDT 
Finally nailed this down.  Double clicking on a marker in Problems view now opens the correct TS editor.  Also, user can now right click on any artifact and open it in its corresponding editor.  

Here are the changes:

Modified Files:
org.eclipse.tigerstripe.workbench.internal.core.model:
AssociationArtifact
AssociationClassArtifact
DatatypeArtifact
DependencyArtifact
EnumArtifact
EventArtifact
ExceptionArtifact
Literal
ManagedEntittyArtifact
Method
PackageArtifact
QueryArtifact
SessionFacadeArtifact
UpdateProcedureArtifact

org.eclipse.tigerstripe.workbench.base
MANIFEST.MF
plugin.xml

org.eclipse.tigerstripe.workbench.ui
EclipsePlugin

org.eclipse.tigerstripe.workbench.ui.internal.editors.artifacts
ArtifactEditorBase
ArtifactOverviewPage

org.eclipse.tigerstripe.workbench.ui.internal.views.explorerview
TSExplorerUtils

org.eclipse.tigerstripe.workbench.ui.base
plugin.xml

New Files:
AbstractContentDescriber.java		
EventContentDescriber.java
AssociationClassContentDescriber.java	
ExceptionContentDescriber.java
AssociationContentDescriber.java	
PackageContentDescriber.java
DataTypeContentDescriber.java		
QueryContentDescriber.java
DependencyContentDescriber.java		
SessionContentDescriber.java
EntityContentDescriber.java		
UpdateContentDescriber.java
EnumContentDescriber.java
Comment 2 Navid Mehregani CLA 2010-09-21 00:53:31 EDT 
Another major change is the error message that's now displayed in the header of TS editor.  This is integrated with Tigerstripe's build, and will update automatically as soon as a new build is completed.