Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between pages "Callisto Coordinated Update Sites" and "Polish3.2"

(Difference between pages)
(→‎Project Responsibilities -- edited to update project responsibiliies)
 
 
Line 1: Line 1:
−
== Purpose of this document ==
+
<h1>3.2 Polish Items<br>
 +
</h1>
 +
<p><small><i>Last update: March 15, 2006 (Changes since March 13, 2006 in <font
 +
  color="#33cc00"><b>green</b></font>. New entries in Team and JDT UI)</i><br>
 +
  </small></p>
 +
<p><font color="#00FF00"><strong><em>New additions in green.</em></strong></font></p>
 +
<p><small><font color="#FF0000"><strong>Entries in RED have been fixed.</strong></font></small></p>
 +
<p><strong><font color="#0000FF">Entries in BLUE are not in the plan for 3.2</font></strong></p>
 +
<p><small><br>
 +
  </small> So far, I have received input from the Search, Platform/JDT Text, JDT
 +
  Core, JDT UI, and Debug teams. This document contains a summary of that feedback.
 +
  The items are listed by component, but are otherwise in no particular order.
 +
  <br>
 +
</p>
 +
<h2>General / All</h2>
 +
<table border="1" cellpadding="2" cellspacing="2" width="100%">
 +
 
 +
    <tr>
 +
      <th width="10%">Bugzilla</th>
 +
      <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
      <td align="right" width="10%"></td>
 +
      <td>Do we need a new splash screen? <em><strong><font color="#00FF00">MVM asking designers to investigate in light of new welcome as well.</font></strong></em></td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right" width="10%"></td>
 +
      <td>Update keywords for searching preference pages. I.e. verify that all the new preferences are covered.</td>
 +
    </tr>
 +
</table>
 +
<br>
 +
<h2>Platform Runtime</h2>
 +
<table border="1" cellpadding="2" cellspacing="2" width="100%">
 +
    <tr>
 +
      <th width="10%">Bugzilla</th>
 +
      <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
      <td align="right">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=128178 128178]</td>
 +
      <td>[Workbench] earlyStartup does not work in runtime eclipse with binary-imported plugins</td>
 +
    </tr>
 +
</table>
  
−
This page is to document processes and procedures for providing improved coordination of update sites provided by the many Eclipse Projects. It's focus is on the 10 or so projects as part of the
+
<h2>Platform Compare</h2>
−
[http://www.eclipse.org/projects/callisto.php Callisto simultaneous release] but some of the information would be helpful to any Eclipse adopter.
+
<table border="1" cellpadding="2" cellspacing="2" width="100%">
 +
    <tr>
 +
      <th width="10%">Bugzilla</th>
 +
      <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
      <td align="right" width="10%">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=78063 78063]</td>
 +
      <td>Full Javadoc line selected even though only a character has been added to a word</td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right" width="10%">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=68758 68758]
 +
      </td>
 +
      <td>Structured Compare: selected added element not part of selection</td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=128362 128362]</td>
 +
      <td>[Patch] Creating patch from compare in between versions/revisions</td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=118021 118021]</td>
 +
      <td>Structured compare not available with additions or deletions</td>
 +
    </tr>
 +
    <tr>
 +
      <td><p> [https://bugs.eclipse.org/bugs/show_bug.cgi?id=112661 <font color="#00FF00">112661</font>]
 +
          (bugs logged by mvm previously)</p>
 +
        <p><font color="#00FF00"> [https://bugs.eclipse.org/bugs/show_bug.cgi?id=132693 132693]</font></p></td>
 +
      <td>Cleanup UI of Create/Apply Patch wizards (follow Eclipse UI guidelines):<br>
 +
      <ul>
 +
        <li>button sizes</li>
 +
        <li>caption</li>
 +
        <li>margins</li>
 +
        <li>mnemonics (missing)</li>
 +
        <li>polish all descriptions and messages</li>
 +
        <li>Match Project... button launches dialog called Retarget
 +
        Patch (inconsistent)</li>
 +
      </ul>
 +
      </td>
 +
    </tr>
 +
 
 +
</table>
 +
<br>
 +
<ul></ul>
 +
<h2>Platform CVS</h2>
 +
<table border="1" cellpadding="2" cellspacing="2" width="100%">
 +
    <tr>
 +
      <th width="10%">Bugzilla</th>
 +
      <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
      <td align="right" width="10%"><strong><font color="#FF0000">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=112927 112927]</font></strong></td>
 +
      <td><strong><font color="#FF0000">[performance] Update CVS workspace job takes too long</font></strong></td>
 +
    </tr>
 +
    <tr>
 +
      <td></td>
 +
      <td>See also " [#too_may_password">too many passwords]" in the Platform UI section below.</td>
 +
    </tr>
 +
</table>
 +
<br>
 +
<h2>Platform Help</h2>
 +
<table border="1" cellpadding="2" cellspacing="2" width="100%">
 +
    <tr>
 +
      <th width="10%">Bugzilla</th>
 +
      <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
      <td align="right" width="10%"></td>
 +
      <td>New help support should be improved (2 votes):<br>
 +
      <ul>
 +
        <li>Help button should be on the side where the help shows up. Should stay pushed, and a release should close the help view again</li>
 +
        <li>dialogs without help should better not get the help button</li>
 +
        <li>clicking on a link should directly open the help browser as the space next to the dialog is always too small</li>
 +
      </ul>
 +
      </td>
 +
    </tr>
 +
 
 +
</table>
 +
<br>
 +
<h2>Platform SWT</h2>
 +
<table border="1" cellpadding="2" cellspacing="2" width="100%">
 +
    <tr>
 +
      <th width="10%">Bugzilla</th>
 +
      <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
      <td align="right" width="10%">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=95634 95634]</td>
 +
      <td>[Tree] TreeColumn does not show "..." on cut-off Text and misses tooltips</td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right" width="10%"></td>
 +
      <td>I know I'm dreaming, but: styled ranges inside a tree item (Font/colors etc for e.g. a word inside the full label) would be a boost</td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right"> [https://bugs.eclipse.org/bugs/show_bug.cgi?id=125702 125702]</td>
 +
      <td><font color="#000000">If you collapse a tree on a recent version of GTK+, a big block of whitespace appears at the bottom. It's very irritating.</font></td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right"><p> [https://bugs.eclipse.org/bugs/show_bug.cgi?id=123425 123425]</p>
 +
        <p> [https://bugs.freedesktop.org/show_bug.cgi?id=5200 5200]</p></td>
 +
      <td><font color="#000000">There's also the &quot;festival of carets&quot; bug. This is immediately noticeable to        anyone using a recent GTK+, and it makes us look bad. Unfortunately, it appears to be a bug somewhere in the Cairo/Pango/glib/GTK+ stack specific to the FPU mode (which the Java VM modifies on start-up). This bug is bad and will be hard to track down. We need to do work if we want to see this fixed; we can't just say &quot;It's their problem&quot;.</font></td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right"></td>
 +
      <td>&nbsp;</td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right"></td>
 +
      <td>&nbsp;</td>
 +
    </tr>
 +
 
 +
</table>
 +
<br>
 +
<h2>Platform Team</h2>
 +
<table border="1" cellpadding="2" cellspacing="2" width="100%">
 +
 
 +
    <tr>
 +
      <th width="10%">Bugzilla</th>
 +
      <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
      <td></td>
 +
      <td>Need a general polish pass on new History view filtering and user interactions. The bugs below are examples...</td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right" width="10%">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=125860 125860]</td>
 +
      <td><font color="#FF0000"><strong>New history view: filter is not persisted - no way to constantly ignore local history</strong></font></td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right" width="10%">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=129916 129916]</td>
 +
      <td><font color="#FF0000"><strong>Per date sorting in History view forced on me upon ever input change</strong></font></td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right">&nbsp;</td>
 +
      <td><p><font color="#00FF00"><strong>MOVED FROM UI</strong></font></p>
 +
        <p>There are sometimes <a name="too_may_password">]too many password dialogs:<br>
 +
        </p>
 +
        <ul>
 +
          <li>If I'm trying to work off-line but have CVS projects in workspace, it can happen that you get lots of dialogs to ask for the password as the CVS decorators each need that password. Clicking cancel once should be enough to let them know that I'm not interested in entering the password now.</li>
 +
          <li>It would be nice to have a less intrusive way of asking for passwords. Idea is e.g. a status line icon similar to the progress view that blinks when a passwords are pending. Clicking on this icon brings a 'authentication view' that shows that status of all passwords: passed, failed, canceled, and lets me trying to connect again.</li>
 +
        </ul></td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=130408 130408]</td>
 +
      <td><font color="#FF0000"><strong>Should be able to export psfs to the workspace
 +
        (2 votes)</strong></font></td>
 +
    </tr>
 +
 
 +
</table>
 +
<br>
 +
<h2>Platform Text</h2>
 +
<table border="1" cellpadding="2" cellspacing="2" width="100%">
 +
 
 +
    <tr>
 +
      <th width="10%">Bugzilla</th>
 +
      <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
      <td align="right" width="10%">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=11624 11624]</td>
 +
      <td><strong><font color="#0000FF">Text Drag and Drop (has many bug votes)</font></strong><br>
 +
      <ul>
 +
        <li>depends on StyledText support ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=106372 NEW - Provide DND support for the StyledText widget 106372]),
 +
        which is now marked as FIXED.</li>
 +
      </ul>
 +
      <p>In order to resolve this we first need to put the grounds for drag and drop contributions
 +
      to editors, otherwise clients contributing some sort of DnD will get broken.
 +
      This is covered in [https://bugs.eclipse.org/bugs/show_bug.cgi?id=125957 bug 125957] and won't make it into 3.2.</p></td>
 +
    </tr>
 +
</table>
 +
<br>
  
−
Note: as of this initial writing, this document should be taken as a 'proposal', and as its reviewed and discussed and improved by others, it will become a 'plan'. And then, eventually, once the plan seems to be
+
<h2>Platform UI</h2>
−
working, it will become a true "process and procedures" document.
+
<table border="1" cellpadding="2" cellspacing="2" width="100%">
 +
 
 +
    <tr>
 +
      <th width="12%">Bugzilla</th>
 +
      <th width="88%">Description</th>
 +
    </tr>
 +
    <tr>
 +
      <td align="right"> [https://bugs.eclipse.org/bugs/show_bug.cgi?id=119890 119890]</td>
 +
      <td> <p><strong><font color="#0000FF">[ViewMgmt] Allow control of view tab compression
 +
          </font></strong></p>
 +
        <p><font color="#000000">- this was changed in 3.2 and need to decide if we like it</font></p></td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right"> [https://bugs.eclipse.org/bugs/show_bug.cgi?id=100993 100993]</td>
 +
      <td><font color="#000000">[EditorMgmt][Presentations] Regression: Editor tabs do not remember order or active tab after restarting Eclipse</font>
 +
      <p><strong><font color="#00FF00">Investigating</font></strong></p></td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right"> [https://bugs.eclipse.org/bugs/show_bug.cgi?id=128455 128455]</td>
 +
      <td> <strong><font color="#FF0000">[Presentation] [ViewBar] Outline view toolbar is visible above a maximized editor</font></strong></td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right"> [https://bugs.eclipse.org/bugs/show_bug.cgi?id=131559 131559]</td>
 +
      <td> <font color="#FF0000"><strong>[Markers] Layout of marker filters dialog</strong></font></td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right"> [https://bugs.eclipse.org/bugs/show_bug.cgi?id=129936 129936]</td>
 +
      <td><strong><font color="#0000FF">[ViewMgmt] View part description label should wrap</font></strong></td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right"> [https://bugs.eclipse.org/bugs/show_bug.cgi?id=125691 125691]</td>
 +
      <td> <font color="#0000FF">[ViewMgmt] Can't read view titles</font></td>
 +
    </tr>
 +
    <tr>
 +
      <td height="38" align="right"> [https://bugs.eclipse.org/bugs/show_bug.cgi?id=68684 68684]</td>
 +
      <td><strong><font color="#0000FF"><strong>Remove MRU Ordering from the editors.</strong></font></td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right"> [https://bugs.eclipse.org/bugs/show_bug.cgi?id=113455 113455]</td>
 +
      <td><strong><font color="#FF0000">Some errors do not appear in the Problems view. This happens very frequently for me (multi-processor box, GTK+) if I have grouping turned on.</font></strong></td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right"> [https://bugs.eclipse.org/bugs/show_bug.cgi?id=130818 130818]</td>
 +
      <td><strong><font color="#FF0000">Filters do not seem to apply when grouping by Java type (Problems view).<br>
 +
        </font></strong></td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right">&nbsp;</td>
 +
      <td>&nbsp;</td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right" width="12%">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=126155 126155]</td>
 +
      <td><font color="#FF0000"><strong>[Markers] Issues of multi quick fix dialog</strong></font></td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right" width="12%">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=122639 122639]</td>
 +
      <td>[WorkbenchParts] PageBookView's toolbar doesn't properly re-layout after page switching</td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=128670 128670]</td>
 +
      <td><font color="#FF0000"><strong>[Dialogs] StatusDialog adds 2 horizontal margins around button bar</strong></font></td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=127629 127629]</td>
 +
      <td><font color="#FF0000"><strong>[Markers] problems view: keep selection stable</strong></font></td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=128381 128381], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=128381 128381]</td>
 +
      <td><strong><font color="#FF0000">[Markers] group should only show (10 of 10 items) if beyond the limit</font></strong></td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=129812 129812]</td>
 +
      <td><strong><font color="#FF0000">[Markers] Enabling problem categorization per default</font></strong></td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=129184 129184]</td>
 +
      <td><strong><font color="#FF0000">Progress view should be made more prominent</font></strong></td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=127289 127289]</td>
 +
      <td><strong><font color="#FF0000">[Markers] SystemFilter and group selection
 +
        state not preserved</font></strong></td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right"><strong><font color="#0000FF">see suggestions in bug [https://bugs.eclipse.org/bugs/show_bug.cgi?id=109998 109998]</font></strong></td>
 +
      <td><strong><font color="#0000FF">Experimental (?) Keys preference page (3 votes):<br> <ul>
 +
          <li>what do we do with the two pages?</li>
 +
          <li>sorting by keys, by commands and by scope [https://bugs.eclipse.org/bugs/show_bug.cgi?id=109998 109998]</li>
 +
          <li>see which keys are free and which commands are not used</li>
 +
          <li>Platform UI team is investigating what can/can not be done about this without Doug around</li>
 +
        </ul></font></strong></td>
 +
    </tr>
 +
    <tr>
 +
      <td></td>
 +
      <td>Finish the preferences clean up effort from 3.0:<br>
 +
        <ul>
 +
          <li><strong><font color="#FF0000">decorator preference pages should offer a link to decorators</li>
 +
          <li>font / color preferences should use shared settings so it is also possible to configure the color and font decoration for CVS on the CVS page</font></strong></li>
 +
          <li><strong><font color="#00FF00">UI - please provide a bug for this so we can track polish</font></strong></li>
 +
        </ul></td>
 +
    </tr>
 +
    <tr>
 +
      <td></td>
 +
      <td><strong><font color="#0000FF">Improve the look of the filter control (preferences, other dialogs):<br>
 +
        <ul>
 +
          <li>the text field seems unaligned as long as there is no 'clear' button</li>
 +
          <li>either dump the 'clear' button, or add it as a lay-over over the text field:</li>
 +
          <ul>
 +
            <li>For example,&nbsp;in Thunderbird (mozilla mail client), they added a magnifying glass inside the text field (Good visual indication what this field is about) and the clear button ('x', is IMO a better icon than what we have) is inside the text field when applicable. Even better is the help text&nbsp;in light gray.</li>
 +
            <li><strong><font color="#00FF00">UI - please provide a bug for this so we
 +
              can track polish</font></strong></li>
 +
          </ul>
 +
        </ul></font></strong></td>
 +
    </tr>
 +
    <tr>
 +
      <td></td>
 +
      <td><p>The fast view icon looks like a bug, as the lower right corner is missing. For all the icons on the fast view bar, it isn't obvious what they do. They should be more "inviting" to click on. Maybe some extra adornment in the icon like an arrow that points in the direction they will open. The tooltip should also show the keyboard shortcut.</p>
 +
        <p><strong><font color="#FF0000">New icon is being requested, no other
 +
          work decided at this point</font></strong></p>
 +
        <p><strong><font color="#00FF00">UI - please provide a bug for this so we can
 +
          track polish</font></strong></p></td>
 +
    </tr>
 +
    <tr>
 +
      <td></td>
 +
      <td>&nbsp;</td>
 +
    </tr>
 +
</table>
  
−
This document was started because of a cross-project agreement reached at the December, 2005, EMO Architecture Council Meeting. There, through their representatives to the Architecture Council, the projects of
+
<h2>JDT Core</h2>
−
the Callisto Release agreed to improve the cross-project update experience. The agreement was that I ([[User:David williams|David Williams]]) would coordinate the effort ... but the projects still had to do the work!
+
<table border="1" cellpadding="2" cellspacing="2" width="100%">
 +
 
 +
    <tr>
 +
      <th width="10%">Bugzilla</th>
 +
      <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
      <td align="right" width="10%">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=108087 108087]</td>
 +
      <td><strong><font color="#FF0000">Java conventions default formatter settings
 +
        confused</font></strong></td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right" width="10%">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=118217 118217]</td>
 +
      <td><p>Change 'unused parameters' warning to only work on private or final methods to avoid false positives.</p></td>
 +
    </tr>
 +
 
 +
</table>
  
−
This document is in no way to "take over" any of the Eclipse base project [http://www.eclipse.org/platform/index.php Update Team's] function, proposals, or responsibilities.
 
  
−
It is also <b>not to add to their responsibilities</b>. The goal for Callisto release is to use and "push the limits" of the current capabilities and technologies of the Update Manager. Of course, bugs and feature
 
−
requests may
 
−
result, and that is fine, but I wanted to be clear this proposal is not for anything fundamentally new ... it is just to document what's already possible, and make sure it is coordinated and carried out with "best
 
−
practices" in mind.
 
  
−
If I understand Wiki's at all committers can use the "talk" feature to provide feedback. Others may open a bugzilla on the Cross Project bugzilla component.
+
<h2>JDT Debug</h2>
 +
<table border="1" cellpadding="2" cellspacing="2" width="100%">
 +
 
 +
    <tr>
 +
      <th width="10%">Bugzilla</th>
 +
      <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
      <td align="right" width="10%"><strong><font color="#0000FF"> [https://bugs.eclipse.org/bugs/show_bug.cgi?id=128074 128074]</font></strong></td>
 +
      <td><strong><font color="#0000FF">Cannot format stack trace</font></strong></td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=123589 123589]</td>
 +
      <td>Unexpected switch to empty editor when using scrapbook</td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=123588 123588]</td>
 +
      <td>Loosing key binding in scrapbook page</td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=130534 130534]</td>
 +
      <td><strong><font color="#FF0000">add a "collapse all" to the tree's toolbar</font></strong></td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=128558 128558]</td>
 +
      <td>support variables in port and host fields of Remote Java Applications</td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=77125 77125]</td>
 +
      <td><strong><font color="#FF0000">preference for determing how Java breakpoints
 +
        are created - to suspend thread or entire VM</font></strong></td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=125768 125768]</td>
 +
      <td>Support to display breakpoints in rulers of external edtiors:<br> <ul>
 +
          <li>ideally, there would be support for markers in external files from text/platform, but we might be able to do something here <i><b>(not sure how much work this is)</b></i></li>
 +
          <li>since we support breakpoints in external files, and the editor now supports a ruler in external files, we really should make the two work together</li>
 +
        </ul></td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=80746 80746]</td>
 +
      <td><font color="#0000FF"><strong>filter exceptions in anonymous classes of X when filtered on X</strong></font></td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=89474 89474]</td>
 +
      <td><strong><font color="#FF0000">support to edit attributes of multiple archives at once</font></strong></td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=110837 110837]</td>
 +
      <td><strong><font color="#FF0000">properly specify bootpath when launching to avoid problems with crypto applications</font></strong></td>
 +
    </tr>
 +
    <tr>
 +
      <td></td>
 +
      <td>Columns in Variables/Registers view:<br>
 +
        <ul>
 +
          <li>We've added support to the debug platform for columns in debug views</li>
 +
          <li>We want to add support for columns in the java debugger as an optional presentation (we've started this already)</li>
 +
          <li><font color="#00FF00">DEBUG - please provide a bug for this so we can track polish</font></li>
 +
        </ul></td>
 +
    </tr>
 +
    <tr>
 +
      <td></td>
 +
      <td>Undo/Redo:<br>
 +
        <ul>
 +
          <li>We don't currently support undo/redo in the Scrapbook or Display view, which has made a few users angry</li>
 +
          <li><font color="#00FF00">DEBUG - please provide a bug for this so we can track polish</font></li>
 +
        </ul></td>
 +
    </tr>
 +
</table>
 +
<br>
 +
<h2>JDT Text</h2>
 +
<table border="1" cellpadding="2" cellspacing="2" width="100%">
 +
 
 +
    <tr>
 +
      <th width="10%">Bugzilla</th>
 +
      <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
      <td align="right" width="10%">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=95619 95619]</td>
 +
      <td><strong><font color="#FF0000">[5.0][content assist] Function parameter assist does not work with some parameterized types</font></strong></td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right" width="10%">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=92371 92371]</td>
 +
      <td><strong><font color="#FF0000">[content assist] Parameter guessing could also propose
 +
      expressions for parameters of array types</font></strong></td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=41189 41189]</td>
 +
      <td><strong><font color="#FF0000">[hovering] Editor tooltip size too small
 +
        for title text (3 votes)</font></strong></td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=125677 125677]</td>
 +
      <td><strong><font color="#FF0000">[navigation] @category not standing out enough in Java Outline view</font></strong></td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=91500 91500]</td>
 +
      <td><strong><font color="#FF0000">Improve the NLS tooling, especially existing hover and linking features to Eclipse string externalization support (2 votes)</font></strong></td>
 +
    </tr>
 +
 
 +
</table>
 +
<h2>JDT UI</h2>
 +
<table border="1" cellpadding="2" cellspacing="2" width="100%">
 +
    <tr>
 +
      <th width="10%">Bugzilla</th>
 +
      <th>Description</th>
 +
    </tr>
 +
    <tr>
 +
      <td align="right" width="10%">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=129929 129929]</td>
 +
      <td>IDE no longer responsive when JUnit tests are running</td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right" width="10%">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=129925 129925]</td>
 +
      <td>[JUnit view] Hierarchical+failures should not show more than just failures</td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=130106 130106]</td>
 +
      <td><font color="#FF0000">[junit] Hierarchical mode sometimes show testcase in progress
 +
      and sometimes not</font></td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=130107 130107]</td>
 +
      <td><font color="#FF0000">[junit view] Hierarchical mode not properly rebuilding the
 +
      tree</font></td>
 +
    </tr>
 +
    <tr>
 +
      <td align="right" width="10%">
 +
        <p>[https://bugs.eclipse.org/bugs/show_bug.cgi?id=136572 136572]</p>
 +
        <p>[https://bugs.eclipse.org/bugs/show_bug.cgi?id=134078 134078]</p>
 +
        <p>[https://bugs.eclipse.org/bugs/show_bug.cgi?id=134305 134305]</p>
 +
      </td>
 +
      <td>Polish the Clean Up support (2 votes):<br>
 +
        <ul>
 +
          <li><font color="#FF0000">Clean Up with focus on current file forces me to save other resources? This is particularly annoying when the resource is a text scratch file.</font></li>
 +
          <li><font color="#0000FF">Clean Up should also offer to format the code.</font></li>
 +
          <li><font color="#FF0000">The wizard needs polish.</font></li>
 +
        </ul>
 +
      </td>
 +
    </tr>
 +
    <tr>
 +
      <td></td>
 +
      <td><p><font color="#0000FF">New Java Perspective (old one becomes the 'Classic Java Perspective')</font></p>
 +
        </td>
 +
    </tr>
 +
    <tr>
  
−
== Use cases ==
+
      <td align="right" width="10%">
−
 
+
        <p>[https://bugs.eclipse.org/bugs/show_bug.cgi?id=119259 119259]</p>
−
There are 3 primary use cases that cross-project, coordinated update sites provide:
+
      </td>
−
 
+
      <td><font color="#FF0000">provide a way to get fully qualified class name into clipboard
−
1. Allow end-users to install some minimum "platform" and from that be able to use Update Manager to install all of the Callisto release, just by going to just one update site and selecting just one thing.
+
      </font></td>
−
 
+
    </tr>
−
<del>2. Allow committers and developers to install an "SDK" version of Callisto, to be used while developing their own plugins.</del>
+
    <tr>
−
 
+
      <td align="right">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=108256 108256]</td>
−
<del>3. Allow adopters to provide their own update sites, and "point to" appropriate sites to pick up prerequisite features. While there is nothing in this Callisto effort to support this directly, Callisto should serve as a good
+
      <td><font color="#FF0000">[refactoring] [ltk] Refactoring preview does not correctly highlight 5.0 code [refactoring]</font></td>
−
example of "best practices" for other projects to follow.</del>
+
    </tr>
−
 
+
    <tr>
−
== Objectives and Constraints ==
+
      <td align="right">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=122527 122527]</td>
−
 
+
      <td><font color="#0000FF">[build path] Offer a SWT container in JDT</font></td>
−
Besides promoting the use cases given above, there are other objectives and constraints to meet:
+
    </tr>
−
 
+
    <tr>
−
 
+
      <td align="right">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=135279 135279]</td>
−
=== Eclipse.org Infrastructure constraints ===
+
      <td><font color="#FF0000">[refactoring] improve order of refactoring actions</font></td>
−
 
+
    </tr>
−
The distribution of Eclipse projects must fit in to the current disk space and "mirror system".
+
    <tr>
−
 
+
      <td align="right">[https://bugs.eclipse.org/bugs/show_bug.cgi?id=135285 135285]</td>
−
* Disk space.
+
      <td><font color="#FF0000">[source actions] improve order of source actions</font></td>
−
** JAR files should not be duplicated to avoid wasting bandwidth and disk space on our mirrors.
+
    </tr>
−
** The site.xml file can be configured to include JARs from various projects and still work with mirrors. See Distributed Bandwidth, below.
+
</table>
−
 
+
−
* Mirroring.
+
−
** Callisto must make the best use of our mirror sites.
+
−
** Our mirror sites should have '''at least''' 24-hours of exclusive access to the Callisto files before releasing them to the public. This is done by waiting for Webmaster approval before sending files to download.eclipse.org.
+
−
** Webmaster will need to advise mirrors ahead of time, so they can anticipate the rush.
+
−
 
+
−
* Bandwidth.
+
−
** Co-ordinate with the Webmaster to "open the floodgates" on the bandwidth ahead of time.
+
−
** R3.1 required additional bandwidth for a foundation-hosted, separate mirror site. We will need this again.
+
−
 
+
−
 
+
−
=== Coordination verus Unification ===
+
−
 
+
−
For ease-of-use, there should be something of a "central site" that should make it easy to "get started" with "all" of Callisto. But, in the Eclipse spirit of allowing projects to "do their own thing" each project should also have their
+
−
own
+
−
discovery and update sites as well. This allows the central "get started" site to be one-size fits all, but still allow projects to offer even more, special features such as tools, examples, etc., that may not be part of
+
−
their "main' deliverables available via Callisto, not to mention have their own schedule for fixes and point releases.
+
−
 
+
−
=== Update Policies ===
+
−
 
+
−
Some sites (corporations) can establish an "corporate" update site, which may have its own policies about what updates when, etc. The process and procedures here should do nothing to interfere with that
+
−
capability.
+
−
 
+
−
== Fundamentals ==
+
−
 
+
−
=== Distributed Storage ===
+
−
 
+
−
Each project will still have its own disk space and area on Eclipse, and will still be responsible for providing jarred features and plugins there, as they would for their own update site.
+
−
 
+
−
=== Distributed Bandwidth ===
+
−
 
+
−
The features (and archive tags, if needed) will be specified using the new "find the closest mirror"  [https://bugs.eclipse.org/bugs/show_bug.cgi?id=99412#c23 luxury support] provided by the Eclipse.org
+
−
download.php script.
+
−
 
+
−
<cite>
+
−
<b>Issue: </b> We (any volunteers?) should begin to collect approximate sizes and make rough estimates of required bandwidth for various scenarios, to make sure our mirroring system will suffice ... or we should panic now!?
+
−
 
+
−
Here is WebMaster's plan to make this happen:
+
−
* Go mirror shopping to get new mirror sites - especially in US and Asia
+
−
* Substantially increase bandwidth a few days ahead of release
+
−
* Allow mirrors 24 hours to sync up
+
−
* Provision a separate, dedicated high-speed mirror within those 24 hours
+
−
* Boom
+
−
</cite>
+
−
 
+
−
=== The Get-Started Platform Download ===
+
−
 
+
−
There will be one ZIP provided (by the Eclipse Project), that corresponds to the minimum amount of Eclipse that enables the update manager to work. This is, literally, the Eclipse Platform ... NOT including JDT and
+
−
PDE.  This feature will have the Callisto site as its implanted discovery site. It will still have 'eclipse' as its update site as it comes from the Eclipse Project (the update site being where "fixes" can be obtained
+
−
automatically by update manager). All other features, from all other projects, will have their own project's discovery and update sites implanted in their features, not the Callisto site). The few features available from
+
−
the central Callisto site will have discovery sites for all 10 Callisto projects.
+
−
 
+
−
<cite>
+
−
<b>Issue: </b>In this day and age, I'm surprised we do not offer "updates" (or "get started") in the form of a WebStart object. I think we do not only due to people constraints ... so, if there is participation from
+
−
the community (including the community of Callisto projects :) then we might be able to improve the user's experience so they'd never have to see another zip file again?
+
−
</cite>
+
−
 
+
−
<b>Note: </b>We should be explicit that the Callisto Update Site, contrary to the name, must begin with a 3.2 based Platform Feature ... there is no capability planned to update from a 3.1 based environment. Likewise, there are no plans to update from an 3.2 M4 environment to a 3.2 M5 environment. We will plan to test updating from an M5 environment to an M6 environment.
+
−
 
+
−
=== The User's Experience ===
+
−
 
+
−
==== The View from Update Manager Dialog ====
+
−
 
+
−
The current plan is, for this Callisto Release, to simply list Features "by Project" [[Image:UpdateProto2.gif]].
+
−
 
+
−
=== Central Callisto Sites ===
+
−
 
+
−
==== Release Site ====
+
−
For the Callisto releases and milestones, there will be one central "discovery" site, such as
+
−
http://download.eclipse.org/callisto/releases
+
−
 
+
−
Note: Its desriable to avoid any reliance on "aliases" as it makes mirroring more difficult to manage.  
+
−
 
+
−
<del>Also, we should be explicit, there is no plans to provide a big-huge-zip that contains all the Callisto projects ... its expected to be provided entirely via update manager.</del> There has been some recent talk of providing "big zips" made easy to get by the use of a form on a web page, and then the user would get, in one download, a zipped up version of their selections. If this is done, would be handled by the Eclipse Foundation (not this cross-project group).
+
−
 
+
−
 
+
−
 
+
−
==== Weekly Integration Update Sites ====
+
−
 
+
−
For those projects wishing to participate, there will be a site for integration builds:
+
−
http://download.eclipse.org/callisto/interim
+
−
 
+
−
==== Working Staging Area ====
+
−
 
+
−
Lastly, there will be a working directory of
+
−
http://download.eclipse.org/callisto/staging
+
−
that is used exclusively by central "Callisto developers" in the days or weeks ahead of the other update "releases" to test that the central features and site.xml is ready before they are copied over to the "public" sites.
+
−
 
+
−
== User Interface Consistency ==
+
−
 
+
−
=== Web site consistency ===
+
−
All update sites will have an "index" file, appropriate for viewing with a web browser ... and we need to work on giving this a consistent look.
+
−
(currently, some projects have none, some have highly detailed slowly performing ones with jars available for download for some reason I do not understand, but [http://download.eclipse.org/webtools/updates/ some :)] have some really nice looking ones.
+
−
 
+
−
=== Update Manager View Consistency ===
+
−
All update sites will provide a "site.xml" file, with a consistent level of abstraction for separately installable features. (Remember, not literally every feature provided by a project has to be "visible" to the update site
+
−
user ... many can be "included" as being required by other features, and installed automatically when other features selected).
+
−
 
+
−
These will be consistent and follow the following UI guidelines:
+
−
 
+
−
; Project Name spelled out, followed by initial in parenthesis, if desired. Such as
+
−
: Graphical Editing Framework (GEF)
+
−
: Eclipse Modeling Framework (EMF)
+
−
 
+
−
; Version numbers only at feature level, not project level categories. Such as
+
−
: Draw2d 3.2 (not GEF 3.2).
+
−
 
+
−
=== Predictable, consistent, long term URL's for update sites ===
+
−
 
+
−
There's currently great inconsistency here. I guess as long as its permanent, and long term, there's no harm. But looks sloppy.
+
−
 
+
−
For example, GEF is in Eclipse, and has no update site of its own. [[https://bugs.eclipse.org/bugs/show_bug.cgi?id=128348 128348]]
+
−
 
+
−
Some sites have a version number in their URL, such as tools/ve/updates/1.0/ and some do not, such as
+
−
tools/emf/updates/. The latter is correct, and important with the new qualified versioning conventions.
+
−
 
+
−
So, I suggest, this is the time to get consistent, but will need some care and thought to be sure it doesn't "break" anything.
+
−
 
+
−
== Planned Tests and Trial runs ==
+
−
 
+
−
During February, initial test versions will be created to download "all of Callisto" to see how it does,
+
−
from several parts of the world. Its not expected these will be "usable" versions of Callisto.
+
−
 
+
−
By the end of the M5 period (3/3), there will be a usable version of Callisto available via update manager.
+
−
(This is the version that can (will) be pointed to during EclipseCon, as an example of what's coming).
+
−
 
+
−
After M5, there will be "updates" (what's the right word for updates to updates?) to the milestones site for each Release Candidate leading up to the release.
+
−
 
+
−
Note: after M5, projects may elect to use the weekly I-build site. But this part of this proposal is sort of experimental, and will need some investigation, to be sure this is no great extra work for anyone ... but the idea is that for developers that are building on top of other features, it's very handy to be able to update pre-reqs in a frequent, easy way. That is, in other words, these "integration sites" are not literally an end-user requirement, so will get a little less attention.
+
−
 
+
−
== Project Responsibilities ==
+
−
 
+
−
This document and this "coordinated effort" is in no way meant to substitute for the projects themselves understanding update manger and update sites and actively
+
−
contributing [[callisto_update_people | the necessary people]] to ensure the
+
−
correct end result.
+
−
 
+
−
The following are some requirements placed on the projects participating in Callisto (most should not be anything "new", but some will be, and feasibility and need will have to be evaluated as we go).
+
−
 
+
−
* provide [[project update sites]], with jars, urls, site.xml files, etc. pretty much as has been done before ... but, might be a good time to change past decisions (for example, GEF does not have its own update site, for ... historical reasons, I guess).  The Callisto site.xml file will "point to" these project-level update sites, so, basically, each project must have a working update site before Callisto can have a working update site. See [[project update sites]] for more details.
+
−
 
+
−
* provide to "[[callisto build]]" a list of minimum features for inclusion in "runtime" version of Callisto (and, please, minimum for "end users" to take advantage of your functionality). It would include 'end user' documentation, but not 'isv documentation nor JavaDoc.
+
−
 
+
−
<del>* provide to [[User:David williams|David williams]] list of features for inclusion in "SDK" version of Callisto (should be no duplicates with first list, the SDK features should "require" runtime versions, so that someone may install runtime first, then install SDK later, without re-downloading or installing the runtime versions). These SDK features dos not have to be ALL your projects features, but should, at least, include 'source' and 'isv documentation'.</del>
+
−
 
+
−
* provide accurate "feature size" so the update time and progress can be accurate. This is just good practice, but since I've noticed many don't sizes in their updates, I thought I would call it out here, since this will be more important in Callisto.
+
−
 
+
−
* (maybe) provide signed jars, so users get some assurance they are installing verifiable Callisto features. This is more important now, using the "nearest mirror" techniques, since users may not know exactly where the jar is coming from. [I just say "maybe" because I do not think any of us know the technical steps or requirements for this.]
+
−
 
+
−
** <b>ISSUE: </b> If we have signed jars, it would be "nice" to have a "signed by Eclipse Foundation" corporate certificate, which I mention here, because I think to get such a certificate is a little time consuming (and not free :)
+
−
 
+
−
== Help Wanted ==
+
−
 
+
−
Besides the main deliverables for Callisto, the participating projects are asked to provide some assistance in testing the Callisto update site and, if possible, there are many tools that could be contributed to help. For example,
+
−
 
+
−
* a "peek" tool which doesn't actually update anything, but which could, say, get the date and size headers for all the jars that would be requested by update manager, just for a warm reassuring feeling that all is (still) available as expected in a quick and painless way.
+
−
 
+
−
* specialist to help with security, signed jars would likely be helpful.
+
−
 
+
−
* specialists to help test and tweak update performance would likely not be refused.
+
−
 
+
−
* etc.
+
−
 
+
−
== Bugzilla Queries ==
+
−
 
+
−
The following are some handy bugzilla queries related to update manager.
+
−
 
+
−
[https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=Platform&component=Update&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&field0-0-0=noop&type0-0-0=noop&value0-0-0=&order=bugs.bug_severity,bugs.target_milestone%2Cbugs.target_milestone%2Cbugs.bug_severity%2Cmap_components.name%2Cbugs.bug_severity%2Cbugs.target_milestone%2Cbugs.bug_severity%2Cmap_components.name%2Cbugs.bug_severity%2Cmap_reporter.login_name%2Cmap_reporter.login_name%2Cmap_components.name%2Cbugs.target_milestone%2Cbugs.bug_severity%2Cbugs.target_milestone%2Cbugs.resolution%2Cmap_components.name%2Cmap_assigned_to.login_name%2Cbugs.bug_status%2Cbugs.target_milestone%2Cbugs.target_milestone%2Cbugs.target_milestone%2Cbugs.bug_severity%2Cbugs.bug_status%2Cbugs.target_milestone%2Cbugs.priority%2Cbugs.bug_id&query_based_on=  All Opened]
+
−
 
+
−
 
+
−
[https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=Platform&component=Update&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailreporter1=1&emailtype1=substring&email1=david_williams&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=  All Opened by David Williams :) since starting to play with Callisto Updates.]
+
−
 
+
−
== Tips and Tricks ==
+
−
 
+
−
In addition to the written works in the reference section, I often some across little tidbits in bug reports, newsgroups, etc., and hope we can collect some of them on our [[Callisto Build and Update Tips and Tricks]] page. (So I can find them in the future :)
+
−
 
+
−
== Related Links for Further Enjoyable Reading and Reference ==
+
−
 
+
−
[http://help.eclipse.org/help31/index.jsp?topic=/org.eclipse.platform.doc.isv/guide/product_update.htm Basics of Update Sites]
+
−
 
+
−
[http://www.eclipse.org/articles/Article-Update/keeping-up-to-date.html How To Keep Up To Date]
+
−
 
+
−
[http://www.eclipse.org/eclipse/platform-core/documents/plugin-versioning.html Plugin Versioning Proposal]
+
−
 
+
−
[http://www.eclipse.org/eclipse/platform-core/documents/update.html Update Site Proposal]
+
−
 
+
−
[http://www.eclipse.org/eclipse/platform-core/documents/3.1/run_from_jars.html Jarring Plugins]
+
−
 
+
−
[[Development_Conventions_and_Guidelines]]
+
−
 
+
−
[[JAR_Signing]]
+

Revision as of 11:17, 20 April 2006

3.2 Polish Items

Last update: March 15, 2006 (Changes since March 13, 2006 in green. New entries in Team and JDT UI)

New additions in green.

Entries in RED have been fixed.

Entries in BLUE are not in the plan for 3.2


 So far, I have received input from the Search, Platform/JDT Text, JDT Core, JDT UI, and Debug teams. This document contains a summary of that feedback. The items are listed by component, but are otherwise in no particular order.

General / All

Bugzilla Description
Do we need a new splash screen? MVM asking designers to investigate in light of new welcome as well.
Update keywords for searching preference pages. I.e. verify that all the new preferences are covered.


Platform Runtime

Bugzilla Description
128178 [Workbench] earlyStartup does not work in runtime eclipse with binary-imported plugins

Platform Compare

Bugzilla Description
78063 Full Javadoc line selected even though only a character has been added to a word
68758 Structured Compare: selected added element not part of selection
128362 [Patch] Creating patch from compare in between versions/revisions
118021 Structured compare not available with additions or deletions

112661 (bugs logged by mvm previously)

132693

 Cleanup UI of Create/Apply Patch wizards (follow Eclipse UI guidelines):
  • button sizes
  • caption
  • margins
  • mnemonics (missing)
  • polish all descriptions and messages
  • Match Project... button launches dialog called Retarget Patch (inconsistent)


    Platform CVS

    Bugzilla Description
    112927 [performance] Update CVS workspace job takes too long
    See also " [#too_may_password">too many passwords]" in the Platform UI section below.


    Platform Help

    Bugzilla Description
    New help support should be improved (2 votes):
    • Help button should be on the side where the help shows up. Should stay pushed, and a release should close the help view again
    • dialogs without help should better not get the help button
    • clicking on a link should directly open the help browser as the space next to the dialog is always too small


    Platform SWT

    Bugzilla Description
    95634 [Tree] TreeColumn does not show "..." on cut-off Text and misses tooltips
    I know I'm dreaming, but: styled ranges inside a tree item (Font/colors etc for e.g. a word inside the full label) would be a boost
    125702 If you collapse a tree on a recent version of GTK+, a big block of whitespace appears at the bottom. It's very irritating.

    123425

    5200

    		 There's also the "festival of carets" bug. This is immediately noticeable to anyone using a recent GTK+, and it makes us look bad. Unfortunately, it appears to be a bug somewhere in the Cairo/Pango/glib/GTK+ stack specific to the FPU mode (which the Java VM modifies on start-up). This bug is bad and will be hard to track down. We need to do work if we want to see this fixed; we can't just say "It's their problem".
     
     


    Platform Team

    Bugzilla Description
    Need a general polish pass on new History view filtering and user interactions. The bugs below are examples...
    125860 New history view: filter is not persisted - no way to constantly ignore local history
    129916 Per date sorting in History view forced on me upon ever input change
     

    MOVED FROM UI

    There are sometimes <a name="too_may_password">]too many password dialogs:

    • If I'm trying to work off-line but have CVS projects in workspace, it can happen that you get lots of dialogs to ask for the password as the CVS decorators each need that password. Clicking cancel once should be enough to let them know that I'm not interested in entering the password now.
    • It would be nice to have a less intrusive way of asking for passwords. Idea is e.g. a status line icon similar to the progress view that blinks when a passwords are pending. Clicking on this icon brings a 'authentication view' that shows that status of all passwords: passed, failed, canceled, and lets me trying to connect again.
    130408 Should be able to export psfs to the workspace (2 votes)


    Platform Text

    Bugzilla Description
    11624 Text Drag and Drop (has many bug votes)

    In order to resolve this we first need to put the grounds for drag and drop contributions to editors, otherwise clients contributing some sort of DnD will get broken. This is covered in bug 125957 and won't make it into 3.2.


    Platform UI

    Bugzilla Description
    119890

    [ViewMgmt] Allow control of view tab compression

    - this was changed in 3.2 and need to decide if we like it
    100993 [EditorMgmt][Presentations] Regression: Editor tabs do not remember order or active tab after restarting Eclipse

    Investigating
    128455 [Presentation] [ViewBar] Outline view toolbar is visible above a maximized editor
    131559 [Markers] Layout of marker filters dialog
    129936 [ViewMgmt] View part description label should wrap
    125691 [ViewMgmt] Can't read view titles
    68684 Remove MRU Ordering from the editors.</td> 
       </tr>
    113455</td> Some errors do not appear in the Problems view. This happens very frequently for me (multi-processor box, GTK+) if I have grouping turned on.</td> 
       </tr>
    130818</td> Filters do not seem to apply when grouping by Java type (Problems view).
           </td>
   </tr>
     </td>  </td> 
       </tr>
    126155</td> [Markers] Issues of multi quick fix dialog</td> 
       </tr>
    122639</td> [WorkbenchParts] PageBookView's toolbar doesn't properly re-layout after page switching</td> 
       </tr>
    128670</td> [Dialogs] StatusDialog adds 2 horizontal margins around button bar</td> 
       </tr>
    127629</td> [Markers] problems view: keep selection stable</td> 
       </tr>
    128381, 128381</td> [Markers] group should only show (10 of 10 items) if beyond the limit</td> 
       </tr>
    129812</td> [Markers] Enabling problem categorization per default</td> 
       </tr>
    129184</td> Progress view should be made more prominent</td> 
       </tr>
    127289</td> [Markers] SystemFilter and group selection 
           state not preserved</td>
   </tr>
    see suggestions in bug 109998</td> Experimental (?) Keys preference page (3 votes):
    • what do we do with the two pages?
    • sorting by keys, by commands and by scope 109998
    • see which keys are free and which commands are not used
    • Platform UI team is investigating what can/can not be done about this without Doug around
    </td> 
       </tr>
    </td> Finish the preferences clean up effort from 3.0:
    • decorator preference pages should offer a link to decorators</li>
    • font / color preferences should use shared settings so it is also possible to configure the color and font decoration for CVS on the CVS page
    • UI - please provide a bug for this so we can track polish
    </td> 
       </tr>
    </td> Improve the look of the filter control (preferences, other dialogs):
    • the text field seems unaligned as long as there is no 'clear' button
    • either dump the 'clear' button, or add it as a lay-over over the text field:
      • For example, in Thunderbird (mozilla mail client), they added a magnifying glass inside the text field (Good visual indication what this field is about) and the clear button ('x', is IMO a better icon than what we have) is inside the text field when applicable. Even better is the help text in light gray.
      • UI - please provide a bug for this so we can track polish
    </td> 
       </tr>
    </td>

    The fast view icon looks like a bug, as the lower right corner is missing. For all the icons on the fast view bar, it isn't obvious what they do. They should be more "inviting" to click on. Maybe some extra adornment in the icon like an arrow that points in the direction they will open. The tooltip should also show the keyboard shortcut.

    New icon is being requested, no other work decided at this point

    UI - please provide a bug for this so we can track polish

    </td> 
       </tr>
    </td>  </td> 
       </tr>

    </table>

    JDT Core

    Bugzilla Description
    108087 Java conventions default formatter settings confused
    118217

    Change 'unused parameters' warning to only work on private or final methods to avoid false positives.


    JDT Debug

    Bugzilla Description
    128074 Cannot format stack trace
    123589 Unexpected switch to empty editor when using scrapbook
    123588 Loosing key binding in scrapbook page
    130534 add a "collapse all" to the tree's toolbar
    128558 support variables in port and host fields of Remote Java Applications
    77125 preference for determing how Java breakpoints are created - to suspend thread or entire VM
    125768 Support to display breakpoints in rulers of external edtiors:
    • ideally, there would be support for markers in external files from text/platform, but we might be able to do something here (not sure how much work this is)
    • since we support breakpoints in external files, and the editor now supports a ruler in external files, we really should make the two work together
    80746 filter exceptions in anonymous classes of X when filtered on X
    89474 support to edit attributes of multiple archives at once
    110837 properly specify bootpath when launching to avoid problems with crypto applications
    Columns in Variables/Registers view:
    • We've added support to the debug platform for columns in debug views
    • We want to add support for columns in the java debugger as an optional presentation (we've started this already)
    • DEBUG - please provide a bug for this so we can track polish
    Undo/Redo:
    • We don't currently support undo/redo in the Scrapbook or Display view, which has made a few users angry
    • DEBUG - please provide a bug for this so we can track polish


    JDT Text

    Bugzilla Description
    95619 [5.0][content assist] Function parameter assist does not work with some parameterized types
    92371 [content assist] Parameter guessing could also propose expressions for parameters of array types
    41189 [hovering] Editor tooltip size too small for title text (3 votes)
    125677 [navigation] @category not standing out enough in Java Outline view
    91500 Improve the NLS tooling, especially existing hover and linking features to Eclipse string externalization support (2 votes)

    JDT UI

    Bugzilla Description
    129929 IDE no longer responsive when JUnit tests are running
    129925 [JUnit view] Hierarchical+failures should not show more than just failures
    130106 [junit] Hierarchical mode sometimes show testcase in progress and sometimes not
    130107 [junit view] Hierarchical mode not properly rebuilding the tree

    136572

    134078

    134305

    		 Polish the Clean Up support (2 votes):
    • Clean Up with focus on current file forces me to save other resources? This is particularly annoying when the resource is a text scratch file.
    • Clean Up should also offer to format the code.
    • The wizard needs polish.

    New Java Perspective (old one becomes the 'Classic Java Perspective')

    119259

    		 provide a way to get fully qualified class name into clipboard
    108256 [refactoring] [ltk] Refactoring preview does not correctly highlight 5.0 code [refactoring]
    122527 [build path] Offer a SWT container in JDT
    135279 [refactoring] improve order of refactoring actions
    135285 [source actions] improve order of source actions
    Retrieved from "https://wiki.eclipse.org/index.php?title=Callisto_Coordinated_Update_Sites&oldid=4141"

    Back to the top