Hi, >>> Does it answer to you questions? (I hope to be enough clear on what I >>> have in mind on those points, do not hesitate to ask more. >> >> >> I wonder if I am missing something. >> I'd better learn CPS? > I think it will be good to install or to login on a demo cps server > server to see how it is working
> I will look for an account on a demo CPS server and I will send you. Thanks. I will look into CPS and FileSystem provider. Takenori
Hi, I drew a relationship between ResourceManager and db4o Local ECM Provider. http://tmtec.biz/download/ResourceManager.jpg Now that I have figured out an overview of ECM Resource I'd like to know priorities ahead. In order to pass the next phase(Creation Review?) of Eclipse Development Process, what is important? Reliable contributor names? Reliable models? Completeness of an initial implementation? > I will look for an account on a demo CPS server and I will send you. Can you send the account? Thanks, Takenori -----Original Message----- From: apogee-bounces@... [mailto:apogee-bounces@... com]On Behalf Of Sato Sent: Tuesday, February 28, 2006 2:03 PM To: apogee@... Subject: RE: [Apogee] Local ECM Provider Hi,(Continue reading)
Hi Sato, I apologize for the answer delay, I was really busy next week. Sato a écrit : > I drew a relationship between ResourceManager and db4o Local ECM Provider. > http://tmtec.biz/download/ResourceManager.jpg > Now that I have figured out an overview of ECM Resource > I'd like to know priorities ahead. > Great, thanks! (Sorry to not comment it, Bogdan is much more efficient for that(Continue reading)
Hi, First of all, many thanks for your registration of db4o community, Bodgan :) > So most important is to improve specifications and start the code > (detailled roadmap, etc.). Then I begin to code in order to refine the spec, following FileSystem provider. > To start to code, I propose to keep it simple for now: point an > component you are interested in, write some technical specs and discuss > them, code!(Continue reading)
Hi Sato, I've done some work on the UI level Now you can browse the resource tree from the Apogee perspective. A "New Site wizard" is available for nthe FileSystem provider - so you can map a file system tree to an Apogee site. The model was refined - I hope to update the arch. doc soon to explain modifications - and some problems in the Apogee resource model detected when implementing the UI fixed. The main modifications are: - A Site is now managed locally by the ResourceManager - it is not managed by the ECM provider - while ISiteFolder and ISiteFiles are managed by ECM provider The site have a root that is a ISiteFolder and is mapping the local site to a remote (ECM provider controlled) object tree. - more high level listeners added - changed the path from string to ResourcePath. I think I will change it again these days to IPath provided eclipse - added extension point to define object types and resource UI adapters. - created the UI adapter/view infrastructure - need optimization at content provider level - for now each time getLabel() is called a lookup for the resouirce metadata is performed which can be very costly on some ECM providers since the metadata may be located on network. I shoul do some caching at this level. Anyway I think each ECM providers should implement a caching mechanism for the metadata if looking it up is costly - since the metadata is frequently asked at the UI level. Anyway this could also be improved at UI level by doing some caching in(Continue reading)
Hi,
I was unable to test the filesystem provider, where do you configure apogee to add the new site wizard ?
Regards,
Nicolas
Hi Sato,
I've done some work on the UI level
Now you can browse the resource tree from the Apogee perspective.
A "New Site wizard" is available for nthe FileSystem provider - so you
can map a file system tree to an Apogee site.
The model was refined - I hope to update the arch. doc soon to explain
modifications - and some problems in the Apogee resource model detected
when implementing the UI fixed.
The main modifications are:
- A Site is now managed locally by the ResourceManager - it is not
managed by the ECM provider - while ISiteFolder and ISiteFiles are
managed by ECM provider
The site have a root that is a ISiteFolder and is mapping the local
site to a remote (ECM provider controlled) object tree.
- more high level listeners added
- changed the path from string to ResourcePath. I think I will change it
again these days to IPath provided eclipse
- added extension point to define object types and resource UI adapters.
- created the UI adapter/view infrastructure - need optimization at
content provider level - for now each time getLabel() is called a lookup
for the resouirce metadata is performed which can be very costly on some
ECM providers since the metadata may be located on network.
I shoul do some caching at this level.
Anyway I think each ECM providers should implement a caching mechanism
for the metadata if looking it up is costly - since the metadata is
frequently asked at the UI level.
Anyway this could also be improved at UI level by doing some caching in
the view content provider (this is not thread safe but providers are
allways called from the UI thread)
You need the following plugins to test the UI perspective:
(I've not tested yet in Windows)
**drwxr-xr-x 3 bstefanescu bstefanescu 4096 2006-03-03 18:37
com.db4objects.db4o_1.0.0
-rw-r--r-- 1 bstefanescu bstefanescu 113642 2006-03-03 18:37
com.nuxeo.apogee_1.0.0.jar
-rw-r--r-- 1 bstefanescu bstefanescu 29297 2006-03-03 18:48
org.nuxeo.apogee.filesystem_1.0.0.jar
-rw-r--r-- 1 bstefanescu bstefanescu 12643 2006-03-03 19:21
org.nuxeo.commons_1.0.0.jar
-rw-r--r-- 1 bstefanescu bstefanescu 61061 2006-03-03 19:21
org.nuxeo.core.resources_1.0.0.jar
-rw-r--r-- 1 bstefanescu bstefanescu 402 2006-03-03 18:37
org.nuxeo.logging_1.0.0.jar
-rw-r--r-- 1 bstefanescu bstefanescu 15736 2006-03-03 18:37
org.nuxeo.ui_1.0.0.jar
-rw-r--r-- 1 bstefanescu bstefanescu 15318 2006-03-03 18:59
org.nuxeo.ui.resources_1.0.0.jar
-rw-r--r-- 1 bstefanescu bstefanescu 210410 2006-03-03 18:37
org.slf4j.nlog4j_1.0.0.jar
You can run Apogee as a IDe plugin or as a RCP application (the rcp app
is defined by the plugin com.nuxeo.apogee )
To see the resource navigator enter the Apogee Perspective and then
create a new filesystem site from the new wizard menu:
New > Apogee Project > New File System Site
The user defined sites are persisted using db4o (see
org.nuxeo.core.resources.model.impl.SitesManager class)
Sites are stored in the db4o as SiteObject objects...
I will try to document all this at the end of the week
Sato wrote:
>Hi,
>
>First of all,
>many thanks for your registration of db4o community, Bodgan :)
>
>
>
>>So most important is to improve specifications and start the code
>>(detailled roadmap, etc.).
>>
>>
>
>Then I begin to code in order to refine the spec, following FileSystem provider.
>
>
>
>>To start to code, I propose to keep it simple for now: point an
>>component you are interested in, write some technical specs and discuss
>>them, code!
>>
>>
>
>I see.
>
>
>
>>The easiest and most efficient way for you to have a look at CPS is to
>>download it (http://www.cps-project.org/ ) and install/run it.
>>
>>
>
>OK. I try it.
>
>Thanks,
>Takenori
>
>-----Original Message-----
>From: Eric Barroca [mailto: eb-CQNGlVZ5l00AvxtiuMwx3w@public.gmane.org]
>Sent: Monday, March 06, 2006 11:24 AM
>To: Sato
>Cc: apogee-FQDHc1wsLCU3qPAbE1dS1g@public.gmane.org.com
>Subject: Re: [Apogee] Local ECM Provider
>
>
>Hi Sato,
>
>I apologize for the answer delay, I was really busy next week.
>
>Sato a écrit :
>
>
>>I drew a relationship between ResourceManager and db4o Local ECM Provider.
>>http://tmtec.biz/download/ResourceManager.jpg
>>Now that I have figured out an overview of ECM Resource
>>I'd like to know priorities ahead.
>>
>>
>>
>Great, thanks!
>(Sorry to not comment it, Bogdan is much more efficient for that
>
>
>
>>In order to pass the next phase(Creation Review?) of Eclipse Development Process,
>>what is important?
>>Reliable contributor names?
>>Reliable models?
>>Completeness of an initial implementation?
>>
>>
>>
>So most important is to improve specifications and start the code
>(detailled roadmap, etc.).
>Supporters are also important, but hopefully we have enough to start
>(Special thanks to you and db4o, btw).
>
>So it's time to improve technical specs and code components, now. The
>organization of the project will be improved by the time (following the
>Eclipse meritocratic model).
>To start to code, I propose to keep it simple for now: point an
>component you are interested in, write some technical specs and discuss
>them, code!
>
>
>
>>>I will look for an account on a demo CPS server and I will send you.
>>>
>>>
>>>
>>Can you send the account?
>>
>>
>The easiest and most efficient way for you to have a look at CPS is to
>download it (http://www.cps-project.org/) and install/run it.
>It's a 4 click install and run on windows.
>
>If you would like to access an online instance, I will send you the demo
>early this week (we are installing the CPS 3.4 demo site).
>
>
>Thanks for your work,
>
>EB.
>
>
>
--
Bogdan Stefanescu - Apogee project Team Leader
Nuxeo - Open Source ECM - www.nuxeo.com
Apogée - the rich client platform for ECM
http://apogee.nuxeo.org/ - http://www.nuxeo.com/en
_______________________________________________
Apogee mailing list
Apogee <at> lists.nuxeo.com
http://lists.nuxeo.com/cgi-bin/mailman/listinfo/apogee
_______________________________________________ Apogee mailing list Apogee@... http://lists.nuxeo.com/cgi-bin/mailman/listinfo/apogee
Hello all, As many people sugested, we have decided that Apogee must support JCR specs. This means a rework of the current resource model will be done this week (and may be the next week) The JCR model will not be used directly by the UI instead we are preserving the concepts already defined (that are inspired from eclipse model) on top of the JCR resources tree. This is so, because different JCR implementors may have different JCR repository structures, node types, mixin types and logic. So the only way to get an unified model is to make a small layer on top of the JCR that let the propgrammer access the JCR repositories managed by Apogee in a common way by the mean of IFile, IFolder and ISite handles. The ECM provider will need to handle the mapping between it's JCR node types and logic and the Apogee model. So a part of the current resource model will be refactored. The new model will not force an ECM provider to be JCR compatible (so the demo filesystem provider will normaly work with the new model) it only adds native support for JCR. Also the docs will be updated accordlying Regards, Bogdan
In fact, I found the problem, it seems it was a configuration problem. On my launching config, I did a "add required plugin" which resolve this problem.
Unfortunately, I now have a second problem, the following line throw a nullpointerexception setImageDescriptor(
Activator.getDefault().getImageRegistry().getDescriptor("icons.wizban.new_site"));
But commenting it solve this, so it's working, but maybe not as it should.
Thanx,
Nico
Hi Nicolas,
Nicolas a écrit :
> I was unable to test the filesystem provider, where do you configure
> apogee to add the new site wizard ?
I got the same problem this afternoon: did you checkout the
org.nuxeo.apogee.filesystem plugin ?
Regards
Cedric
_______________________________________________
Apogee mailing list
Apogee-FQDHc1wsLCVb90+sfpvX0g@public.gmane.org
http://lists.nuxeo.com/cgi-bin/mailman/listinfo/apogee
_______________________________________________ Apogee mailing list Apogee@... http://lists.nuxeo.com/cgi-bin/mailman/listinfo/apogee
RSS Feed
