Description Douglas Pollock 2005-10-03 11:52:36 EDT

It would be nice if the import/export dialog suggested items based on the 
context from which it is coming.  I'll list some examples. 
 
+ An export button on the preference dialog.  This should lead directly to the 
export preference wizard. 
 
+ An export button on the preference dialog, with the keys preference page 
showing.  This should lead directly to the export preference wizard with the 
keys preference export filter selected. 
 
+ Right-clicking on a plug-in project and selecting export.  This should open 
the export tab on the dialog, and display the following items at the top of 
the list as "suggestions": "Archive File" and "Deployable plug-ins and 
fragments".  It might also suggest "File System".  If the plug-in project is a 
Java project, it might also suggest "JAR file".  If it contains a ".product" 
file, then it might also suggest "Eclipse product". 
 
+ Selecting "Import" will offer to prompt the user immediately for the file to 
import.  If there is a single selection from the selection service, then it 
will automatically file this in.  The selected file will drive the list of 
suggestions.  For example, selecting a ".epf" file will suggest a preference 
import, and selecting a ".bkpt" file will suggest a breakpoint import. 
 
+ Selecting a ".product" file and selecting "export" would suggest "Eclipse 
product". 
 
 
I'm pretty sure other clear suggestions would arise in downstream plugins.  
Basically, every file type and project nature could potentially lead to a 
suggestion.  I also think that there might be other "hooks", similar to the 
preference dialog, which would lead to clear suggestions.  MVM suggested 
right-clicking within a plugin.xml file.  Perhaps also an "Export..." option 
in the "Breakpoints" view. 
 
 
The rationale behind this enhancement request is simply that our import/export 
dialog is getting more and more complex with every release.  To do a simple 
export, we are requiring more and more user steps.  However, export is an 
infrequent event.  It is not something that the average user will be an expert 
at doing, as they only do it every once in a while.  They will not necessarily 
remember what the page is called for the task at hand.