Community
Participate
Working Groups
Build ID: Eclipse 3.4 Depends on Bug 213402, which needs to be implemented before this enhancement takes place. When a user is working on a resource in the CDOEditor, he might want to make a reference to an element stored in another repository (or even out of CDO, as Bug 213402 describes). In this case, the (only?) option is to load a resource into the current CDOEditor (its WorkingSet?). This loading is transient, these external resources are not imported into the repository (unless the user wishes to). For this, EMF provided "load resource..." action in the contextual menu of the Sample Editor (right mouse click). In the case of the CDOEditor, this action should be adapted to the new CDO environment. This implies: - Being able to browse current available repositories - Transient loading of external resources (XMIResources) to allow referencing their elements. Could be integrated with 242155, to give the the user the option to import external resource into the repo. Any comments are welcome :)
Now that we have Bug #213402, we can start with this, but: - Commiting a transaction which contains CDOObjects referencing other objects persisted out of a CDO Repository won't work. This was expected to fixed in Bug 213402. - What it's currently possible to be done is loading a CDOResource persisted in a repository, but we would need some UI artifacts to get this done: * Create a CDO-Repository explorer to be able to select resources to be loaded. * A central storage of repository URIs to be used in the repository explorer. * Modify CDOActionBarContributor to add a new action "Load from CDO Repository.." As an example, I'll show what I've done for our product: IMG1: http://img151.imageshack.us/img151/7184/img1oe9.png IMG2: http://img266.imageshack.us/img266/9311/img2wz0.png IMG3: http://img227.imageshack.us/img227/6820/img3xa7.png - IMG1: Preferences page to allow the user add commonly used repository URIs (we are currently using a different URI format). - IMG2: Load Resource Dialog. Removed the other actions until it get's fixed. - IMG3: Repository Explorer (I haven't profit from the new CDOResourceFolder, so everything is shown plain :( ) Comments?
(In reply to comment #1) > Now that we have Bug #213402, we can start with this, but: > > - Commiting a transaction which contains CDOObjects referencing other objects > persisted out of a CDO Repository won't work. This was expected to fixed in Bug > 213402. > > - What it's currently possible to be done is loading a CDOResource persisted in > a repository, but we would need some UI artifacts to get this done: > > * Create a CDO-Repository explorer to be able to select resources to be > loaded. > * A central storage of repository URIs to be used in the repository explorer. > * Modify CDOActionBarContributor to add a new action "Load from CDO > Repository.." > > As an example, I'll show what I've done for our product: > > IMG1: http://img151.imageshack.us/img151/7184/img1oe9.png > IMG2: http://img266.imageshack.us/img266/9311/img2wz0.png > IMG3: http://img227.imageshack.us/img227/6820/img3xa7.png > > - IMG1: Preferences page to allow the user add commonly used repository URIs > (we are currently using a different URI format). > - IMG2: Load Resource Dialog. Removed the other actions until it get's fixed. > - IMG3: Repository Explorer (I haven't profit from the new CDOResourceFolder, > so everything is shown plain :( ) > > Comments? > This is cool Vic!! Can you share your code ?
Simon, > This is cool Vic!! Can you share your code ? yes, I can, but it would need some refactor, since it's currently part of our product code. I'll work on it and provide a patch as soon as posible :)
Re-assigning to Vik in preparation of his new committer state...
Rebasing all unresolved enhancement requests to 3.0
Rebasing all outstanding enhancements requests to version 4.0
Moving all open enhancement requests to 4.1
Moving all open issues to 4.2. Open bugs can be ported to 4.1 maintenance after they've been fixed in master.
Moving all outstanding enhancements to 4.3
Moving all open enhancement requests to 4.4
Moving all open bugzillas to 4.5.
Moving all unaddressed bugzillas to 4.6.
Moving all open bugs to 4.7
Moving all unresolved issues to version 4.8-
Moving all unresolved issues to version 4.9
Moving to 4.13.
