blob: 412a7106f08a83fead5904e29c500e2a7289cb3e (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
|
======================================================================
EXAMPLE TEAM UI API USAGES
======================================================================
1. embeding sync viewer in dialog/wizard
2. added a new content provider (logical views)
3. adding custom label decorations
4. actions/menus
5. fetching sync info set without instantiating a participant
6. fetch and wait for the event collector to finish processing the changes
======================================================================
PR LIST (07-01-2004)
======================================================================
x P3 schedule support by participant.
this requires changing the refresh jobs to accept scheduling different jobs. Essentially being able to have an
ordered queue of refreshes. Also, participant will need a schedule object to encapsulate the schedule logic.
x P3 status message could be more precise instead of simply "Working". But to do this we need access to the job progress monitor
and it isn't available API from the UI. (removed status in sync view, progress will be shown in the progress shell).
x P1 end of refresh prompt should be a property change notice, and let the participant decide what to do!
x P2 decide overview page contents and how it should be used
x remove duplicated tree/table viewers classes. the orignial ones simply have the INavigable behavior.
x P1 make changes section only be a pagebook. this would easily allow adding any number of composites to the page?
should look at memory consuption and ensure that we are disposing properly!
- compareeditorinput fetcheds remote content outside of a progress monitor
x decorations for SyncInfoDiffElements (of which type.. project persistent property setting?)
x labels for compare editors (text merge viewers and title for diff viewer)
x generic navigate support for SyncInfoDiffTreeViewer, PRd compare for API support
x readonly state for compare panes
- progress support added when fetching (e.g. caching contents in ITypedElement). This will require compare to add some API.
x INavigable in compare needs to be made API.
- details dialog needs to create composites once then display them. Or only create once!!!!
x sync set filtering creation must be more precise. For example you should be able to specify a root and a direction.
x cvs update/commit action in sync view toolbar are not updating their state anymore :(
x P3 mode switching at the end of a refresh to ensure that changes are shown if available
x P2 need an event for adding roots to a subscriber to update the list shown
x memory and sync set disposal in syncsetcompare input!!!! VERY IMPORTANT!!!
- overiding outgoing/incoming doesn't show the changes in the commit dialog because the filter is only configured to show in one direction.
======================================================================
PR LIST (16-01-2004)
======================================================================
- progress monitoring in SyncSet.reset and such. there are many places where null progress monitors are passed along.
- showing sync view in commit dialog is complicated because there is no easy way of finding out exactly which resources will be committed at the
point the commit comment dialog is shown. Need to provide new API on the commit dialog for this.
- convert details dialogs that show sync view into wizards, this allows more room to browse the changes. almost like the refactoring. Preview >> button instead of Next >>.
- job status handler API or not??
======================================================================
PR LIST (26-01-2004)
======================================================================
- navigable APIs must be consolidated, sync view navigation
- compare configuration review
- logical view extensions
- based on project natures
- ui (e.g. layouts/context menu??)
- content provider should not assume diff nodes have associated resources
- content provider input? Is it a diff node or sync set? diff node hack required for getting the
compare editor input working.
- viewer input as a diffnode with a sync set seems wrong?
- share reconciling with existing (e.g. using compare contents to resolve)
- comment grouping logical view
- target migration
|
