platform-core-home/documents/3.1/large_scale_issues.html

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.6, Thu Jan 6 15:10:08 2005 UTC revision 1.7, Fri Jan 14 19:17:09 2005 UTC
# Line 9  Line 9 
9  <table width="100%">  <table width="100%">
10  <tr><td style="background:#0080C0"><b><span style="color:white">Large-scale development issues</span></b></td></tr>  <tr><td style="background:#0080C0"><b><span style="color:white">Large-scale development issues</span></b></td></tr>
11  </table>  </table>
12  <font size="-1">Last modified: January 5, 2005</font>  <font size="-1">Last modified: January 14, 2005</font>
13  <p>  <p>
14  One of the major development themes for Eclipse 3.1 is to improve support for  One of the major development themes for Eclipse 3.1 is to improve support for
15  "Large-scale development" in Eclipse. This includes improving collaboration for  "Large-scale development" in Eclipse. This includes improving collaboration for
# Line 44  Line 44 
44          in memory about the synchronization and "dirty" state of each resource. Explore          in memory about the synchronization and "dirty" state of each resource. Explore
45          reducing the footprint of this data or using lazy caching to only bring this information          reducing the footprint of this data or using lazy caching to only bring this information
46          into memory when needed.          into memory when needed.
47  <li><img src="../../images/glass.gif"  height="10" width="10" border="0">  <li><img src="../../images/progress.gif" height="5" width="14" border="0">
48          Message bundles. Most plug-ins store translated strings in <tt>ResourceBundle</tt>          Message bundles. Most plug-ins store translated strings in <tt>ResourceBundle</tt>
49          objects.  These bundles are not space-efficient, and often use lengthy string-based          objects.  These bundles are not space-efficient, and often use lengthy string-based
50          keys for message lookup.  Explore a more efficient representation, integer-based keys,          keys for message lookup.  Explore a more efficient representation, integer-based keys,
# Line 119  Line 119 
119  </ul>  </ul>
120  </p>  </p>
121  <h3>4. Support for non-incremental builders</h3>  <h3>4. Support for non-incremental builders</h3>
122  <p><img src="../../images/glass.gif"  height="10" width="10" border="0">  <p><img src="../../images/ok.gif"  height="10" width="10" border="0">
123          The workspace builder infrastructure is designed primarily with efficient          The workspace builder infrastructure is designed primarily with efficient
124          incremental compilers in mind.  Auto-build is turned on by default, and this          incremental compilers in mind.  Auto-build is turned on by default, and this
125          is only realistic for fast builders.  The workspace should have support          is only realistic for fast builders.  The workspace should have support
Legend:
Removed from v.1.6  
changed lines
  Added in v.1.7