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. 
  I have committed some changes of project.container.view extension
point. There are two elements now: simpletab and uritab - they are
defined in schema/page.exsd. uritab takes as attributes: accessMethod,
contents (among others). They will be used to identify which page should
be opened and what should be the parameters. This is the result of our
discussion about project container and repositories definition. What do
you think about it?
  I have also added another attribute: tabOrder. The idea is to define,
which tabs should be displayed "rather" earlier in the project viewer
(e.g. overview tab should be the first one). tabOrder is given by
extension provider, so they can compete who gets earlier. Do you think
this is ok?
  There are also two new extensions that add overview and subprojects
tabs to the project container view extension point. The extensions are
in client.project.ui. This is a very initial version, so only demo
information is displayed. Can you check if it is something what we
generally expect?
  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