platform-core-home/plan_userexperience.html

Parent Directory Parent Directory | Revision Log Revision Log

Revision 1.3 - (view) (download) (as text)

1 : dj 1.1 <!doctype html public "-//w3c//dtd html 4.0 transitional//en">
2 :     <html>
3 :     <head>
4 :     <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
5 :     <meta name="GENERATOR" content="Microsoft FrontPage 4.0">
6 :     <title>Platform/Core Component Planning Details</title>
7 :     <link rel="stylesheet" href="http://dev.eclipse.org/default_style.css" type="text/css">
8 :     </head>
9 :     <body text="#000000" bgcolor="#FFFFFF">
10 :     &nbsp;
11 :     <table BORDER=0 CELLSPACING=5 CELLPADDING=2 WIDTH="100%" >
12 :     <tr>
13 :     <td ALIGN=LEFT VALIGN=TOP COLSPAN="2" BGCOLOR="#0080C0"><b><font face="Arial,Helvetica"><font color="#FFFFFF">Platform/Core
14 : dj 1.3 Component Planning Details - Improve User Experience</font></font></b></td>
15 : dj 1.1 </tr>
16 :     <tr>
17 :     <td ALIGN=RIGHT VALIGN=TOP WIDTH="2%"><img SRC="Adarrow.gif" BORDER=0 height=16 width=16></td>
18 : dj 1.3 <td WIDTH="98%"><a name="user"></a>
19 : dj 1.1 <p><i>Default Location of Workspace</i> - (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=33976">33976</a>,
20 :     <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=34532">34532</a>)
21 :     Currently if the user doesn't specify the location of their workspace,
22 :     then the default is to place is in a &quot;workspace&quot; directory under
23 :     the Eclipse install directory. (equivalent of using &quot;user.dir&quot;
24 :     java System property) This is very problematic, especially in the cases
25 :     where you have a multi-user system and a single shared installation (like
26 :     Linux) where users don't have write access to the installation directory.
27 :     A better solution would be to use the user's home directory (&quot;user.home&quot;
28 :     java System property) as a default location. This would result in (for
29 : dj 1.3 instance) <i>/usr/home/fred</i> (on Linux) or <i>C:/Documents and Settings/Fred</i>
30 :     (on Windows).</p>
31 :     </td>
32 :     </tr>
33 :     <tr>
34 :     <td ALIGN=RIGHT VALIGN=TOP WIDTH="2%"><img SRC="Adarrow.gif" BORDER=0 height=16 width=16></td>
35 :     <td>
36 : dj 1.2 <p><i><a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-vcm-home/docs/online/team3.0/settings.html">Separation
37 :     of User Settings and Plug-in Metadata</a></i> - (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=36965">36965</a>)
38 : dj 1.1 It is common for users to want to share some settings (like background
39 :     colours and fonts) with all workspaces that they use with a particular
40 :     Eclipse install, while other settings (like compiler settings) should
41 :     be on a per workspace basis. Currently Eclipse all of these settings on
42 :     a per workspace basis and we would like to remove this bundling.</p>
43 : dj 1.3 </td>
44 :     </tr>
45 :     <tr>
46 :     <td ALIGN=RIGHT VALIGN=TOP WIDTH="2%"><img SRC="Adarrow.gif" BORDER=0 height=16 width=16></td>
47 :     <td>
48 : dj 1.1 <p><i>Multiple Workspaces</i> - (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=37681">37681</a>,
49 :     <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=5509">5509</a>)
50 :     Users want to be able to better manage multiple workspace within the Eclipse
51 :     environment. This could either mean coming up with a way to pretty a single
52 :     Eclipse image running with 2 workspaces loaded, switching between multiple
53 :     workspaces within the same session (via File -&gt; Open/Close for instance),
54 : dj 1.3 etc. <i>Need to re-visit this for M5. Potential for some of this work
55 :     to be done in the RCP work.</i></p>
56 :     </td>
57 :     </tr>
58 :     <tr>
59 :     <td ALIGN=RIGHT VALIGN=TOP WIDTH="2%"><img SRC="Adarrow.gif" BORDER=0 height=16 width=16></td>
60 :     <td>
61 : dj 1.1 <p><i>Translation of Executable Messages</i> - (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=35135">35135</a>)
62 :     The messages which are displayed by the Eclipse executable are currently
63 :     not translated. We need to define an external message story for this code,
64 :     as well as the code which is in the startup.jar.</p>
65 : dj 1.3 </td>
66 :     </tr>
67 :     <tr>
68 :     <td ALIGN=RIGHT VALIGN=TOP WIDTH="2%"><img SRC="Adarrow.gif" BORDER=0 height=16 width=16></td>
69 :     <td>
70 : dj 1.1 <p><i>Show User Log File Location</i> - (bug <a href="http://bugs.eclipse.org/bugs/show_bug.cgi?id=33974">33974</a>)
71 :     When there is an error trying to start Eclipse we produce a dialog to
72 :     the user telling them to check their log file but we don't print out the
73 :     exact location of this file. If the user specified the -data command-line
74 :     argument then the location of the file is easy to calculate. Otherwise,
75 :     it is done through Java System properties which is much harder to do in
76 : dj 1.3 C code. </p>
77 :     </td>
78 :     </tr>
79 :     <tr>
80 :     <td ALIGN=RIGHT VALIGN=TOP WIDTH="2%"><img SRC="Adarrow.gif" BORDER=0 height=16 width=16></td>
81 :     <td>
82 :     <p><em>Improve Workspace/File-system Synchronization</em> - (bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=36962">36962</a>)
83 :     Improve workspace synchronization with file system. A file resource in
84 :     the workspace gets out of sync when the underlying file in the file system
85 :     is created, deleted, or rewritten outside of Eclipse. File resources usually
86 :     remains out of sync until the user explicitly hits Refresh. The Eclipse
87 :     Platform should provide ways to keep the in-memory representation in sync
88 :     with the file system; for example, by hooking OS file system callbacks
89 :     where available, and by polling for file system changes in a background
90 :     thread. </p>
91 :    
92 :     <em>Notes:</em> We need to improve the case where people are editing files
93 :     outside of Eclipse and we detect that the files in the user's workspace
94 :     are out of sync with the file system. A good general statement is &quot;it
95 :     is hard to use Eclipse when the files are not in sync&quot;. Currently there
96 :     exists the auto-refresh plug-in which users can download and install. We
97 :     need to look at integrating this into the SDK. There are legal issues for
98 :     this as well as technical issues. First step might be to do a package rename
99 :     and start to include it in the build, with future work including integrating
100 :     it better into the base plug-ins. </p>
101 :     <p></td>
102 :     </tr>
103 :     <tr>
104 :     <td ALIGN=RIGHT VALIGN=TOP WIDTH="2%"><img SRC="Adarrow.gif" BORDER=0 height=16 width=16></td>
105 :     <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>)
106 :     Allow editors to open files outside workspace. A common request is to
107 :     be able to use Eclipse to open a file that is not part of the workspace,
108 :     or perhaps even one on a remote system. In addition, applications would
109 :     like to provide file extension associations so that double-clicking on
110 :     a file in the OS desktop would open the associated Eclipse editor. The
111 :     operations and capabilities available on these "outside of the workspace"
112 :     files would need to be defined. </p> </p>
113 :     <p><em>Notes: </em>Users would like to be able to (for instance) double-click
114 :     on a java file in Windows Explorer and open up Eclipse with that file
115 :     so they can use the JDT/UI Java Editor. What people want: associate files,
116 :     syntax-hightlighting and content assist. We could have a known project
117 :     (e.g. &quot;External Files&quot;) then you would be able to set up a classpath
118 :     and project references for that project so you could get content assist,
119 :     etc.<br>
120 : dj 1.1 </p>
121 : dj 1.3 </p></td></tr>
122 : dj 1.1 </table>
123 :    
124 :     </body>
125 :     </html>