Bug 137086 - [project explorer] Add link with editor using logical hierarchy meta model object
Summary: [project explorer] Add link with editor using logical hierarchy meta model ob...
Status: NEW
Alias: None
Product: WTP Java EE Tools
Classification: WebTools
Component: jst.j2ee (show other bugs)
Version: 1.5   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: Future   Edit
Assignee: Kaloyan Raev CLA
QA Contact:
URL:
Whiteboard: GSoC
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2006-04-17 17:06 EDT by John Lanuti CLA
Modified: 2010-01-28 11:42 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John Lanuti CLA 2006-04-17 17:06:14 EDT
Customer explained how it would be nice to have a            
"blue-arrows" Toggle button feature parallel to the current     
"Yellow-arrows" Toggle button feature.Just like "Yellow-Arrows" 
button has the tooltip -- "link open editors with Navigator     
contents" , the "blue-arrows" feature can have the tool-tip     
"Link open editors with current logical hierarchy view item"    
                                                                
That feature will provide the following functionality :         
If the user clicks on an open editor , the focus in the project 
explorer will go back to the logical item in the hierarchy view 
under the Deployment descriptor (in its Sub-tree) rather than   
going to the file on the file-system in the "ejbmodule" -       
subtree  (for eg. clicking EmpLocalhome.java in editor view     
should go to the "EmpLocalHome" logical entity being shown in   
the Deployment descriptor sub-tree. The Current "yellow-arrows" 
feature rather makes the focus go into the "ejb module" folder  
and focuses on the EmpLocalHome.java file itself. )             
                                                                
If the above "blue-arrows" feature is made availalbe the        
developer never has  to leave the Deployment descriptor subtree 
during the entire EJB project development work flow. Currently ,
the "yellow-arrows" feature makes the focus go back into the    
"ejbmodule" folder containing the corresponding .java . In      
situations where the EJB project might contain 100's of EJB's   
inside them, "ejbmodule" might contain 1000's of files          
including the Deploy Code etc. The user then needs to scroll all
the way up to the Deployment Descriptor sub-tree to go          
double-click and open any other logical view item ,say another  
Entity bean component (eg. LocalHome or home interface etc.)    
The customer complained that he ends up clicking on the         
"collapse-all" feature in this case there by losing the whole   
work-flow and then has to go back to the logical hierarchy view 
under the Deployment descriptor sub-tree to find a particular   
ejb component for editing.
Comment 1 Kaloyan Raev CLA 2008-08-07 13:05:45 EDT
This is an interesting suggestion. I'd say that there is a lot of sense in it. 
However, the topic could be even broader: the Deployment Descriptor tree should be integrated in Mylyn's Context. 

I don't thing the team has enough resource to make this for 3.1, but I think this is a good idea for Google Summer of Code topic. 
Comment 2 Kaloyan Raev CLA 2009-03-10 04:47:07 EDT
Kiril will try to propose this enhancement as a GSoC project. 
Comment 3 kiril mitov CLA 2009-03-10 05:07:52 EDT
Proposed 
http://wiki.eclipse.org/Google_Summer_of_Code_2009_Ideas