[Zope3-dev] Zope and a RDB

2006-05-06 Thread John Catt
Hello,
JSR 170 

http://www.cmswatch.com/Feature/123
http://www.artima.com/lejava/articles/contentrepository3.html

seems to be the next standard of the CMS world.

Wouldn't be a good thing to make Zope 3 compatible with this standard ?

Thanks

- John
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com



Re: [Zope3-dev] Zope and a RDB

2006-05-06 Thread Andreas Jung



--On 6. Mai 2006 10:12:21 +0200 John Catt [EMAIL PROTECTED] wrote:


Hello,

JSR 170

http://www.cmswatch.com/Feature/123
http://www.artima.com/lejava/articles/contentrepository3.html

seems to be the next standard of the CMS world.

Wouldn't be a good thing to make Zope 3 compatible with this standard ?



I think Nuxeo with its Zope 3 ECM project is working on JSR 170 support.
See z3lab.org.

-aj

--
ZOPYX Ltd.  Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany
Web: www.zopyx.com - Email: [EMAIL PROTECTED] - Phone +49 - 7071 - 793376
E-Publishing, Python, Zope  Plone development, Consulting


pgpr2HOwXPxRU.pgp
Description: PGP signature
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com



Re: [Zope3-dev] Zope and a RDB

2006-05-06 Thread Fermigier Stefane

Andreas Jung wrote:



--On 6. Mai 2006 10:12:21 +0200 John Catt [EMAIL PROTECTED] wrote:


Hello,

JSR 170

http://www.cmswatch.com/Feature/123
http://www.artima.com/lejava/articles/contentrepository3.html

seems to be the next standard of the CMS world.

Wouldn't be a good thing to make Zope 3 compatible with this standard ?



I think Nuxeo with its Zope 3 ECM project is working on JSR 170 support.
See z3lab.org.


This was on of the subjects of a recent sprint in Paris, and one of the 
major change scheduled for CPS4.


You may find more information here:

http://blogs.nuxeo.com/sections/blogs/fermigier/2006_04_13_cps4-project-officially-started
http://blogs.nuxeo.com/sections/blogs/eric_barroca/2006_04_26_open-source-ecm-cps-platform-4-yellowcake-teaser
http://blogs.nuxeo.com/sections/blogs/fermigier/2006_04_19_cps4-z3ecm-sprint-day-1-short-report
http://blogs.nuxeo.com/sections/blogs/fermigier/2006_04_20_cps4-z3ecm-sprint-day-2-minimal-report
http://blogs.nuxeo.com/sections/blogs/fermigier/2006_04_20_cps4-z3ecm-sprint-day-2-short-report
http://blogs.nuxeo.com/sections/blogs/tarek_ziade/2006_04_25_cps4-z3ecm-sprint-final-wrapup
http://blogs.nuxeo.com/sections/blogs/ruslan_spivak/2006_04_28_here-we-go-java-content-repository-ice-connector

Feel free to join the CPS4 mailing list 
(http://lists.nuxeo.com/mailman/listinfo/cps4) if you want to contribute 
something very welcome, of course).


 S.

--
Stefane Fermigier - CEO, Nuxeo SAS - http://www.nuxeo.com/en/
Open Source ECM provider - http://www.cps-project.org 
Free soft. developer - http://blogs.nuxeo.com/sections/blogs/fermigier


___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com



[Zope3-dev] ImportError: cannot import name IObjectEvent when I install Zope3 Wiki 0.2.5

2006-05-06 Thread KLEIN Stéphane

Hi,

I've installed with success Zope 3.2.0 on Ubuntu from source (I haven't 
used Ubuntu Zope Package).


Now, I would like to install Zope3 Wiki 0.2.5 package. I've fetched wiki 
source from SVN. Next, I've put this file in /lib/python/ directory in 
my Zope instance : /var/zope/1/lib/python/zwiki/


Next, I've put zwiki-configure.zcml file in 
/var/zope/1/etc/package-includes/ directory. zwiki-configure.zcml contain :


include package=zwiki /

Now, when I restart zope (/var/zope/1/bin/runzope) I've this error :

  File 
/usr/local/src/Zope-3.2.0/build/lib.linux-i686-2.4/zope/configuration/config.py, 
line 184, in resolve

mod = __import__(mname, *_import_chickens)
  File /var/zope/1/lib/python/zwiki/interfaces.py, line 22, in ?
from zope.component.interfaces import IObjectEvent
zope.configuration.xmlconfig.ZopeXMLConfigurationError: File 
/var/zope/1/etc/site.zcml, line 7.2-7.55
ZopeXMLConfigurationError: File 
/var/zope/1/etc/package-includes/zwiki-configure.zcml, line 1.0-1.27
ZopeXMLConfigurationError: File 
/var/zope/1/lib/python/zwiki/configure.zcml, line 84.2-87.8

ImportError: cannot import name IObjectEvent

Full log in file joined.

Thanks for your help,
--Stéphane
  File ./runzope, line 48, in ?
run()
  File ./runzope, line 44, in run
main([-C, CONFIG_FILE] + sys.argv[1:])
  File 
/usr/local/src/Zope-3.2.0/build/lib.linux-i686-2.4/zope/app/twisted/main.py, 
line 74, in main
service = setup(load_options(args))
  File 
/usr/local/src/Zope-3.2.0/build/lib.linux-i686-2.4/zope/app/twisted/main.py, 
line 139, in setup
zope.app.appsetup.config(options.site_definition, features=features)
  File 
/usr/local/src/Zope-3.2.0/build/lib.linux-i686-2.4/zope/app/appsetup/appsetup.py,
 line 110, in config
context = xmlconfig.file(file, context=context, execute=execute)
  File 
/usr/local/src/Zope-3.2.0/build/lib.linux-i686-2.4/zope/configuration/xmlconfig.py,
 line 554, in file
include(context, name, package)
  File 
/usr/local/src/Zope-3.2.0/build/lib.linux-i686-2.4/zope/configuration/xmlconfig.py,
 line 490, in include
processxmlfile(f, context)
  File 
/usr/local/src/Zope-3.2.0/build/lib.linux-i686-2.4/zope/configuration/xmlconfig.py,
 line 345, in processxmlfile
parser.parse(src)
  File /usr/lib/python2.4/site-packages/_xmlplus/sax/expatreader.py, line 
109, in parse
xmlreader.IncrementalParser.parse(self, source)
  File /usr/lib/python2.4/site-packages/_xmlplus/sax/xmlreader.py, line 123, 
in parse
self.feed(buffer)
  File /usr/lib/python2.4/site-packages/_xmlplus/sax/expatreader.py, line 
216, in feed
self._parser.Parse(data, isFinal)
  File /usr/lib/python2.4/site-packages/_xmlplus/sax/expatreader.py, line 
364, in end_element_ns
self._cont_handler.endElementNS(pair, None)
  File 
/usr/local/src/Zope-3.2.0/build/lib.linux-i686-2.4/zope/configuration/xmlconfig.py,
 line 326, in endElementNS
self.context.end()
  File 
/usr/local/src/Zope-3.2.0/build/lib.linux-i686-2.4/zope/configuration/config.py,
 line 544, in end
self.stack.pop().finish()
  File 
/usr/local/src/Zope-3.2.0/build/lib.linux-i686-2.4/zope/configuration/config.py,
 line 690, in finish
actions = self.handler(context, **args)
  File 
/usr/local/src/Zope-3.2.0/build/lib.linux-i686-2.4/zope/configuration/xmlconfig.py,
 line 490, in include
processxmlfile(f, context)
  File 
/usr/local/src/Zope-3.2.0/build/lib.linux-i686-2.4/zope/configuration/xmlconfig.py,
 line 345, in processxmlfile
parser.parse(src)
  File /usr/lib/python2.4/site-packages/_xmlplus/sax/expatreader.py, line 
109, in parse
xmlreader.IncrementalParser.parse(self, source)
  File /usr/lib/python2.4/site-packages/_xmlplus/sax/xmlreader.py, line 123, 
in parse
self.feed(buffer)
  File /usr/lib/python2.4/site-packages/_xmlplus/sax/expatreader.py, line 
216, in feed
self._parser.Parse(data, isFinal)
  File /usr/lib/python2.4/site-packages/_xmlplus/sax/expatreader.py, line 
364, in end_element_ns
self._cont_handler.endElementNS(pair, None)
  File 
/usr/local/src/Zope-3.2.0/build/lib.linux-i686-2.4/zope/configuration/xmlconfig.py,
 line 326, in endElementNS
self.context.end()
  File 
/usr/local/src/Zope-3.2.0/build/lib.linux-i686-2.4/zope/configuration/config.py,
 line 544, in end
self.stack.pop().finish()
  File 
/usr/local/src/Zope-3.2.0/build/lib.linux-i686-2.4/zope/configuration/config.py,
 line 690, in finish
actions = self.handler(context, **args)
  File 
/usr/local/src/Zope-3.2.0/build/lib.linux-i686-2.4/zope/configuration/xmlconfig.py,
 line 490, in include
processxmlfile(f, context)
  File 
/usr/local/src/Zope-3.2.0/build/lib.linux-i686-2.4/zope/configuration/xmlconfig.py,
 line 345, in processxmlfile
parser.parse(src)
  File /usr/lib/python2.4/site-packages/_xmlplus/sax/expatreader.py, line 
109, in parse
xmlreader.IncrementalParser.parse(self, source)
  File /usr/lib/python2.4/site-packages/_xmlplus/sax/xmlreader.py, line 123, 
in parse

[Zope3-dev] SimpleKeyReference

2006-05-06 Thread Jean-Marc Orliaguet


Hi,

I have a use case for using key references to non-persistent objects, so 
I'd like to use: zope.app.keyreference.testing.SimpleKeyReference


but the import path is just a bit weird:
any problem with renaming: zope/app/keyreference/testing.py to 
zope/app/keyreference/simple.py ?


regards
/JM
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com



[Zope3-dev] Re: ImportError: cannot import name IObjectEvent when I install Zope3 Wiki 0.2.5

2006-05-06 Thread Philipp von Weitershausen
KLEIN Stéphane wrote:
 Hi,
 
 I've installed with success Zope 3.2.0 on Ubuntu from source (I haven't
 used Ubuntu Zope Package).
 
 Now, I would like to install Zope3 Wiki 0.2.5 package. I've fetched wiki
 source from SVN.

Moreover, you've fetched it from the 'trunk'. You should've fetched it
from the 3.2 branch. That's one is compatible with Zoep 3.2.x.


By the way, this is the wrong list...

Philipp

___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com



[Zope3-dev] Google SoC Project

2006-05-06 Thread Stephan Richter
Hey everyone,

Nate sent just a message that I am interested in a SoC project with the Plone 
Foundation. Okay, let me write something too.

I think doing a SoC project would be a lot of fun and would give me some time 
to work on Zope 3. Unfortunately, I am a little bit lost to what I could do 
that widely benefits Zope 3, Zope 2, CMF and Plone. Here are some of my 
ideas, some are stolen from the Plone project suggestions:

1. Finish the ZSCP site[1]

I think that the ZSCP process will be vital for controlling software quality 
in the future and provide people with a valuable resource for additional Zope 
software. My original proposal was modest by design, since I did not 
anticipate to have much time to work on a larger vision. With the SoC project 
I could finish the implementation of the proposal and extend the scope to be 
more inclusive of existing packages/products, especially with regard to 
Plone.

This project would fit the SoC program well, since its scope is well-defined 
and extensible.

.. [1] http://mail.zope.org/pipermail/zope3-dev/2006-February/018319.html

2. Implement Local Sites in ZCML

I already mentioned this several times: It would be very nice, if we could 
define local sites in ZCML. I understand this task very well and could write 
a proposal and implement it in a well-defined time frame. BTW, this task is a 
must happen, if we want to port something like Plone to Zope 3 eventually.

This project might be too short for the Google SoC. But I think it has a lot 
of potential.

3. Optimize ZCML

We talked about it many times. The startup time for Zope 3 is too long. In 
part this is due to the schema field conversion and verification of the ZCML 
attributes. I would like to work with Jim on some strategies to optimize the 
startup time by reducing the ZCML processing. Over the years we have thought 
of several solutions, but they all involved a lot of hard labor that noone 
was willing to do for free. Well, getting paid to do it, is a good 
motivator. ;-) Of course, this is also very important to the Plone people as 
more and more ZCML is being used.

I think that this project would have exactly the right timeframe and scope for 
a Google SoC project.

4. Implement a Query Framework and Language for Zope

Through my contract work I have recently played extensively with catalogs and 
indices in Zope 3. Furthermore I have used hurry.query for all my searches. I 
think hurry,query could be extended to become a full-featured query framework 
for Zope, including ad-hoc searches of objects. Furthermore, over and over 
again we get requests from people wanting to quickly query the ZODB (or at 
least the content space). I think it would be possible to build a query 
language on top of hurry.query.

This project would be somewhat experimental, but fit the spirit of Google's 
SoC.

5. Implement Portlets

Implement portlets in the sense of JSR 168. I think that a Zope portlet 
implementation in the spirit of JSR 168 is very feasible and would benefit a 
wide variety of Zope users. Achieving full JSR 168 compatibility is probably 
a lot more tricky and a risky objective, since I do not know the entire 
standard.

I think if the project would state that we try to implement portlets and only 
try to discover the feasibility of JSR 168 compliance, then this could be a 
decent S-C project. But I am not as thrilled about it, since it involves a 
standard. ;-)

That's it! Let me know, if you can think of any tasks that would bring us all 
forward.

Regards,
Stephan
-- 
Stephan Richter
CBU Physics  Chemistry (B.S.) / Tufts Physics (Ph.D. student)
Web2k - Web Software Design, Development and Training
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com



[Zope3-dev] Making a separate project for zope.bforest

2006-05-06 Thread Gary Poster
Hey all.  Seems like no-one but ZC has used zope.bforest, and it  
probably fits better in the a million itsy-bitsy projects story now  
that we have it (and an accompanying automated test story).  Anyone  
object if I move it out of the trunk?


Gary
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com



[Zope3-dev] Re: Google SoC Project

2006-05-06 Thread Martin Aspeli

Hi Stephan!

Nate sent just a message that I am interested in a SoC project with the  
Plone

Foundation. Okay, let me write something too.


It feels almost like cheating, since you're likely to know more than any  
potential mentor about the stuff you're working on, but I think it'd be a  
great idea to give you more time and compensation for contribution. ;-)


I think doing a SoC project would be a lot of fun and would give me some  
time
to work on Zope 3. Unfortunately, I am a little bit lost to what I could  
do

that widely benefits Zope 3, Zope 2, CMF and Plone. Here are some of my
ideas, some are stolen from the Plone project suggestions:


I think it's important (for Google) that it's the Plone Foundation that  
has been approved for mentorship, not Zope Corp or the Zope Foundation (if  
there is/will be such a thing...). That means that what you do under this  
guise needs to be directly relatable to and beneficial for Plone.



1. Finish the ZSCP site[1]

I think that the ZSCP process will be vital for controlling software  
quality
in the future and provide people with a valuable resource for additional  
Zope

software. My original proposal was modest by design, since I did not
anticipate to have much time to work on a larger vision. With the SoC  
project
I could finish the implementation of the proposal and extend the scope  
to be

more inclusive of existing packages/products, especially with regard to
Plone.

This project would fit the SoC program well, since its scope is  
well-defined

and extensible.

.. [1] http://mail.zope.org/pipermail/zope3-dev/2006-February/018319.html


I have two reservation about this - the first is that the process seems  
very arduous (i.e. there are a *lot* of tickboxes in that table, and there  
is the potential to create a lot of red tape). The second is that without  
a large amount of buy-in from the wider community (and in the context of  
SoC, that means primarily the Plone community), it won't gain the  
necessary traction to be relevant.


To be sure, I support the principle of the ZSCP, but it is a very hard  
*social* problem (as opposed to a purely technical one) that may not fit  
the model of a single student working on it for a few months.


As I recall, much of the process was also biased (for good reasons!)  
towards pure Zope 3 products, which may actually mean that the majority of  
Plone components could never fully comply with the standard... which in  
turn doesn't make for a great case of the Plone Foundation Summer-of-Code  
application. :)



2. Implement Local Sites in ZCML

I already mentioned this several times: It would be very nice, if we  
could
define local sites in ZCML. I understand this task very well and could  
write
a proposal and implement it in a well-defined time frame. BTW, this task  
is a
must happen, if we want to port something like Plone to Zope 3  
eventually.


This project might be too short for the Google SoC. But I think it has a  
lot

of potential.


I think that anything that solves one or two of these for Zope 3 would be  
highly relevant to Plone:


 - Local-ness - everything in CMF/Plone is about local. Only when  
product X is installed should X's functionality be exposed, and before X  
is installed, something that's registered in ZCML or whatnot could  
possibly break. People expect to have several Plone sites in one Zope  
instance and configure them differently.


I'm not entirely sure how this fits with ZCML, though, since ZCML is  
inherently global (i.e. we can't hard-code site names in ZCML ;-), but I'm  
guessing you're talking about a more generalisable way to install things  
locally and have things only take effect when locally enabled?


 - Through-the-web customisability of *templates*. I'm not convinced we  
need TTW-classes and components and logic - those things fit progammer  
minds and programmer minds don't mind filesystems and like svn. But people  
using Plone are *very often* drawn to it because the ease with which they  
can override/customise page templates (and by extension visual logic,  
layout, etc.) without leaving their web browser or learn a large stack of  
technologies. It's not an ideal model, and we need good ways of getting  
out of the ZODB and into a skin product or similar. But we are extremely  
reluctant to make use of views with page templates (as opposed to page  
templates that acquire views and then call its methods) in Plone precisely  
because it means sacrificing TTW customisability.



3. Optimize ZCML

We talked about it many times. The startup time for Zope 3 is too long.  
In
part this is due to the schema field conversion and verification of the  
ZCML
attributes. I would like to work with Jim on some strategies to optimize  
the
startup time by reducing the ZCML processing. Over the years we have  
thought
of several solutions, but they all involved a lot of hard labor that  
noone

was willing to do for free. Well, getting paid to do it, is a 

[Zope3-dev] Re: Making a separate project for zope.bforest

2006-05-06 Thread Martin Aspeli

On Sat, 06 May 2006 21:14:57 +0100, Gary Poster [EMAIL PROTECTED] wrote:

Hey all.  Seems like no-one but ZC has used zope.bforest, and it  
probably fits better in the a million itsy-bitsy projects story now  
that we have it (and an accompanying automated test story).  Anyone  
object if I move it out of the trunk?


A b-forest? That's like so many b-trees you can't see it for them?

Martin



--
You can just adapt yourself out of it... // Archipelago sprint 26/04/2006

___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com



Re: [Zope3-dev] Re: Making a separate project for zope.bforest

2006-05-06 Thread Gary Poster


On May 6, 2006, at 6:13 PM, Martin Aspeli wrote:


On Sat, 06 May 2006 21:14:57 +0100, Gary Poster [EMAIL PROTECTED] wrote:

Hey all.  Seems like no-one but ZC has used zope.bforest, and it  
probably fits better in the a million itsy-bitsy projects story  
now that we have it (and an accompanying automated test story).   
Anyone object if I move it out of the trunk?


A b-forest? That's like so many b-trees you can't see it for them?


:-)

Yes, it's a simple, reasonably-well-tested building block that  
aggregates multiple btrees into a single dict-like interface.  You  
can decide whether you want to see the trees, or the forest.


We've used it for two very different purposes:

- the guts for simple rotating caches (here, the forest is the  
engine for the public API, and the trees are just used internally  
as the buckets that can be cleared and rotated);


- the guts for an object that should be seen both as an aggregated  
container for all jobs, and as an object with two discrete child  
containers for active jobs and for completed jobs, respectively.


I think many of us have written similar code (especially the cache  
with rotating buckets).  It's simple code.  It's a generic task,  
though, so why not start with a shared, tested engine?


But anyway, it's only in the core because we didn't have the mini- 
package story when we packaged it: it's never been in a release, AFAIK.


Gary
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com