| <!doctype html public "-//w3c//dtd html 4.0 transitional//en"> |
| <html> |
| <head> |
| <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> |
| <meta name="GENERATOR" content="Microsoft FrontPage 4.0"> |
| <title>Platform/Core Component Planning Details</title> |
| <link rel="stylesheet" href="http://dev.eclipse.org/default_style.css" type="text/css"> |
| </head> |
| <body text="#000000" bgcolor="#FFFFFF"> |
| |
| <table BORDER=0 CELLSPACING=5 CELLPADDING=2 WIDTH="100%" > |
| <tr> |
| <td ALIGN=LEFT VALIGN=TOP COLSPAN="2" BGCOLOR="#0080C0"><b><font face="Arial,Helvetica"><font color="#FFFFFF">Platform/Core |
| Component Planning Details - Improve User Experience</font></font></b></td> |
| </tr> |
| <tr> |
| <td ALIGN=RIGHT VALIGN=TOP WIDTH="2%"><img SRC="../../images/Adarrow.gif" BORDER=0 height=16 width=16></td> |
| <td WIDTH="98%"><a name="user"></a> |
| <p><i>Default Location of Workspace</i> - (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=33976">33976</a>, |
| <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=34532">34532</a>) |
| Currently if the user doesn't specify the location of their workspace, |
| then the default is to place is in a "workspace" directory under |
| the Eclipse install directory. (equivalent of using "user.dir" |
| java System property) This is very problematic, especially in the cases |
| where you have a multi-user system and a single shared installation (like |
| Linux) where users don't have write access to the installation directory. |
| A better solution would be to use the user's home directory ("user.home" |
| java System property) as a default location. This would result in (for |
| instance) <i>/usr/home/fred</i> (on Linux) or <i>C:/Documents and Settings/Fred</i> |
| (on Windows).</p> |
| </td> |
| </tr> |
| <tr> |
| <td ALIGN=RIGHT VALIGN=TOP WIDTH="2%"><img SRC="../../images/Adarrow.gif" BORDER=0 height=16 width=16></td> |
| <td> |
| <p><i><a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-vcm-home/docs/online/team3.0/settings.html">Separation |
| of User Settings and Plug-in Metadata</a></i> - (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=36965">36965</a>) |
| It is common for users to want to share some settings (like background |
| colours and fonts) with all workspaces that they use with a particular |
| Eclipse install, while other settings (like compiler settings) should |
| be on a per workspace basis. Currently Eclipse all of these settings on |
| a per workspace basis and we would like to remove this bundling.</p> |
| </td> |
| </tr> |
| <tr> |
| <td ALIGN=RIGHT VALIGN=TOP WIDTH="2%"><img SRC="../../images/Adarrow.gif" BORDER=0 height=16 width=16></td> |
| <td> |
| <p><i>Multiple Workspaces</i> - (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=37681">37681</a>, |
| <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=5509">5509</a>) |
| Users want to be able to better manage multiple workspace within the Eclipse |
| environment. This could either mean coming up with a way to pretty a single |
| Eclipse image running with 2 workspaces loaded, switching between multiple |
| workspaces within the same session (via File -> Open/Close for instance), |
| etc. <i>Need to re-visit this for M5. Potential for some of this work |
| to be done in the RCP work.</i></p> |
| </td> |
| </tr> |
| <tr> |
| <td ALIGN=RIGHT VALIGN=TOP WIDTH="2%"><img SRC="../../images/Adarrow.gif" BORDER=0 height=16 width=16></td> |
| <td> |
| <p><i>Translation of Executable Messages</i> - (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=35135">35135</a>) |
| The messages which are displayed by the Eclipse executable are currently |
| not translated. We need to define an external message story for this code, |
| as well as the code which is in the startup.jar.</p> |
| </td> |
| </tr> |
| <tr> |
| <td ALIGN=RIGHT VALIGN=TOP WIDTH="2%"><img SRC="../../images/Adarrow.gif" BORDER=0 height=16 width=16></td> |
| <td> |
| <p><i>Show User Log File Location</i> - (bug <a href="http://bugs.eclipse.org/bugs/show_bug.cgi?id=33974">33974</a>) |
| When there is an error trying to start Eclipse we produce a dialog to |
| the user telling them to check their log file but we don't print out the |
| exact location of this file. If the user specified the -data command-line |
| argument then the location of the file is easy to calculate. Otherwise, |
| it is done through Java System properties which is much harder to do in |
| C code. </p> |
| </td> |
| </tr> |
| <tr> |
| <td ALIGN=RIGHT VALIGN=TOP WIDTH="2%"><img SRC="../../images/Adarrow.gif" BORDER=0 height=16 width=16></td> |
| <td> |
| <p><em>Improve Workspace/File-system Synchronization</em> - (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=36962">36962</a>) |
| Improve workspace synchronization with file system. A file resource in |
| the workspace gets out of sync when the underlying file in the file system |
| is created, deleted, or rewritten outside of Eclipse. File resources usually |
| remains out of sync until the user explicitly hits Refresh. The Eclipse |
| Platform should provide ways to keep the in-memory representation in sync |
| with the file system; for example, by hooking OS file system callbacks |
| where available, and by polling for file system changes in a background |
| thread. </p> |
| |
| <em>Notes:</em> We need to improve the case where people are editing files |
| outside of Eclipse and we detect that the files in the user's workspace |
| are out of sync with the file system. A good general statement is "it |
| is hard to use Eclipse when the files are not in sync". Currently there |
| exists the auto-refresh plug-in which users can download and install. We |
| need to look at integrating this into the SDK. There are legal issues for |
| this as well as technical issues. First step might be to do a package rename |
| and start to include it in the build, with future work including integrating |
| it better into the base plug-ins. </p> |
| <p></td> |
| </tr> |
| <tr> |
| <td ALIGN=RIGHT VALIGN=TOP WIDTH="2%"><img SRC="../../images/Adarrow.gif" BORDER=0 height=16 width=16></td> |
| <td><p><em>Editing files outside of the workspace </em>- (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=37935">37935</a>) |
| Allow editors to open files outside workspace. A common request is to |
| be able to use Eclipse to open a file that is not part of the workspace, |
| or perhaps even one on a remote system. In addition, applications would |
| like to provide file extension associations so that double-clicking on |
| a file in the OS desktop would open the associated Eclipse editor. The |
| operations and capabilities available on these "outside of the workspace" |
| files would need to be defined. </p> </p> |
| <p><em>Notes: </em>Users would like to be able to (for instance) double-click |
| on a java file in Windows Explorer and open up Eclipse with that file |
| so they can use the JDT/UI Java Editor. What people want: associate files, |
| syntax-hightlighting and content assist. We could have a known project |
| (e.g. "External Files") then you would be able to set up a classpath |
| and project references for that project so you could get content assist, |
| etc.<br> |
| </p> |
| </p></td></tr> |
| </table> |
| |
| </body> |
| </html> |
