[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [corona-dev] FW: CCX and PCV (or CCV)
|
One problem that I find with this approach is that we already have a
number or actions in PCX for various types of repositories. Some actions
require PCV. We would have to make those actions dependent on type of
containing CC. But of course it can be done.
Marcin
O'Flynn, Dennis wrote:
Piotr,
The following is about bugz item 173623
<https://bugs.eclipse.org/bugs/show_bug.cgi?id=173623>
The objective of was to provide an “explorer” view that would show all
of the defined ContextContainers, regardless of their type. This would
allow the “SystemContainer”, “ProjectContainers”, as well as any other
container type to be listed in the same “explorer” view.
When the user selects a ContextContainer to be opened, the “explorer”
needs to launch the appropriate “viewer”. For our exemplary
implementation of a “ProjectContainer”, this would be our current
“ProjectContainerViewer” (PCV). The specific “viewer” to be launched
will be defined by using a new extension point
(org.eclipse.corona.viewer?), similar to how the current PCV finds the
specific PCV-page to use for a REPOSITORY-DESCRIPTOR.
The goal of this enhancement is to allow any collaboration solution to
easily register the specific “viewer” for its type of ContextContainer
through the use of an extension point. The “explorer” is used to match
the ContextContainer type to the specific “viewer”.
-----Original Message-----
From: Piotr Jaworowski [mailto:jaworowski.piotr@xxxxxxxxx]
Sent: Monday, March 12, 2007 1:02 PM
To: O'Flynn, Dennis
Cc: Jaworowski, Piotr
Subject: CCX and PCV (or CCV)
Hi,
Sorry that I'm writing so late, but i had emergency at home and i had to
run.
Regarding bug 173623:
/What was done till now:
/ * New “Context Container Explorer” can display any type of
ContextContainer
* CCX retrieves data from the server in the background.
/You’d like to have additionally following thing /(as I’ve understood in
the conf. call):
* common "Show view" action for all elements in CCX view.
* Extension point defined for CCX elements which would say which view
should be opened for an element;
/Some questions:/
* Is it possible for element to be shown in separate view? Or would you
like to have it in the way it’s done now; one context container, one
view with separate sub tabs for it’s repository descriptors?
* which value you’d like me to check for context container to mach
proper view;
- object instance
- CC uri
- CC type
- all of the above ;-)
/Current implementation:
/ I'm not sure what we're trying to achive, but in current
implementation we can easily enhance the CCX actions.
The "Show View" is an action which is assigned to CCX displayed element
(for now all elements), other projects can write their own actions for
opening the views in not "corona standard" way.
Actions can customized in many ways. Check the example for "Import"
action. Action will be displayed only for RepositoryDescriptorStub
objects which have content-type set to
/http://www.eclipse.org/corona/contentTypes/eclipseProjectContent
/
<objectContribution
adaptable="false"
id="RepositoryDescriptorStub.workbench.project"
objectClass="org.eclipse.corona.container.project.ui.model.RepositoryDescriptorStub">
<visibility>
<objectState
name="content-type"
value="http://www.eclipse.org/corona/contentTypes/eclipseProjectContent"/>
</visibility>
<action
class="org.eclipse.corona.container.project.ui.explorer.actions.ImportPCXActionDelegate"
id="org.eclipse.corona.container.project.ui.explorer.actions.ImportPCXActionDelegate"
label="Import"
menubarPath="additions"/>
</objectContribution>
If you could please give me some more info, how do you see this, it
would be really great.
Thanks a lot, and sorry I’ve misunderstood the bug description so I
didn’t take care of this before.
Cheers,
Piotr
The contents of this e-mail are intended for the named addressee only.
It contains information that may be confidential. Unless you are the
named addressee or an authorized designee, you may not copy or use it,
or disclose it to anyone else. If you received it in error please
notify us immediately and then destroy it.
------------------------------------------------------------------------
_______________________________________________
corona-dev mailing list
corona-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/corona-dev
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
