[Zope-Annce] CPS 3.4.0 released!
-- Stéfane Fermigier, Tel: +33 (0)6 63 04 12 77 (mobile). Nuxeo Collaborative Portal Server: http://www.nuxeo.com/cps Gestion de contenu web / portail collaboratif / groupware / open source! CPS 3.4.0 released! === After 1 year and 1/2 of hard work (more than 11000 commits by 32 developers), Nuxeo is pleased to announce, on behalf of the CPS developers community, the release of CPS 3.4.0, the new stable version of CPS, the open source ECM platform. Source code is available here: http://www.cps-project.org/static/src/ or http://www.cps-project.org/sections/downloads/ A binary installer for Windows (includes Zope 2.9.1) here: http://www.cps-project.org/static/windows/CPS-3.4.0-1.exe And other binaries are planned for release in a few days (including MacOS). Please read the following for more information on CPS and CPS 3.4. What is CPS? CPS is an Open Source Enterprise Content Management (ECM) platform that provides developers with a rich toolkit to create applications in the fields of: Web Content Management (WCM), Document Management (DM), Collaboration (CSCW), Workflow and Business Process Management (BPM) and corporate portals. CPS may be compared to proprietary solutions like Documentum by EMC, LiveLink by OpenText, or SharePoint by Microsoft. For more information, check: - Marketing material at: http://www.nuxeo.com/en/products/cps/ What's new? --- A lot of things have changed since the previous major stable release, CPS 3.2, in september 2004. Here are the most important ones. User-visible changes 1. A new default UI, that features both usability improvement and a better-looking default skin. This makes working with CPS a more enjoyable experience for end-users. 2. Switch from HTML 4.01 Transitional to XHTML 1.0 Strict, with work on accessibility (A-level by default, AA and AAA-level possible at the expense of some features). 3. AJAXification: use of AJAX techniques for a more responsive and more powerful UI (asynchronous form updates). 4. CPSSkins, which is a very powerful web-based WYSIWYG theme editor for CMF-based applications, has been integrated. It makes it easy for graphic designers or webmasters to modify the look of CPS without writing CSS or template code. 5. CPSPortlets, a web-based WYSIWYG portlet editor that makes it easy for content administrators to modify the presentation of information on a CPS site. 6. New applicative products have been added to the CPS default application: CPSBlog (for blogs), CPSWiki (for wikis), CPSOOo (to manage OpenOffice.org documents). 7. The webmail and shared calendar components have been completely rewritten. They are available as separate packages. 8. CPSGeo, a GIS product for CPS that allows for geolocation of documents in a CPS application. It is available as a separate package. Architecture changes 1. We have switched to recent versions of Zope (2.9) and CMF (1.6). 2. We have switched most new developments to the Zope 3 component architecture, thanks to Five, the bridge between Zope 2 and Zope 3. 3. We now use of GenericSetup, the new default, XML-based, configuration tool, instead of CPSInstaller. Using declarative configuration makes it now much easier to manage upgrades between versions 4. We have switched the unit and functional test harnesses to the Zope 2.9 layer-based test runner. This eases the creation and speeds up the execution for the 2543 tests included in the CPS source code so far. 5. We now use CPSUserFolder as a powerful replacement to UserFolder. CPSUserFolder makes it possible to use a user directory managed by CPSDirectory as a source of users in CPS. 6. DCWorkflow has been extended as CPSWorkflow to provide a document-based workflow engine with dynamic schemas support (inspired by the activity-based workflow model) that can handle any document-based business process. This hybrid model gives all the power and flexibility needed to define dynamic validation / review / delegation states to model any paper process you have in the real world, while keeping workflow modeling simple enough to be easily understood by users. 7. CPSRemoteController provides a Web Service interface to remotely control CPS portals (both from another CPS portal or from totally different applications) in a language-independent manner through XML-RPC. CPSRemoteController is also very handy for task automation. 8. CPSRelation provides a tool that manages RDF relations between content objects. 9. Many, speed optimisations, at both low level (including work on ZODB transactions and CPSCore internal optimizations) and high level (rendering of CPSDocument and CPSPortlets caches) to make it possible to manage applications with hundreds of thousands of documents (soon: millions of documents) and tens of gigabytes of data (soon: terabytes of data).
[Zope-Checkins] SVN: Zope/branches/Zope-2_8-branch/lib/python/OFS/Cache.py Provide missing security declarations for 'ZCacheable_isAMethod'
Log message for revision 65847:
Provide missing security declarations for 'ZCacheable_isAMethod'
and 'ZCacheable_getManagerURL'.
Changed:
U Zope/branches/Zope-2_8-branch/lib/python/OFS/Cache.py
-=-
Modified: Zope/branches/Zope-2_8-branch/lib/python/OFS/Cache.py
===
--- Zope/branches/Zope-2_8-branch/lib/python/OFS/Cache.py 2006-03-07
04:58:13 UTC (rev 65846)
+++ Zope/branches/Zope-2_8-branch/lib/python/OFS/Cache.py 2006-03-07
10:38:14 UTC (rev 65847)
@@ -94,6 +94,8 @@
'ZCacheable_getManagerId',
'ZCacheable_getManagerIds',
'ZCacheable_configHTML',
+ 'ZCacheable_isAMethod',
+ 'ZCacheable_getManagerURL',
)),
(ChangeCacheSettingsPermission,
('ZCacheable_setManagerId',
___
Zope-Checkins maillist - Zope-Checkins@zope.org
http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/philikon-local-components/ Branch for some minor modifications to Zope 2 regarding the work on local
Log message for revision 65856: Branch for some minor modifications to Zope 2 regarding the work on local component registration. They're minor, but break Five tests, hence the branch. Changed: A Zope/branches/philikon-local-components/ -=- Copied: Zope/branches/philikon-local-components (from rev 65855, Zope/trunk) ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/philikon-local-components/lib/python/zope/ Switch some essential zope.* packages to Jim's adapter branch
Log message for revision 65857: Switch some essential zope.* packages to Jim's adapter branch Changed: _U Zope/branches/philikon-local-components/lib/python/zope/ -=- Property changes on: Zope/branches/philikon-local-components/lib/python/zope ___ Name: svn:externals - app -r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/app cachedescriptors -r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/cachedescriptors component-r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/component configuration-r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/configuration documenttemplate -r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/documenttemplate event-r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/event exceptions -r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/exceptions hookable -r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/hookable i18n -r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/i18n i18nmessageid-r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/i18nmessageid interface-r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/interface modulealias -r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/modulealias pagetemplate -r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/pagetemplate proxy-r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/proxy publisher-r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/publisher schema -r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/schema security -r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/security server -r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/server structuredtext -r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/structuredtext tal -r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/tal tales-r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/tales testing -r 40941 svn://svn.zope.org/repos/main/zope.testing/trunk/src/zope/testing thread -r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/thread deprecation -r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/deprecation dottedname -r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/dottedname formlib -r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/formlib index-r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/index testbrowser -r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/testbrowser + app svn://svn.zope.org/repos/main/Zope3/branches/jim-adapter/src/zope/app cachedescriptors -r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/cachedescriptors component svn://svn.zope.org/repos/main/Zope3/branches/jim-adapter/src/zope/component configuration-r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/configuration documenttemplate -r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/documenttemplate event-r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/event exceptions -r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/exceptions hookable -r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/hookable i18n -r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/i18n i18nmessageid-r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/i18nmessageid interface svn://svn.zope.org/repos/main/Zope3/branches/jim-adapter/src/zope/interface modulealias -r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/modulealias pagetemplate -r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/pagetemplate proxy-r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/proxy publisher-r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/publisher schema -r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/schema security -r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/security server -r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/server structuredtext -r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/structuredtext tal -r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/tal tales-r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/tales testing -r 40941 svn://svn.zope.org/repos/main/zope.testing/trunk/src/zope/testing thread -r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/thread deprecation -r 41215 svn://svn.zope.org/repos/main/Zope3/trunk/src/zope/deprecation dottedname -r 41215
[Zope-Checkins] SVN: Zope/branches/philikon-local-components/lib/python/Products/ Switch included Five to local component branch so people can check it out
Log message for revision 65858: Switch included Five to local component branch so people can check it out more easily. Changed: _U Zope/branches/philikon-local-components/lib/python/Products/ -=- Property changes on: Zope/branches/philikon-local-components/lib/python/Products ___ Name: svn:externals - Five svn://svn.zope.org/repos/main/Products.Five/tags/1.3.2 + Five svn://svn.zope.org/repos/main/Products.Five/branches/philikon-local-components ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/philikon-local-components/lib/python/OFS/ Make ObjectManager an IPossibleSite.
Log message for revision 65859:
Make ObjectManager an IPossibleSite.
Changed:
U Zope/branches/philikon-local-components/lib/python/OFS/ObjectManager.py
U Zope/branches/philikon-local-components/lib/python/OFS/interfaces.py
-=-
Modified:
Zope/branches/philikon-local-components/lib/python/OFS/ObjectManager.py
===
--- Zope/branches/philikon-local-components/lib/python/OFS/ObjectManager.py
2006-03-07 16:27:21 UTC (rev 65858)
+++ Zope/branches/philikon-local-components/lib/python/OFS/ObjectManager.py
2006-03-07 16:28:46 UTC (rev 65859)
@@ -46,6 +46,7 @@
from ZODB.POSException import ConflictError
from zope.interface import implements
+from zope.component.interfaces import ComponentLookupError
import CopySupport
from interfaces import IObjectManager
@@ -166,6 +167,19 @@
isPrincipiaFolderish=1
+# IPossibleSite API
+
+_components = None
+
+def getSiteManager(self):
+if self._components is None:
+raise ComponentLookupError('No component registry defined.')
+return self._components
+
+def setSiteManager(self, components):
+self._components = components
+
+
def __class_init__(self):
try:mt=list(self.meta_types)
except: mt=[]
Modified: Zope/branches/philikon-local-components/lib/python/OFS/interfaces.py
===
--- Zope/branches/philikon-local-components/lib/python/OFS/interfaces.py
2006-03-07 16:27:21 UTC (rev 65858)
+++ Zope/branches/philikon-local-components/lib/python/OFS/interfaces.py
2006-03-07 16:28:46 UTC (rev 65859)
@@ -28,6 +28,7 @@
from webdav.interfaces import IDAVResource
from zope.app.traversing.interfaces import IContainmentRoot
+from zope.app.component.interfaces import IPossibleSite
class IOrderedContainer(Interface):
@@ -476,13 +477,12 @@
# not synced with ZopeBook API Reference;
# based on OFS.ObjectManager.ObjectManager
class IObjectManager(IZopeObject, ICopyContainer, INavigation, IManageable,
- IAcquirer, IPersistent, IDAVCollection, ITraversable):
-
+ IAcquirer, IPersistent, IDAVCollection, ITraversable,
+ IPossibleSite):
Generic object manager
This interface provides core behavior for collections of heterogeneous
-objects.
-
+objects.
meta_types = Tuple(
title=uMeta types,
___
Zope-Checkins maillist - Zope-Checkins@zope.org
http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/trunk/lib/python/OFS/Image.py OFS.Image: 'Image.update_data' did not refresh the Etag.
Log message for revision 65865: OFS.Image: 'Image.update_data' did not refresh the Etag. Changed: U Zope/trunk/lib/python/OFS/Image.py -=- Modified: Zope/trunk/lib/python/OFS/Image.py === --- Zope/trunk/lib/python/OFS/Image.py 2006-03-07 21:54:54 UTC (rev 65864) +++ Zope/trunk/lib/python/OFS/Image.py 2006-03-07 21:55:56 UTC (rev 65865) @@ -794,6 +794,7 @@ self.ZCacheable_invalidate() self.ZCacheable_set(None) +self.http__refreshEtag() def __str__(self): return self.tag() ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] CVS: Cruft/ExtensionClass/src - Acquisition.c:1.61.4.1.32.1
Update of /cvs-repository/Cruft/ExtensionClass/src
In directory cvs.zope.org:/tmp/cvs-serv6895
Modified Files:
Tag: zc-Zope-2-7-5
Acquisition.c
Log Message:
Backported fix fromn trunk. The simplification of wrappers is not
merely an optimization. It is critical for getting correct wrapper
semantics.
=== Cruft/ExtensionClass/src/Acquisition.c 1.61.4.1 = 1.61.4.1.32.1 ===
--- Cruft/ExtensionClass/src/Acquisition.c:1.61.4.1 Tue Oct 21 08:44:39 2003
+++ Cruft/ExtensionClass/src/Acquisition.c Tue Mar 7 17:56:25 2006
@@ -138,39 +138,6 @@
/* */
-static PyObject *
-__of__(PyObject *inst, PyObject *parent)
-{
- PyObject *r, *t;
-
- UNLESS(r=PyObject_GetAttr(inst, py__of__)) return NULL;
- UNLESS(t=PyTuple_New(1)) goto err;
- PyTuple_SET_ITEM(t,0,parent);
- ASSIGN(r,PyObject_CallObject(r,t));
- PyTuple_SET_ITEM(t,0,NULL);
- Py_DECREF(t);
-
- if (r
- r-ob_refcnt==1
- isWrapper(r)
- WRAPPER(r)-container isWrapper(WRAPPER(r)-container)
- )
-while (WRAPPER(r)-obj isWrapper(WRAPPER(r)-obj)
- (WRAPPER(WRAPPER(r)-obj)-container ==
- WRAPPER(WRAPPER(r)-container)-obj)
- )
- {
- /* Simplify wrapper */
- Py_XINCREF(WRAPPER(WRAPPER(r)-obj)-obj);
- ASSIGN(WRAPPER(r)-obj, WRAPPER(WRAPPER(r)-obj)-obj);
- }
-
- return r;
-err:
- Py_DECREF(r);
- return NULL;
-}
-
static Wrapper *freeWrappers=0;
static int nWrappers=0;
#define MAX_CACHED_WRAPPERS 200
@@ -227,6 +194,49 @@
{
PyObject_DEL(self);
}
+}
+
+static PyObject *
+__of__(PyObject *inst, PyObject *parent)
+{
+ PyObject *r, *t;
+
+ UNLESS(r=PyObject_GetAttr(inst, py__of__)) return NULL;
+ UNLESS(t=PyTuple_New(1)) goto err;
+ Py_INCREF(parent);
+ PyTuple_SET_ITEM(t,0,parent);
+ ASSIGN(r,PyObject_CallObject(r,t));
+ Py_DECREF(t);
+
+ if (r != NULL
+ isWrapper(r)
+ WRAPPER(r)-container isWrapper(WRAPPER(r)-container)
+ )
+while (WRAPPER(r)-obj isWrapper(WRAPPER(r)-obj)
+ (WRAPPER(WRAPPER(r)-obj)-container ==
+ WRAPPER(WRAPPER(r)-container)-obj)
+ )
+ {
+if (r-ob_refcnt !=1 )
+ {
+t = newWrapper(WRAPPER(r)-obj,
+ WRAPPER(r)-container,
+ (r-ob_type));
+Py_DECREF(r);
+if (t==NULL)
+ return NULL;
+r = t;
+ }
+
+/* Simplify wrapper */
+Py_XINCREF(WRAPPER(WRAPPER(r)-obj)-obj);
+ASSIGN(WRAPPER(r)-obj, WRAPPER(WRAPPER(r)-obj)-obj);
+ }
+
+ return r;
+err:
+ Py_DECREF(r);
+ return NULL;
}
static PyObject *
___
Zope-Checkins maillist - Zope-Checkins@zope.org
http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-dev] Re: http access to svn repos?
Tres Seaver wrote: Where should I write the proposal? Who is going to review it? http://www.zope.org/Wikis/DevSite/Proposals ; post here and zope3-dev for review. yay! a wiki... oh the joy... You need to identify potential issues, document any changes needed to the Apache config (to enable the DAV verbs, for instance), and spell out how to revert it; then get the rest of the community to accept it, at least tacitly. *sigh* red tape wins again. It's much easier to just do nothing, and just not be able to contribute from behind a firewall... The issues aren't so much technical feasibility as social / legal: a checkin done using somebody's private key is way less deniable than one done with a password. Unless you plan to set up a system for issuing client certificates to contributors, I don't think https is superior to svn+ssh at all. Hmmm, I'm tempted to call BS on this. How much of this has actually been tested in a court? Really, all this crap gets caught up on pseudo legal BS which ultimately just makes it more difficult for people to contribute :-( I really don't get the whole paranoia about passwords anyway... yes, client certs and public key are more secure, but really, why are we setting the bar so high? It's not like we're dealing with top secret national security stuff... yes, this sucks :-/ It's *by design*. OK, as a concrete example, the guys at my current big project have effectively donated a full MSDN license so I can pick up doing the Windows builds and give Tim a break. But, because they're a bank, they care about security and so don't let any old protocol through their firewalls... http and https are fine, I can check into or out of my own repository, and any other repo running a standard protocol. However, zope.org insists on using the esoteric svn+ssh protocol for write access (which you have to jump through all sorts of hoops to get working on Windows anyway :-/) and the getting-used-less-and-less svn protocol which is just flat blocked by large and immovable firewalls... For trying to get people to help out, this sucks ass. Come on, we're an open source project, we _want_ people to help out, not keep on pushing them away with higher and higher bars :-( Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Principles
Hi there, Geoff Davis wrote: I am very glad to see that Jim's efforts to better articulate a vision for Zope have generated so much interest. I am not so sure that the discussion has been an entirely productive one. I think that we as a community would benefit by working on our social engineering as much as our software engineering. Heh. Yeah. :) [snip] One of the things that GTY recommends is to establish a set of agreed upon principles for evaluating proposals. I think that having such a set of principles would help us better focus our current discussion. Agreed. Let's take a step back from the particulars of the various proposals floating around and see if we can nail down some principles. Here is a very rough, very incomplete start: One thing about these principles is weight. Even if we all agree, some may think one principle is more important than another. Should one principle be able to trump another one? 1. Zope should have a clear message about where we are going. I'm sure we all agree on this, but this is so broad that it is not very useful. Here's a stab at refining it: 1.1 We should have a clear message about where Zope 2 is going. The message should give existing and prospective Zope 2 users an idea of how long their code will continue to work on releases in the Zope 2 path and what kind of upgrade process they will face as the Zope 2 line evolves. 1.2 Ditto for Zope 3. +1 2. Zope should try to expand its developer base. Again, I am sure we all agree, but this is too broad to be useful. 2.1 Zope should leverage the work of others by moving toward an architecture that allows one to easily use code from outside Zope. +1 This effectively increases the developer base by letting us leverage the work of others outside the immediate Zope community. I assume that this (and integration) are the primary motivations driving the CA. I don't think that's the only motivation driving the CA. A very important motivation of the CA in my book is extensibility and evolution. Using the CA makes it easier to evolve existing codebases by extending them in all kinds of ways. 2.2 Zope should be useful for developers not using the full application server stack. Again, this serves to increase our developer base by drawing in people outside our traditional core audience. +1 I'll add a few related principles that have a different perspective: * Zope should aim not to reinvent the wheel. Instead we should leverage code outside of Zope in Zope itself. * Zope should play friendly with the Python community * We want to engage the Python community and use Python community code, engaging in non-zope communities. * We want the Python community to use more code spun off Zope, and have them engage into our community. And one more that came up a lot: * We want to cater better to a set of developers left in the cold by Zope 3. We probably need some principles about the Zope brand, and so on, but I think this should serve as a useful starting point. * We want the strengthen the brand of our software. * of the software we call Zope 2 * of the software we call Zope 3 * of the components that Zope 3 is composed of * We want to strengthen the brand named Zope. * the Zope 2 brand. * the Zope 3 brand. * the Zope without 2 or 3 brand. * We want to use the strengths of the Zope brand in our communication. * We want to capitalize on technical strengths. * We want to capitalize experience and maturity. * Extended CMS features. * We want to counter the weaknesses of the Zope brand. * We want to counter the crufty, overly complex reputation that Zope has in the Python community. * We want to counter the reputation in the Python community that Zope is off on its own. * We want to avoid the weaknesses of the Zope brand. * In particular, the cruftly, overly complex reputation that Zope has in the Python community. * We don't want to weaken the Zope brand. * We don't want to give the impression we promise features that we end up not delivering. * We don't want to give the impression we promise features soon that we end up delivering only very much later. Note that these principles can all lead to quite different conclusions, but it's indeed good to articulate them. Let's see if we can expand and refine these principles before going down the vision road. I think that we will find that once we have articulated a set of core principles, defining a vision that adheres to them will be much easier. Very good initiative! I'll leave it up to you Geoff to see whether you want to adopt some of the principles I listed in a larger document and give them a canonical number. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists -
[Zope-dev] Re: [Zope3-dev] Two visions
On Mar 6, 2006, at 9:21 PM, Jake wrote: I think it is a huge mistake to lose Zope branding. After years of building up momentum behind a project, to head off into some strange developer code speak is just going to lose people who are not intimately involved. The world, after many years, gets versions. Stick to it. Works: Mac OS9 - Mac OSX (10) Here was a mistake: Mosaic - Netscape - Netscape Communicator - Netscape Gold - Firebird - Mozilla - Firefox Considering Firefox has nearly 15% marketshare today, I'd call it a success. It certainly could have been worse had Netscape not done the hail mary of releasing it under another name that wasn't conflated with its own brand (witness the takeup rate of Netscape 6/7). - C ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] http access to svn repos?
Chris Withers wrote: Hi All, Would anyone be averse to making anonymous http checkouts possible from zope.org? Not in principle. In fact, I would find it convenient for a particular project. I doubt that anyone with access to that machine has time, \ although I can only speak for myself. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: http access to svn repos?
Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris Withers wrote: Would anyone be averse to making anonymous http checkouts possible from zope.org? Some of us are behind annoying proxies that won't let svn through :-/ At one point, enabling the 'http:' checkout gateway was a sure-fire recipe for getting SVN's knickers in a twist, which is why we disabled it. Or maybe that was ViewCSV. Actually, it was BekeleyDB. :) The main obstical was that it required apache 2 and, at the time we were running apache 1 and I didn't want to spend the time figuring out the apache access. In any case, I would guess that you might persuade folks to allow DAV-based checkout (which is what svn-over-http is), but you are likely to have to write it up as a proposal, including specific information about the Apache / SVN configuration changes required. PS: https write access would be nice, but I guess that's out of the question? Yes, definitely. The answer is the same as when you asked for it two years ago (: the WebDAV stuff is slow (which may be a reason not to allow annonymous http: checkouts, too), and the credentials mechanism is built entirely around the contributor's SSH key.. I would support HTTP anonymous checkouts. I'm really against writable HTTP checkouts because I consider the credentials mechanism for HTTP access to be extremely lame. Despite out lame program for uploading keys, I find the ssh-based access mechanism to be far more usable and secure. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Redirect Exception and Five
Hi all, I have a problem developing a Product using Five.When a Redirect Exception is raised from a PluggableUserFolder inside my product, it is not handled by the publisher, and I have an error message instead a browser redirect. The same test inside a normal Folder works fine. I'm using Zope 2.9.0, and tried to add this ZCML statements, but I've no luck, and I can't find any other message talking about this. five:traversable class=OFS.Application.Application/ five:traversable class=OFS.Folder.Folder/ five:traversable class=zExceptions.Redirect/ five:traversable class=Products.PluggableUserFolder.PluggableUserFolder.PluggableUserFolder/ five:traversable class=.folder.APWebFolder/ Anybody knows what could happen ? Thanks -- Santi Camps Earcon S.L. - http://www.earcon.com - http://www.kmkey.com ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [ZWeb] version3
On 3/7/06, Tom Von Lahndorff [EMAIL PROTECTED] wrote: The latest and greatest. I'm working on the middle content well, but the rest is pretty much done, including the nav. It is really great looking! But do we need menus, It doesn't hurt usability though, IMO. (I am not a usability expert) Regards, Baiju M ___ Zope-web maillist - Zope-web@zope.org http://mail.zope.org/mailman/listinfo/zope-web
Re: [ZWeb] version3
On Tue, 07 Mar 2006 07:10:07 -0500, Tom Von Lahndorff wrote The latest and greatest. I'm working on the middle content well, but the rest is pretty much done, including the nav. http://www.modscape.com/zope wow that really is so much better than what we have now.. great work! ___ Zope-web maillist - Zope-web@zope.org http://mail.zope.org/mailman/listinfo/zope-web -- NSTP (M) BHD ___ Zope-web maillist - Zope-web@zope.org http://mail.zope.org/mailman/listinfo/zope-web
Re: [ZWeb] version3
On 3/7/06, baiju m [EMAIL PROTECTED] wrote: But do we need menus, It doesn't hurt usability though, IMO. It is important that in every menu, the main item should be clickable and go to a page where you can select all of the subitems, in case you are on a browser that desn't support JS, or sucks. If this is true, then menus are acceptable. -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/ ___ Zope-web maillist - Zope-web@zope.org http://mail.zope.org/mailman/listinfo/zope-web
Re: [Zope] newbie Simple WebSite Construction Using Zope and Search
Hello Matt, I did something similar a few years ago when we had to merge a number of web-sites, and needed to enable content providers who could not be expected to cope with much more than heading and paragraph tags. The users are very pleased with the site functionality - but the implementation displays my then inexperience with Python and Zope, so could not be packaged for others to use. So I have been working on a Zope 3 implementation, which I hope to make available within a couple of weeks. You can have a look at the Zope 2 site I created (for whatever reason I did not what to use CMS or Plone): http://www.geos.ed.ac.uk/ And this is a screen grab of the Zope 3 package with similar functionality as it stands at the moment: http://www.geos.ed.ac.uk/homes/ceford/zope3/ So I can't answer your questions directly, but: My Zope 2 site used a lot of dtml documents as page components. In Zope 3 I have only used Page Templates. In my Zope 2 site searches also find dtml documents, so I provide a custom display that puts in links to the pages that put the dtml in the right context. E.g. if a search finds a dtml document called page.bdy the link displayed is page.html. Best regards Cliff Ford Matt Slavin wrote: Hi, I am trying to use Zope to create a very simple company website (about 40 pages, or so) with the intention of having the flexibility to expand functionality etc in due course. I have very little Python / DTML experience, but have managed to set up the site using includes on the main index page and then use aquisition to provide the content within each section. I'm not sure if this is a safe - or correct way of going about it, but it seems ideal for our purposes. The navigational menus dynamically include a link to each sub folder - ie website/services/ - and navigating to a section, index_html is automatically shown. The mainContent variable is then dynamically placed into index_html. (So there are separate mainContent dtmlDocuments in About Us, Services etc..) This means we can keep the content completely separate, and do not have to include headers, footers and other includes within the mainContent variable. Brilliant. However, when using the search script - http://www.zope.org/Members/Ioan/SiteSearch - results return a link back to the dtml_Document file mainContent, which gets displayed without any of the header of footer information. Is there any way to render the page with header and footer info? (By, I guess, redirecting the page to the containing folder, so that it pulls out index_html instead...) Any thoughts on this would be gratefully received - as I'm not sure this is the best way of using Zope, but it seems so much better than using plain old included variables. kind regards, Matt - Yahoo! Cars NEW - sell your car and browse thousands of new and used cars online search now - ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev ) ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] newbie Simple WebSite Construction Using Zope and Search
Hi Matt, Matt Slavin wrote: expand functionality etc in due course. I have very little Python / DTML experience, but have managed to set up the site using Don't torture yourself, use ZPT and not DTML... includes on the main index page and then use aquisition to provide the content within each section. Usually you use acquisition to get the templates and have your content be the structure of the site... However, when using the search script - http://www.zope.org/Members/Ioan/SiteSearch - results return a link back to the dtml_Document file mainContent, which gets displayed without any of the header of footer information. Is there any way to render the page with header and footer info? (By, I guess, redirecting the page to the containing folder, so that it pulls out index_html instead...) Just fiddle in your results method so it generates the correct url.. Sounds like: whatever.aq_parent.absolute_url() ...should get you what you need :-) cheers, Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] (microsoft) webdav and zope 2.8.4
Dieter Maurer wrote: Really? I thought the contributor agreement had already been changed to remove the clauses you find offensive? These are still proposals -- still not effective. *sigh* So while everyone is busy talking about visions on a dev list, important stuff like getting you to be able to commit feels like it's getting sidelined :-( If your read the foundation's policy you will find something like: Becoming a contributor is an honour ... You need to be invited. ... Intially, the foundation assigns initial contributors who may invite additional ones. Well, if no-one else does, _I'll_ damn well invite you :-D Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Using PUT_factory for objects outside of ZODB
I want to be able to intercept PUT requests to Zope to store objects outside of the ZODB by storing the body of the PUT request in an SQL database. I've written a PUT_factory external method that calls the function PUT_ParameterFile defined below: == [...boilerplate Zope imports...] class ParameterFile(Implicit): security = ClassSecurityInfo() security.declareObjectPublic() security.setDefaultAccess(allow) def __init__(self, context, job_batch_id, body): self.context = context self.job_batch_id = job_batch_id self.body = body def PUT(self, REQUEST, RESPONSE): self.context.SQL_UpdateJobBatchParameterFile( job_batch_id=self.job_batch_id, parameter_file=self.body) RESPONSE.setStatus(204) return RESPONSE def PUT_ParameterFile(self, name, typ, body): if typ == text/plain: return ParameterFile(self, name, body) = The ParameterFile.PUT method is being called, but then Zope returns w/ the error Can't pickle extension class __builtin__.ParameterFile at 72918728: attribute lookup __builtin__.ParameterFile failed. Why is Zope trying to pickle the ParameterFile object when it's handling PUT itself? TIA, John ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Re: Using PUT_factory for objects outside of ZODB
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 John Barham wrote: I want to be able to intercept PUT requests to Zope to store objects outside of the ZODB by storing the body of the PUT request in an SQL database. I've written a PUT_factory external method that calls the function PUT_ParameterFile defined below: == [...boilerplate Zope imports...] class ParameterFile(Implicit): security = ClassSecurityInfo() security.declareObjectPublic() security.setDefaultAccess(allow) def __init__(self, context, job_batch_id, body): self.context = context self.job_batch_id = job_batch_id self.body = body def PUT(self, REQUEST, RESPONSE): self.context.SQL_UpdateJobBatchParameterFile( job_batch_id=self.job_batch_id, parameter_file=self.body) RESPONSE.setStatus(204) return RESPONSE def PUT_ParameterFile(self, name, typ, body): if typ == text/plain: return ParameterFile(self, name, body) = The ParameterFile.PUT method is being called, but then Zope returns w/ the error Can't pickle extension class __builtin__.ParameterFile at 72918728: attribute lookup __builtin__.ParameterFile failed. Why is Zope trying to pickle the ParameterFile object when it's handling PUT itself? The PUT factory has a contract that it return an object, which will then be seated in its container, after which its PUT method will be called. If you don't want that behavior, then you need to use a custom container which overrides PUT itself, rather than trying to use the one in the 'webdav' package. Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFEDX9U+gerLs4ltQ4RAkm0AKCQcOw4cwIoOtvRlkOCSa6AnfQRWQCfXgEa L9OVqmOmjf1x1jQ8pvGcVIw= =I+rr -END PGP SIGNATURE- ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] newbie Simple WebSite Construction Using Zope and Search
Matt Slavin wrote: Hi, I am trying to use Zope to create a very simple company website (about 40 pages, or so) with the intention of having the flexibility to expand functionality etc in due course. I have very little Python / DTML experience, Python is in itself pretty easy to learn. DTML is a pure horror IMHO, and I avoid it by all means. ZPT (Zope Page Templates) are perhaps not the simplest existing template solution, but combined with metal macros and acquistion, it's a very powerful solution. but have managed to set up the site using includes on the main index page and then use aquisition to provide the content within each section. I'm not sure if this is a safe - or correct way of going about it, but it seems ideal for our purposes. The navigational menus dynamically include a link to each sub folder - ie website/services/ - and navigating to a section, index_html is automatically shown. The mainContent variable is then dynamically placed into index_html. (So there are separate mainContent dtmlDocuments in About Us, Services etc..) This means we can keep the content completely separate, and do not have to include headers, footers and other includes within the mainConte nt variable. Brilliant. However, when using the search script - http://www.zope.org/Members/Ioan/SiteSearch - results return a link back to the dtml_Document file mainContent, which gets displayed without any of the header of footer information. Is there any way to render the page with header and footer info? (By, I guess, redirecting the page to the containing folder, so that it pulls out index_html instead...) What I do is using ZPT and metal macros. 1/ I have one or more master page template(s) for the layout(s). This|these template(s) define a a page macro at the beginning (before the doc type declaration) and slots for the parts that are to be overridden by other templates - one of these slots being the main_content. 2/ then I have content page templates that callback on the appropriate master template and fill in the needed slots The whole thing relies on the Product used for content knowing how to render in a page template (the EpozDocument product provides a good base for this - don't be afraid, it's not that terrible). A sample master template would look like this: metal:block define-macro=page DOCTYPE html head title tal:content=here/title_or_idtitle/title metal:block define-slot=meta/metal:block ... /head body div id=header metal:block define-slot=header the standard header, can be overriden /metal:block /div div id=sidebar metal:block define-slot=sidebar div tal:replace=here/get_side_menu / /metal:block /div div id=main_content metal:block define-slot=main_content this is the main content area, to be overriden /metal:block /div div id=footer the standard header, can be overriden /metal:block /div /body /html /metal:block And a (very simple) page template for a given content type could be (assume there's a get_master_template method (ie python script or method of the content product) that returns the appropriate master template): metal:block use-macro=here/get_master_template/macros/page metal:block fill-slot=main_content h1 tal:content=here/title_or_idthe title/h1 div tal:content=here/content the real content /div /metal:block /metal:block I did my first Zope site with this architecture and the EpozDocument product for content pages, and it has proven to be a pretty usable/maintainable/extensible solution. HTH -- bruno desthuilliers développeur [EMAIL PROTECTED] http://www.modulix.com ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Redirect Exception and Five
Hi all, I have a problem developing a Product using Five.When a Redirect Exception is raised from a PluggableUserFolder inside my product, it is not handled by the publisher, and I have an error message instead a browser redirect. The same test inside a normal Folder works fine. I'm using Zope 2.9.0, and tried to add this ZCML statements, but I've no luck, and I can't find any other message talking about this. five:traversable class=OFS.Application.Application/ five:traversable class=OFS.Folder.Folder/ five:traversable class=zExceptions.Redirect/ five:traversable class=Products.PluggableUserFolder.PluggableUserFolder.PluggableUserFolder/ five:traversable class=.folder.APWebFolder/ Anybody knows what could happen ? Thanks -- -- Santi Camps Earcon S.L. - http://www.earcon.com - http://www.kmkey.com ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Re: (microsoft) webdav and zope 2.8.4
On 3/2/06, Patrick Decat [EMAIL PROTECTED] wrote: PS: Just noticed Tres' comment about comming up with a patch which makes the header addition configurable. I'll try do that on my next Zope upgrade. Regards, Patrick. I just upgraded from Zope 2.9.0 to Zope 2.9.1 and submitted a patch ( http://www.zope.org/Collectors/Zope/1441 ) that makes the 'MS-Author-Via' header configurable. Regards, Patrick. ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] repozo.py
We are (finally) moving to repozo for our backups. We are running a mixed collection of Zopes -- mostly Zope 2.7.6, Zope 2.8.X and Zope 2.9.0. For the near term we cannot move to a single release. There are differences between the versions of repozo distributed with the different Zope systems. I assume that the they are backward compatible and that the repozo.py shipped with Zope 2.9.0 is compatible with all variations of the Data.fs format. -- ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] manage_pasteObjects question
I am trying to do a manage_cutObjects in one script and then a manage_pasteObjects. When I execute this line from my pasteObjects python script: context.manage_pasteObjects(cb_copy_data=context.cb_dataItems(),REQUEST=req['__cp']) I get a message back: "The data in the clipboard could not be read, possibly due to cookie data being truncated by your web browser. Try copying fewer objects." I'm not sure why this happens. This doesn't happen from the ZMI so it's something to do with how I'm calling context.manage_pasteObjects in the above snippet. I also had my pasteObjects script return the clipboard data: print context.cb_dataItems() return printed which returns: [cmsPage at /cmstest/tomspage3.shtml] So, I know I've got clipboard data but for some reason, manage_pasteObjects thinks I don't and raises eInvalid on line 143 of OFS.CopySupport.py. Any ideas? Thanks, Tom Palermo Senior Web Developer Constella Group, LLC ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Need Urgent Help
Guys I am required to interface with the following systems: Hummingbird DM Hummingbird RM Documentum RM OpenText Livelink Crystal Enterprise Pro Any ideas? Meir Livneh ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Help needed to simplify some code
Several months ago someone provided me with me with some sample code which did exactly what I wanted, but looking at it again it looks a little unwieldy and could do with tidying up. It consists of:- span tal:define=opts python:here.lib.parse_file(file=here.news,sepr=',',clone=1) tal:block repeat=opt opts lia tal:content=python:opt[1] tal:attributes=href python:'news_items/' + opt[0]/a/li /tal:block /span which involves parsing a file containing two fields separated by ',' eg. 001,abc 002,jkl 003,xyz The second field is just a string which appears in a selection menu, and the first is the name of a folder which contains an object called 'content' which get displayed on selecting the correponding link. I know this is not a particularly elegant way of doing it, but after looking at some TAL examples just can't figure out the right way to do it. Some help in simplifying it would be appreciated. -- John ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Need Urgent Help
Hire a consultant. - C On Mar 7, 2006, at 7:09 PM, Meir Livneh wrote: Guys I am required to interface with the following systems: Hummingbird DM Hummingbird RM Documentum RM OpenText Livelink Crystal Enterprise Pro Any ideas? Meir Livneh ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev ) ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Zope Managed Server
Hello Folks, I'm interested in finding a company that will do monthly managed zope hosting. We're looking for a dedicated machine. I know that Zope Corp does this and it is quite expensive. I wonder if anyone has had any experiences with such a service. Any advice is highly appreciated, and I apologize if this list is an inappropriate venue to pose such a question. Thanks! Dan ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] newbie Simple WebSite Construction Using Zope and Search
Just wanted to say thanks for all your responses, they were brilliant. It's givenme an insight into further zope use, whilst solving the immediateproblem! Fantastic.CheersMatt Yahoo! Photos NEW, now offering a quality print service from just 8p a photo.___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Need Urgent Help
But learn to post before posting again. Subjects like need urgent help + cross-postings are the first step for a consultant to throw such a posting into the trashcan. -aj --On 7. März 2006 20:33:12 -0500 Chris McDonough [EMAIL PROTECTED] wrote: Hire a consultant. - C On Mar 7, 2006, at 7:09 PM, Meir Livneh wrote: Guys I am required to interface with the following systems: Hummingbird DM Hummingbird RM Documentum RM OpenText Livelink Crystal Enterprise Pro Any ideas? Meir Livneh ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev ) ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev ) pgpx3SnWL5VCg.pgp Description: PGP signature ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Need Urgent Help
+---[ Andreas Jung ]-- | | But learn to post before posting again. | Subjects like need urgent help + cross-postings are the first step | for a consultant to throw such a posting into the trashcan. Actually we rub our hands together and triple our rate d8) -- Andrew Milton [EMAIL PROTECTED] ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Need Urgent Help
--On 8. März 2006 17:12:15 +1100 Andrew Milton [EMAIL PROTECTED] wrote: +---[ Andreas Jung ]-- | | But learn to post before posting again. | Subjects like need urgent help + cross-postings are the first step | for a consultant to throw such a posting into the trashcan. Actually we rub our hands together and triple our rate d8) haha...do you have the need to accept any customer? :-) -aj pgp3u0XEUmafY.pgp Description: PGP signature ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Need Urgent Help
+---[ Andreas Jung ]-- | | | --On 8. M??rz 2006 17:12:15 +1100 Andrew Milton [EMAIL PROTECTED] | wrote: | | +---[ Andreas Jung ]-- | | | | But learn to post before posting again. | | Subjects like need urgent help + cross-postings are the first step | | for a consultant to throw such a posting into the trashcan. | | Actually we rub our hands together and triple our rate d8) | | | haha...do you have the need to accept any customer? :-) No, but, you can't just turn them away either d8) -- Andrew Milton [EMAIL PROTECTED] ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
