platform-ui-home/R3_1/dynamic_teams/dynamic_teams.html

Parent Directory Parent Directory | Revision Log Revision Log

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

1 : mvanmeek 1.1 <html>
2 :     <head>
3 :     <title>Platform UI 3.1</title>
4 :     <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
5 :     <link rel="stylesheet" href="http://dev.eclipse.org/default_style.css" type="text/css">
6 : mvanmeek 1.2
7 : mvanmeek 1.5 <style type="text/css">
8 :     <!--
9 :     .style1 {
10 :     color: #FF3333;
11 :     font-weight: bold;
12 :     }
13 :     -->
14 :     </style>
15 : mvanmeek 1.1 </head>
16 :    
17 :     <body bgcolor="#FFFFFF" text="#000000">
18 :     <table border=0 cellspacing=5 cellpadding=2 width="100%" >
19 :     <tr>
20 : mvanmeek 1.3 <td align=left width="72%"> <font class=indextop>&nbsp; </font>
21 : mvanmeek 1.1 <font class=indexsub> platform user Interface</font></td>
22 :     <td width="28%">
23 :     <img src="http://dev.eclipse.org/images/Idea.jpg" height=86 width=120
24 :     alt="Eclipse documentation banner"
25 :     ></td>
26 :     </tr>
27 :     </table>
28 : mvanmeek 1.3 <h3 align="left">Dynamic Teams</h3>
29 :     <ul>
30 : nick 1.12 <li><a href="dynamic_teams.html#preferences">Preferences</a></li>
31 :     <li><a href="dynamic_teams.html#actionContributions">Action Contributions</a></li>
32 :     <li><a href="dynamic_teams.html#navigatorFramework">Navigator Framework</a></li>
33 : mvanmeek 1.3 </ul>
34 : mvanmeek 1.1 <table border=0 cellspacing=5 cellpadding=2 width="100%" >
35 : nick 1.12 <tr> <a NAME="preferences"> </a>
36 : mvanmeek 1.6 <td width="96%" height="25" colspan="2" align=LEFT valign=TOP bgcolor="#0080C0"><strong><a name="team1"><font color="#FFFFFF" face="Arial,Helvetica">Preference</font></a><font color="#FFFFFF" face="Arial,Helvetica">s</font><font color="#FFFFFF"></font></strong></td>
37 : nick 1.12 </tr>
38 : mvanmeek 1.1 <tr>
39 : mvanmeek 1.7 <td><p><strong>Team Goals in no particular order:</strong></p>
40 : mvanmeek 1.1 <ol>
41 : mvanmeek 1.2 <li>Simplify the preferences UI</li>
42 : mvanmeek 1.7 <li>Establish the approach for adopting the R3.0 Core support for preferences
43 : mvanmeek 1.2 <ol>
44 : mvanmeek 1.7 <li>define the compatibility story for both UI and Core existing API
45 :     </li>
46 :     <li>document a model that plug-ins should use when using preference
47 :     scopes</li>
48 :     <li>Import/Export - define strategy to be used for import and export
49 :     re: scopes </li>
50 : mvanmeek 1.1 </ol>
51 :     </li>
52 : mvanmeek 1.4 <li>Support better ways to make preferences available throughout the UI</li>
53 : mvanmeek 1.1 </ol>
54 : mvanmeek 1.2 <p><strong>Team:</strong></p>
55 :     <ul>
56 : mvanmeek 1.25 <li>Monsignor Tod Creasey</li>
57 : mvanmeek 1.16 <li>DJ Houghten</li>
58 : mvanmeek 1.2 <li>Tom Eicher</li>
59 :     <li>Martin Aeschlimann</li>
60 :     <li>Michael Van Meekeren </li>
61 : mvanmeek 1.25 <li>(Visual Design) Linda Watson</li>
62 : mvanmeek 1.7 </ul>
63 : mvanmeek 1.22 <p><strong>Planned Work for M4 (committed items): </strong></p>
64 : mvanmeek 1.2 <ol>
65 : mvanmeek 1.7 <li> <img src="../../images/progress.gif" nosave="" height="5" width="14" border="0">
66 : mvanmeek 1.9 Preference page sharing/navigation:
67 : mvanmeek 1.7 <ol>
68 :     <li>editing multiple preference pages simultaneously /preference page
69 :     dependancies
70 :     <ol>
71 :     <li>Oct 19 - 26 Martin to investigate this as well as details
72 :     related to how to keep information that is shared accross pages
73 :     in sync</li>
74 :     <li><strong>Oct 26 - Nov 2 </strong>
75 :     <ol>
76 : mvanmeek 1.9 <li><a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/r3_1/proposals/preferences/usability-improvement-suggestions.html">See
77 :     Tom and Martins documentation on overall preference navigation/usability/sharing</a>
78 : mvanmeek 1.10 <ol>
79 :     <li>linking style is supported but can be different per
80 :     page</li>
81 :     <li>will take up less space, need some guidelines for
82 :     commonly used links like &quot;advanced&quot;</li>
83 :     <li>need history controls to move back and forth</li>
84 :     <li>what about jumping around in the lists when the selection
85 :     changes </li>
86 :     <li>how do you open a linked page on specific information</li>
87 :     <li>searching, need to have a prototype</li>
88 :     <li>working copy, need to have a prototype</li>
89 :     </ol>
90 : mvanmeek 1.9 </li>
91 : mvanmeek 1.7 <li>Example 1. Java build path affects other applications
92 :     build path</li>
93 :     <li>Example 2. pages show a preview but preview is affected
94 :     by other pages</li>
95 :     <li>Example 3. project options inherits from instance settings</li>
96 :     <li>pages don't share information
97 :     <ol>
98 :     <li>force apply when page left?</li>
99 :     <li>working copy which is a copy of preferences that all
100 :     pages are working on?</li>
101 :     <li>pages should be organized better, combine pages via
102 :     links or combining the</li>
103 :     </ol>
104 :     </li>
105 :     <li>Important to list the scenarios</li>
106 :     </ol>
107 :     </li>
108 : mvanmeek 1.10 <li><strong>Nov 9 - 16</strong>
109 :     <ol>
110 :     <li>prototype/patch implementation</li>
111 :     <li>first pass for linking between pages behaviour is the
112 :     same as R3.0</li>
113 :     <li>ability to browse back and forward in response to this.</li>
114 :     </ol>
115 :     </li>
116 : mvanmeek 1.19 <li><img src="../../images/ok.gif" nosave="" height="20" width="20" border="0">
117 :     <strong>Nov 18</strong>
118 : mvanmeek 1.14 <ol>
119 :     <li>committed to JDT UI</li>
120 :     <li>looking at forms code</li>
121 :     <li>submitted a patch to <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=78878">bug
122 : mvanmeek 1.19 78878</a>
123 : mvanmeek 1.16 <ol>
124 : mvanmeek 1.19 <li>TC or MVM to look at the patch</li>
125 :     </ol>
126 :     </li>
127 :     </ol>
128 :     </li>
129 :     <li><strong>Nov 23</strong>
130 :     <ol>
131 :     <li>TC - establish a story for the link widget</li>
132 :     <li>make an example use case for this in the UI</li>
133 :     <li>Non-internal version of preference page opening
134 :     <ol>
135 :     <li>i.e. API to open on a page or switch to a page</li>
136 :     <li>take an Object argument as well</li>
137 :     <li>experimental for now</li>
138 :     <li>wait to see what the solution is for filtering/highlighting
139 :     pages to see what to do here</li>
140 : mvanmeek 1.16 </ol>
141 :     </li>
142 : mvanmeek 1.14 </ol>
143 :     </li>
144 : mvanmeek 1.7 <li> Owner: MA (ZRH) </li>
145 :     </ol>
146 :     </li>
147 :     <li>preference sharing (teams contribute similar prefs to a common
148 :     page)
149 :     <ol>
150 : mvanmeek 1.9 <li>Owner: None</li>
151 : mvanmeek 1.7 </ol>
152 :     </li>
153 : mvanmeek 1.19 <li>Tree support in the Project Properties view bug <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=54128">54128</a></li>
154 : mvanmeek 1.7 </ol>
155 :     </li>
156 : mvanmeek 1.9 <li> <img src="../../images/progress.gif" nosave="" height="5" width="14" border="0">
157 : mvanmeek 1.7 Re-catagorize preferences to see if this solves the problems with finding
158 :     the preferences
159 :     <ol>
160 : mvanmeek 1.22 <li><img src="../../images/ok.gif" nosave="" height="20" width="20" border="0">
161 :     Investigate links between pages
162 : mvanmeek 1.10 <ol>
163 :     <li>searching and linking are usefull for managing lots of data
164 :     but also good if someone tends to prefer it over reading the
165 :     pages etc...</li>
166 :     <li>Alternatives
167 :     <ol>
168 :     <li>suggest that we provide examples/API to support links
169 :     but not add to pref ext. pt. schema or bottom of a pref
170 :     page by default</li>
171 :     </ol>
172 :     </li>
173 :     </ol>
174 :     </li>
175 : mvanmeek 1.7 <li>Investigate combining pages that have common information
176 :     <ol>
177 : mvanmeek 1.10 <li><strong>Nov 9 - 16</strong>
178 :     <ol>
179 :     <li>Seems like our three examples (label decorations, colors
180 :     and fonts, editor properties) are very different</li>
181 :     <li>suggest linking should solve this</li>
182 : mvanmeek 1.14 <li>need back&lt;-&gt;forward navigation support in the Preference
183 :     Dialog so the user is not lost</li>
184 : mvanmeek 1.10 </ol>
185 :     </li>
186 : mvanmeek 1.7 <li>Owner: TC,MVM (OTT)</li>
187 :     </ol>
188 :     </li>
189 : mvanmeek 1.22 <li><img src="../../images/ok.gif" nosave="" height="20" width="20" border="0"><strong>Nov
190 :     23</strong>
191 : mvanmeek 1.19 <ol>
192 :     <li>UI to review <a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-ui-home/r3_1/proposals/preferences/page-regrouping.html">suggestions
193 :     on page regrouping </a>by TE and MA on pref pages
194 :     <ol>
195 :     <li>DJ, TC and MVM to review the JDT team pref pages</li>
196 :     </ol>
197 :     </li>
198 :     <li>MA to fabricate some screen shots on hiding advanced pages</li>
199 :     </ol>
200 :     </li>
201 : mvanmeek 1.10 </ol>
202 :     </li>
203 : mvanmeek 1.22 </ol>
204 :     <p><strong>M5 finishing work:</strong></p>
205 :     <p>After M4 there are a few items that we would like to revisit and work
206 :     on independantly to 'complete' and polish what was done in M4, they are:
207 :     </p>
208 :     <ul>
209 : mvanmeek 1.26 <li>Properties dialog (TC to do <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=82467">82467</a>)
210 : mvanmeek 1.22 <ul>
211 : mvanmeek 1.26 <li>put search in the dialog (consistent with preferences dialog)</li>
212 : mvanmeek 1.22 </ul>
213 :     </li>
214 : mvanmeek 1.26 <li> import/export (mvm to release ext. pt. - release for next Integration
215 :     build)
216 : mvanmeek 1.22 <ul>
217 :     <li>add support for pluggable import/export wizards instead of import/export
218 :     on the pref dialog</li>
219 :     </ul>
220 :     </li>
221 :     <li> M5 PreferenceService lookup order and support for listening on all
222 : mvanmeek 1.26 scopes (DJ still working, need to talk to Jim)
223 : mvanmeek 1.22 <ul>
224 :     <li>need to re-visit API here</li>
225 :     <li>build something on top of the existing &quot;too-powerful&quot;
226 :     core support to make a simpler programming model</li>
227 :     </ul>
228 :     </li>
229 : mvanmeek 1.26 <li>working copy (release for next Integration build)
230 : mvanmeek 1.22 <ul>
231 :     <li>use Colors and Fonts and Editors use of the same prefs to show
232 :     colors as a case to prototype a working model API where preferences
233 :     saved go to an intermediate pref. store so that pages can query
234 :     this and get live information for preferences that have been changed
235 :     in one page and not applied to the underlying store yet</li>
236 : mvanmeek 1.26 <li>* TC and DJ to released modified version of Martins work
237 :     <ul>
238 :     <li>for the next Integration build</li>
239 :     </ul>
240 :     </li>
241 : mvanmeek 1.22 </ul>
242 :     </li>
243 : mvanmeek 1.26 <li> View settings (TC , log a bug and see what we can offer here bug
244 :     <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=82566">82566</a>)
245 : mvanmeek 1.22 <ul>
246 :     <li>add a simple view (much like properties) so a view can open a
247 :     dialog on its own preferences and not have them show up in the global
248 :     prefs if not necessary</li>
249 :     </ul>
250 :     </li>
251 : mvanmeek 1.26 <li>View instance data persistance (find existing bugs and see if any
252 :     exist if not log it)
253 : mvanmeek 1.22 <ul>
254 :     <li>currently two instances of the same view can not persist their
255 :     setting which causes lots of strange behaviour when opening multiple
256 :     Workbench windows for example and trying to set various options
257 :     on views</li>
258 :     </ul>
259 : mvanmeek 1.9 </li>
260 : mvanmeek 1.26 <li>What happens with CDT when we apply grouping and they add themselves
261 :     to the SDK (TC and MVM)
262 :     <ul>
263 :     <li> </li>
264 :     </ul>
265 :     need to also be able to change the labels (TC-MVM , TE)
266 :     <ul>
267 :     <li>reduce the need for override labels where possible</li>
268 :     <li>OR provide another label </li>
269 :     </ul>
270 :     </li>
271 : mvanmeek 1.22 </ul>
272 : mvanmeek 1.9 <h2><strong>Completed</strong></h2>
273 :     <ol>
274 :     <li><img src="../../images/ok.gif" nosave="" height="20" width="20" border="0">
275 :     Core API backwards compatibility <strong>(Goal #2) </strong>
276 :     <ol>
277 :     <li> Document a plan with respect to the new API based on dyn. team
278 :     input, document what that story is, publish to mailing lists for
279 :     added visibility</li>
280 :     <li>Oct 19 - 26 (THREE issues) <a href="http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-core-home/documents/user_settings/pref_apis.html">
281 :     See DJs doc on this </a>
282 :     <ol>
283 :     <li>ONE typed events </li>
284 :     <li>TWO - some CORE API for setting prefs. (putValue) does not
285 :     send prop. change events which ends up not updating the caches
286 :     as the caches is changed as a result of an event, what should
287 :     we do for cases where prefs are cached for example and no event
288 :     is sent to update the value
289 :     <ol>
290 :     <li>can not back out as this is API</li>
291 :     <li>log bug reports checking uses of putValue as no event
292 :     is sent </li>
293 :     <li>update doc with hint that only non-API prefs should be
294 :     used in this way if at all</li>
295 :     </ol>
296 :     </li>
297 :     <li>THREE
298 :     <ol>
299 :     <li>plug-ins in RCP should be aware of the no data (no workspace)
300 :     case.</li>
301 :     <li>need to put some changes in workbench</li>
302 :     </ol>
303 :     </li>
304 :     </ol>
305 :     </li>
306 :     <li><strong>Oct 26 - Nov 2</strong>
307 :     <ol>
308 :     <li>DJ to send note to mailing lists with potential problem areas</li>
309 :     <li>porting guide</li>
310 :     </ol>
311 :     </li>
312 :     <li>Owner: DJ (OTT Core) </li>
313 :     </ol>
314 :     </li>
315 :     <li><img src="../../images/ok.gif" nosave="" height="20" width="20" border="0">
316 :     In-line opening of preference pages <strong>(Goal #3)</strong>
317 :     <ol>
318 :     <li> Produce a patch to prototype version of direct preference page
319 :     opening, Platform UI to evaluate agree on final version and implement
320 :     </li>
321 :     <li>Oct 19 - 26
322 :     <ol>
323 :     <li>DP to cleanup a few issues around this work. Some API public
324 :     yet, need to get Tom to try</li>
325 :     </ol>
326 :     </li>
327 :     <li> Owner: Tom (ZRH), Doug Pollock (OTT) </li>
328 : mvanmeek 1.7 </ol>
329 :     </li>
330 : mvanmeek 1.21 <li><img src="../../images/ok.gif" nosave="" height="20" width="20" border="0">
331 :     Pass through the preferences to see which ones should be view only preferences
332 :     <ol>
333 :     <li>need some guidelines for views (MA - ZRH)</li>
334 :     <li><strong>Nov 18</strong>
335 :     <ol>
336 :     <li>TE to check with MA to see if this really is what he was working
337 :     on.</li>
338 :     </ol>
339 :     </li>
340 :     <li><strong>Nov 26</strong>
341 :     <ol>
342 :     <li>Search is an example here, how do we deal with view instance
343 :     settings</li>
344 :     <li>MA - to investigate</li>
345 :     </ol>
346 :     </li>
347 :     </ol>
348 :     </li>
349 : mvanmeek 1.22 <li><img src="../../images/ok.gif" nosave="" height="20" width="13" border="0">
350 : mvanmeek 1.21 Functional high level category view in preference dialog <strong>(Goal
351 :     #1)</strong> </li>
352 :     <ol>
353 :     <ol>
354 :     <ol>
355 :     <li> Iterate over a <strong>Prototype </strong> new Preferences
356 :     Dialog/Demo to dynamic team, to have something new in M3 with
357 :     regards to functional top level preference categories </li>
358 :     <li>Simplified presentation for preferences and preference catagories</li>
359 :     <li>Easier navigation of the preference pages </li>
360 :     <li>Oct 19 - 26 - think of issues with high vs wide pref pages.
361 :     Can we use the width better
362 :     <ol>
363 :     <li>move icons along the top </li>
364 :     <li>how do we deal with pref pages of the same name (e.g. Editors)
365 :     </li>
366 :     </ol>
367 :     </li>
368 :     <li><strong>Oct 26 - Nov 2 </strong> Prototype #2 with list with
369 :     large icons on left and expandable list on right
370 :     <ol>
371 :     <li>need a design review</li>
372 :     </ol>
373 :     </li>
374 :     <li><strong>Nov 9</strong>
375 :     <ol>
376 :     <li>sent <a href="prefs4.gif">samples snapshot to designers</a></li>
377 :     <li>*** TC and MVM - how will catagorization work, how will
378 :     it be flexible from the product level</li>
379 :     <li>what about advanced being a dumping grounds for all other
380 :     options?</li>
381 :     <li>what about having an advanced button on each group so you
382 :     can get all options?</li>
383 :     <li>should not introduce another scope here (i.e. advanced).</li>
384 :     <li>plan to finish for M4</li>
385 :     </ol>
386 :     </li>
387 :     <li><strong>Nov 18</strong>
388 :     <ol>
389 :     <li>waiting on designers </li>
390 :     </ol>
391 :     </li>
392 :     <li>Owner: TC (OTT Platform UI)</li>
393 : mvanmeek 1.22 </ol>
394 :     </ol>
395 :     </ol>
396 :     <li><img src="../../images/ok.gif" nosave="" height="20" width="13" border="0">
397 :     Initiate instrumentation work to help provide data for preference cleanup,
398 :     goal is to have information by beginning of M4<strong> (Goal #1) </strong>
399 :     </li>
400 :     <ol>
401 :     <ol>
402 :     <ol>
403 :     <ol>
404 :     <li>Oct 19 - instrumentation plugins working on R3.0 and R3.0
405 :     M2</li>
406 :     <li>Oct 19 - 22 - decide on date when information can be obtained
407 :     if possible </li>
408 :     <li><strong>Oct 26 - Nov 2 </strong>
409 :     <ol>
410 :     <li>Instrumentation is under way</li>
411 :     </ol>
412 :     </li>
413 :     <li><strong>Nov 18 - </strong>Pilot instrumentation survey to
414 :     be run this coming week</li>
415 :     <li><img src="../../images/ok.gif" nosave="" height="20" width="20" border="0"><strong>Dec
416 :     1</strong>, began survey</li>
417 :     <li>Owner: Michael (OTT Platform UI) </li>
418 :     </ol>
419 : mvanmeek 1.21 </ol>
420 :     </ol>
421 :     </ol>
422 : mvanmeek 1.26 <li><img src="../../images/ok.gif" nosave="" height="20" width="20" border="0">Catagories
423 :     and Components </li>
424 :     <li>
425 :     <ul>
426 :     <li> how can we keep things simple for parenting of pages</li>
427 :     <li>* TC reorganized the schema, updated Platform plugin.xml</li>
428 :     <li>* Groups override parenting </li>
429 :     </ul>
430 :     </li>
431 :     <li> <img src="../../images/ok.gif" nosave="" height="20" width="20" border="0">
432 :     what do we do with advanced topics? (DONE - use Other category)
433 :     <ul>
434 :     <li>hide advanced pages</li>
435 :     <li>advanced sections on individual pages</li>
436 :     <li>advanced category (i.e. group in the toolbar)</li>
437 :     <li>groups in the pref dialog map directly to capabilities aside from
438 :     perhaps always having a &quot;General&quot; group</li>
439 :     </ul>
440 :     </li>
441 : mvanmeek 1.7 </ol>
442 :     <p><strong>Full list of issues that were discussed (note: these are not
443 :     all committed items):</strong></p>
444 : mvanmeek 1.2 <p>* low priority<br>
445 :     ** medium priority<br>
446 :     *** high priority<br>
447 : mvanmeek 1.7 </p>
448 : mvanmeek 1.2 <ol>
449 : mvanmeek 1.7 <li>*** Make the UI simpler, current solution does not scale well, encourages
450 :     too many categories
451 : mvanmeek 1.2 <ol>
452 : mvanmeek 1.7 <li> UI model with leaning towards few logical/functional groupings
453 :     at the top level</li>
454 :     <li>The Import/Export support should only talk about being able to
455 :     export things to the same extent that it can provide a human readable
456 :     string for the items</li>
457 : mvanmeek 1.2 <li>Currently categorized by plug-in</li>
458 : mvanmeek 1.7 <li>Is there any way to enforce/restrict these categories on downstream
459 :     products?</li>
460 : mvanmeek 1.2 </ol>
461 :     </li>
462 : mvanmeek 1.7 <li> *** Clean up
463 : mvanmeek 1.2 <ol>
464 :     <li>Remove legacy, unneeded, confusing preferences, advanced</li>
465 : mvanmeek 1.7 <li>Use instrumentation tools to found out unused preferences vs frequently
466 :     used</li>
467 : mvanmeek 1.2 </ol>
468 :     </li>
469 : mvanmeek 1.7 <li>*** Backwards Compatibility
470 : mvanmeek 1.2 <ol>
471 : mvanmeek 1.7 <li>Need to clearly define what we do/do not support in terms of backward
472 :     compatibility for the Core API</li>
473 : mvanmeek 1.2 <li>Write more tests?</li>
474 :     <li>Scoped preference store tests</li>
475 :     <li>Are we allowed to break APIs?</li>
476 :     </ol>
477 :     </li>
478 : mvanmeek 1.7 <li>*** Sharing
479 : mvanmeek 1.2 <ol>
480 :     <li>Other teams contribute &quot;pages&quot; to a shared page</li>
481 :     <li>Decorators on three pages </li>
482 : mvanmeek 1.7 <li>E.g. workbench contributes a category and other teams contribute
483 :     (e.g. appearance)
484 : mvanmeek 1.2 <ol>
485 :     <li>Not a hardcoded list</li>
486 :     </ol>
487 :     </li>
488 : mvanmeek 1.7 <li>Sharing an individual preference
489 : mvanmeek 1.2 <ol>
490 : mvanmeek 1.7 <li>e.g. print margin is shared for all editors
491 : mvanmeek 1.2 <ol>
492 :     <li> text font, overriding inherited prefs in some cases</li>
493 :     </ol>
494 :     </li>
495 :     </ol>
496 :     </li>
497 :     </ol>
498 :     </li>
499 : mvanmeek 1.7 <li>** Support to directly open a preference page (or open all prefs.
500 :     but to a specific page)
501 : mvanmeek 1.2 <ol>
502 :     <li>On a specific page</li>
503 : mvanmeek 1.7 <li>Page might switch to a specific tab or group (i.e. don't talk
504 :     in terms of the UI, but rather what is to be shown and the page
505 :     figures it out)</li>
506 : mvanmeek 1.2 <li>Option to show all pages, one page, or a part of the page</li>
507 : mvanmeek 1.7 <li>Opening a single page or portion of the preferences
508 : mvanmeek 1.2 <ol>
509 :     <li>ZRH has a prototype</li>
510 :     </ol>
511 :     </li>
512 :     </ol>
513 :     </li>
514 : mvanmeek 1.7 <li>** Scalable
515 : mvanmeek 1.2 <ol>
516 :     <li>Enable search for preferences</li>
517 : mvanmeek 1.7 <li>Enable highlighting of
518 : mvanmeek 1.2 <ol>
519 :     <li> pages in the tree</li>
520 :     <li>controls (checkboxes...) on a page</li>
521 : mvanmeek 1.7 <li>enable different navigation controls on the LHS of the preference
522 :     dialog (see screenshots)</li>
523 : mvanmeek 1.2 <li>ability to have a different view on the preferences</li>
524 :     <li>should we keep the existing structure?</li>
525 :     <li>How do we contribute this information? XML?</li>
526 :     <li>Does the extension point mechanism scale that well?</li>
527 :     <li>Don't want to aggressively activate plug-ins. (when searching)</li>
528 :     </ol>
529 :     </li>
530 :     </ol>
531 :     </li>
532 : mvanmeek 1.7 <li>* Locking/Access Control
533 : mvanmeek 1.2 <ol>
534 : mvanmeek 1.7 <li>Requirements?
535 : mvanmeek 1.2 <ol>
536 :     <li>Locking = remove from the UI? At the granularity of a page?</li>
537 :     <li>Preferences that are not displayed in the UI</li>
538 :     </ol>
539 :     </li>
540 :     </ol>
541 :     </li>
542 : mvanmeek 1.7 <li>*Ability to apply preferences between page switch to help with inconsistent
543 :     preferences
544 :     <ol>
545 :     <li>Need a working copy of the preferences root</li>
546 :     </ol>
547 : mvanmeek 1.2 </li>
548 : mvanmeek 1.7 <li>* API
549 : mvanmeek 1.2 <ol>
550 : mvanmeek 1.7 <li> Do we need new API for associating human readable strings with
551 :     preferences, or categories?</li>
552 : mvanmeek 1.2 <li>Can we simplify the current API?</li>
553 : mvanmeek 1.7 <li> Does this live in Core? UI? Could be at the Preference Page level
554 :     </li>
555 : mvanmeek 1.2 </ol>
556 :     </li>
557 : mvanmeek 1.7 <li>* Running background operations from a preference dialog<span class="style1">
558 :     (NEW ON OCT 19)</span>
559 : mvanmeek 1.5 <ol>
560 : mvanmeek 1.7 <li>E.g. ask for a build twice</li>
561 : mvanmeek 1.5 </ol>
562 :     </li>
563 : mvanmeek 1.7 <li> Theme support on various levels
564 : mvanmeek 1.2 <ol>
565 :     <li>(e.g. syntax highlighting themes, formatting themes, overall themes</li>
566 :     </ol>
567 :     </li>
568 : mvanmeek 1.7 <li>Allow Export to export random preferences, not all preferences are
569 :     stored in core</li>
570 : mvanmeek 1.2 <li>non-exportable preference/non sharable preferences</li>
571 :     <li>Need to deal with the three core layers that we have? Project, configuration...</li>
572 : mvanmeek 1.7 <li>Batched property change events</li>
573 :     <li>Bug 54392 </li>
574 :     </ol>
575 :     <p><strong>Other Future Ideas: </strong></p>
576 : mvanmeek 1.2 <ul>
577 : mvanmeek 1.7 <li>Auto-page generation based on preference types and predifined behaviour
578 :     (e.g. boolean pref gets a check box and a label)</li>
579 :     <li>Metadata for preferences? Store: user-readable name, groupings/dependencies,
580 :     category, exportable flag, sharable flag </li>
581 :     <li> When you export, it might not be exporting what you think you are
582 :     since preference pages aren't explicitly linked to the preference store.
583 :     </li>
584 :     <li> Movement between tabs in preference pages -&gt; marked as dirty until
585 : mvanmeek 1.14 OK or APPLY is hit. Everyone implements their own ?working copy? strategy
586 : mvanmeek 1.2 <ul>
587 : mvanmeek 1.7 <li>Maybe work with a preference tree and then apply it to the real
588 :     preferences? (note: the import/export mechanism at the Core level
589 :     allows manipulation of a preferences tree and then apply it to the
590 :     real tree) </li>
591 : mvanmeek 1.2 </ul>
592 :     </li>
593 :     <li> Displaying scopes in the UI </li>
594 : mvanmeek 1.7 <li>Import/Export of project preferences -&gt; When you import, you really
595 :     want to apply these preferences to a specific group of projects in your
596 :     workspace (underlying mechanism doesn't allow for this right now) </li>
597 : mvanmeek 1.2 </ul></td>
598 : mvanmeek 1.7 <td>&nbsp;</td>
599 : mvanmeek 1.2 </tr>
600 : mvanmeek 1.1 </table>
601 :    
602 :     <table border="0" cellspacing="5" cellpadding="2" width="100%">
603 :     <tbody>
604 :     <tr>
605 : mvanmeek 1.6 <td width="96%" height="23" colspan="2" align="left" valign="top" bgcolor="#0080c0"><b><font face="Arial,Helvetica"><font color="#ffffff">
606 : nick 1.12 <a name="actionContributions"></a>
607 :     Action Contributions</font></font></b></td>
608 : mvanmeek 1.1 </tr>
609 : mvanmeek 1.6 <tr>
610 : nick 1.11 <td height="232" colspan="2" valign="top">
611 : mvanmeek 1.6 <p><strong>Team:</strong></p>
612 :     <ul>
613 :     <li>Nick Edgar</li>
614 :     <li>Kai-Uwe Maetzel</li>
615 :     <li>Douglas Pollock</li>
616 :     <li>Michael Van Meekeren </li>
617 :     </ul>
618 : dpollock 1.28
619 :     <p>The goal is to make significant enhancements to the contributions mechanism.</p>
620 : nick 1.11
621 :     <p><strong>Documents:</strong></p>
622 :     <ul>
623 : dpollock 1.28 <li><a href="../contributions-proposal/requestForComments.html">Proposal (v0.3)</a> [<a href="../contributions-proposal/requestForComments.pdf">PDF</a>] [<a href="../contributions-proposal/requestForComments.sxw">OpenOffice</a>]</li>
624 : dpollock 1.27 <li>Complete example of the <a href="../contributions-proposal/fullExample-new.xml">proposed extension point syntax</a>.</li>
625 :     <li>Complete example of the <a href="../contributions-proposal/fullExample.xml">existing extension point syntax</a>.</li>
626 : nick 1.17 <li><a href="../contributions-proposal/scenarios.html">Scenarios for contributing menu items and toolbar items in the Workbench</a>.</li>
627 :     <li>Actions in the Navigator view (presentation, applicability, etc): <a href="../contributions-proposal/NavigatorActions.html">HTML</a>, <a href="../contributions-proposal/NavigatorActions.xls">Excel spreadsheet</a>.</li>
628 :     <li><a href="../contributions-proposal/nick_navigator.xml">Sketch of changes to Navigator view's extensions (does not correspond exactly with schema above).</a></li>
629 : nick 1.11 </ul>
630 : dpollock 1.23
631 : mvanmeek 1.24 <p><strong>Code</strong></p>
632 : dpollock 1.23 <p>The work in progress is available in CVS. You must check out
633 :     "org.eclipse.core.commands", as well as the "dpollock_Doomsday" branch
634 :     for "org.eclipse.jface", "org.eclipse.ui", "org.eclipse.ui.tests" and
635 :     "org.eclipse.ui.workbench".</p>
636 : nick 1.17
637 : nick 1.11 <p><strong>Planned Work for M5:</strong></p>
638 : mvanmeek 1.6 <ul>
639 : nick 1.11 <li>Investigate pushing down refactoring participants mechanism to workbench and generalizing it to a general operation participants model.(db/ne/jml)
640 :     </li>
641 :     </ul>
642 : nick 1.17
643 : nick 1.11 <p><strong>Planned Work for M4:</strong></p>
644 :     <ul>
645 :     <li> <img src="../../images/progress.gif" nosave="" height="5" width="14" border="0">
646 :     Prototype sample API designed to unify/simplify and clarify (see bug
647 :     36968) the current set of contribution API's
648 : mvanmeek 1.6 <ul>
649 : nick 1.11 <li><img src="../../images/progress.gif" nosave="" height="5" width="14" border="0">
650 :     API should fix the following among others:
651 :     <ul>
652 :     <li><img src="../../images/progress.gif" nosave="" height="5" width="14" border="0">
653 :     difficulty determining keybindings to show for context menu
654 :     items.</li>
655 :     <li><img src="../../images/progress.gif" nosave="" height="5" width="14" border="0">
656 :     understand and plan for support of ordering of items (eg. action
657 :     sets)</li>
658 :     <li><img src="../../images/progress.gif" nosave="" height="5" width="14" border="0">
659 :     ability to declare a command and handler once, and support
660 :     placement of the command separately.
661 :     <ul>
662 :     <li>Enablement is defined by the handler</li>
663 :     </ul>
664 :     </li>
665 :     <li><img src="../../images/progress.gif" nosave="" height="5" width="14" border="0">
666 :     see proposal coming soon</li>
667 :     </ul>
668 :     </li>
669 :     <li><img src="../../images/progress.gif" nosave="" height="5" width="14" border="0">
670 :     write regression tests</li>
671 :     <li><img src="../../images/progress.gif" nosave="" height="5" width="14" border="0">
672 :     build sample/example test plug-ins</li>
673 :     <li><img src="../../images/progress.gif" nosave="" height="5" width="14" border="0">
674 :     investigate lower level (e.g. JFace) related existing API to ensure
675 :     consistancy</li>
676 :     <li><img src="../../images/progress.gif" nosave="" height="5" width="14" border="0">
677 :     minimally support new API based on the existing code
678 :     <ul>
679 :     <li>time permitting enhance or re-write portions of the existing
680 :     code for the following reasons:
681 :     <ul>
682 :     <li>does not support lazy updating in the UI</li>
683 :     <li>poor performance</li>
684 :     <li>complex submenu manager code</li>
685 :     </ul>
686 :     </li>
687 :     </ul>
688 :     </li>
689 :     <li><img src="../../images/progress.gif" nosave="" height="5" width="14" border="0">
690 :     ISV doc showing migration steps and introducing the new API (ac,
691 :     dp) </li>
692 : mvanmeek 1.6 </ul>
693 :     </li>
694 : nick 1.11 </ul>
695 :     <p><strong>Completed Work for M3:</strong></p>
696 :     <ul>
697 :     <li><img src="../../images/ok.gif" nosave="" height="12" width="12" border="0"> Document scenarios for use cases for Actions (ne)</li>
698 : mvanmeek 1.6 </ul>
699 :     <p>&nbsp;</p></td>
700 :     </tr>
701 :     <tr>
702 :     <td width="96%" height="23" colspan="2" align="left" valign="top" bgcolor="#0080c0"><b><font face="Arial,Helvetica"><font color="#ffffff">
703 : nick 1.12 <a name="navigatorFramework"></a>Navigator Framework</font></font></b></td>
704 : mvanmeek 1.6 </tr>
705 : mvanmeek 1.1 <tr>
706 : mvanmeek 1.6 <td height="232" colspan="2" valign="top"><p><strong>Team Goals in no particular order:</strong></p>
707 :     <ol>
708 :     <li>Provide a general framework for developing navigator views in the context of RCP or the Workbench </li>
709 :     <li>Framework should act as a test bed for new support for:
710 :     <ol>
711 :     <li>retargetable actions</li>
712 :     <li>operations framework</li>
713 :     <li>working set enhancements for large workspaces</li>
714 :     <li> </li>
715 :     </ol>
716 :     non-resource based navigator support </li>
717 :     </ol>
718 :     <p><strong>Team:</strong></p>
719 :     <ul>
720 :     <li>Billy Biggs</li>
721 :     <li>Nick Edgar</li>
722 :     <li>Dirk Baeumer</li>
723 :     <li>Michael Van Meekeren </li>
724 :     </ul>
725 :     <p><strong>Planned Work for M3:</strong></p>
726 :     <ul>
727 :     <li><img src="../../images/progress.gif" nosave="" height="5" width="14" border="0"> Implement prototype generic navigator framework based on original <a href="../../navigator-proposal/general_purpose_navigator_proposal.html">&quot;Generic Navigator&quot; proposal</a> <ul>
728 :     <li>Owner BB (OTT) </li>
729 :     </ul>
730 :     </li>
731 :     <li><img src="../../images/progress.gif" nosave="" height="5" width="14" border="0"> Investigate supporting working groups and filters (namely M3 additions in Package Explorer for managing large workspaces) in generic layer
732 :     <ul>
733 :     <li>Owner BB (OTT, DB to send pointers to code)</li>
734 :     </ul>
735 :     </li>
736 :     <li> <img src="../../images/ok.gif" nosave="" height="20" width="20" border="0"> Move re-targetable action work to Action Contributions dyn. team
737 :     <ul>
738 :     <li>Owner MVM (OTT) </li>
739 :     </ul>
740 :     </li>
741 :     <li>OTHER ITEMS
742 :     <ul>
743 :     <li><img src="../../images/progress.gif" nosave="" height="5" width="14" border="0"> Operations (side note, not officially part of this work but recorded here)
744 :     <ul>
745 :     <li>NOTE JM (OTT) and DB (ZRH) to investigate a prototype for this then to come back in M4 with requirements for UI </li>
746 :     <li>Generalize Operations and push code down from LTK DB (ZRH) </li>
747 :     </ul>
748 :     </li>
749 :     <li><img src="../../images/progress.gif" nosave="" height="5" width="14" border="0"> Work on removing needed for LegacyResourceSupport class JM (OTT) </li>
750 :     </ul>
751 :     </li>
752 :     </ul>
753 :     <blockquote>
754 :     <p>&nbsp;</p>
755 :     </blockquote> <p><strong>Ideas/Possible future work:</strong></p>
756 :     <p>- </p></td>
757 : mvanmeek 1.1 </tr>
758 :     <tr>
759 : mvanmeek 1.6 <td width="96%"> </tr>
760 : mvanmeek 1.1 </tbody>
761 :     </table>
762 :     </body>
763 :     </html>