Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [corona-dev] Poject container viewer pages. 
  
  The architecture to access container and container repositories on the
client side looks like this:
	1. container and its repository definitions is taken from the
generated SDO classes
	2. there is an extension point that requires the parameters: the
kind and type and a factory. The extender implements a factory that
returns the actual implementation to access a given repository
	3. there is a method getRepositoryByKind to get repositories
(probably it will be in GenericContainer)
	4. the multi-page project browser supplies a second extension
point that enables the addition of new tabs to the browser, a tab
defines for which kind of repository it should be opened
	5. a tab is opened for each defined repository and matching will
be done by kind attribute; additionally there will be tabs for whole
project container (eg. overview tab, properties, ...).

  The mail about adding kind to ProjectContainer definition is in fact
the result of our discussion about multi-page project browser.

  Marcin & Pawel

-----Original Message-----
From: corona-dev-bounces@xxxxxxxxxxx
[mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of O'Flynn, Dennis
Sent: Saturday, July 15, 2006 12:26 AM
To: Corona development
Subject: RE: [corona-dev] Poject container viewer pages.

Pawel,

Marcin and I had a conversation earlier today re: the extension point
attributes for a ProjectContainerViewPage.  The current attribute,
URI_SCHEME is only a sample.  This sample attribute should be replaced
with the a set of attributes that will allow the ProjectContainerView to
easily match which extension point page should be used for each
ProjectContainer-Repository.

Once these changes are done, please commit them to CVS.

Thanks,
-Dennis

-----Original Message-----
From: corona-dev-bounces@xxxxxxxxxxx
[mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of Kaczmarek, Pawel
Sent: Friday, July 14, 2006 6:14 AM
To: Corona development
Subject: RE: [corona-dev] Poject container viewer pages.


Hi
  We had some discussion here about the structure of the plugin,
especially what should be added by the extension point provider and what
should be generated by extensions.
  I attach the schema file of the plugin (schema/page.exsd) and modified
ProjectContainerView. Now the plugin enables two "elements": uritab and
simpletab. uritab is for view that process some uri, simpletab is for
views like EventList or CoronaProjects explorer. uritab has an
additional uri_scheme attributed in comparison to simple tab.
  Do you think this solution is OK and can be committed?
Pawel

-----Original Message-----
From: corona-dev-bounces@xxxxxxxxxxx
[mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of Wright, Jim
Sent: Friday, July 14, 2006 12:04 PM
To: Corona development
Subject: RE: [corona-dev] Poject container viewer pages.

I have not had a chance to review all of Dennis changes to the project
container view.

To create a new Project Container View, you should be able to add it to
the extension point and extend ProjectContainerPage.

While the sample was a WebBrowser, fixed pages should be easily added.

I while check the changes Dennis made.

JimW

-----Original Message-----
From: corona-dev-bounces@xxxxxxxxxxx
[mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of Marcin Okraszewski
Sent: Friday, July 14, 2006 3:39 AM
To: Corona development
Subject: [corona-dev] Poject container viewer pages.

Hi,
We were looking yesterday at the project container viewer.  It seems
that adding new tabs to the view, requires a registration of a new
protocol handler and then opening some URIs, which selects a proper page
class. It is fine but there are some pages (tabs) that do not work with
URI, but should rather be added for each project container viewer. This
could be an event list for the specified project container, list of
active users, chat view, etc. Shouldn't there be a mechanism (an
additional extension point) for adding fixed pages?

Marcin


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. 
_______________________________________________
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. 
_______________________________________________
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.

Back to the top