[Zope-CMF] CMF Collector: Open Issues
The following supporters have open issues assigned to them in this collector (http://www.zope.org/Collectors/CMF). Assigned and Open jens - CachingPolicyManager: Make Max-Age parameter dynamic, [Accepted] http://www.zope.org/Collectors/CMF/405 mhammond - Windows DevelopmentMode penalty in CMFCore.DirectoryView, [Accepted] http://www.zope.org/Collectors/CMF/366 Pending / Deferred Issues - Wrong cache association for FSObject, [Pending] http://www.zope.org/Collectors/CMF/255 - CMFSetup: Windows exports contain CR/LF, LF and even CR newlines, [Pending] http://www.zope.org/Collectors/CMF/266 - FSPropertiesObject.py cannot handle multiline input for lines, text attributes, [Deferred] http://www.zope.org/Collectors/CMF/271 - Can't invalidate skin items in a RAMCacheManager, [Pending] http://www.zope.org/Collectors/CMF/343 - CMFSetup: Workflow Tool export fails with workflows which have scripts, [Pending] http://www.zope.org/Collectors/CMF/373 - CMFCore.Skinnable.SkinnableObjectManager can merge skin data, [Pending] http://www.zope.org/Collectors/CMF/375 - Proxy Roles does't work for a Script using portal_catalog.searchResults, [Pending] http://www.zope.org/Collectors/CMF/380 - WorkflowAction deprecated warning should not printed for WorkflowMethod, [Pending] http://www.zope.org/Collectors/CMF/388 - workflow notify success should be after reindex, [Pending] http://www.zope.org/Collectors/CMF/389 - Content in Setup gets Cleared (Content Import Handler), [Pending] http://www.zope.org/Collectors/CMF/404 - index_html manage_workspace and view error, [Pending] http://www.zope.org/Collectors/CMF/406 Pending / Deferred Features - Favorite.py: queries and anchors in remote_url, [Pending] http://www.zope.org/Collectors/CMF/26 - DefaultDublinCore should have Creator property, [Pending] http://www.zope.org/Collectors/CMF/61 - path criteria on Topic should honor VHM, [Pending] http://www.zope.org/Collectors/CMF/111 - Document.py: universal newlines, [Pending] http://www.zope.org/Collectors/CMF/174 - Add condition for transition's action like other action, [Pending] http://www.zope.org/Collectors/CMF/207 - Major action enhancement, [Pending] http://www.zope.org/Collectors/CMF/232 - portal_type is undefined in initialization code, [Pending] http://www.zope.org/Collectors/CMF/248 - CMFTopic Does Not Cache, [Deferred] http://www.zope.org/Collectors/CMF/295 - Wishlist: a flag that tags the selected action., [Pending] http://www.zope.org/Collectors/CMF/301 - CMFDefault should make use of allowCreate(), [Pending] http://www.zope.org/Collectors/CMF/340 - Nested Skins, [Deferred] http://www.zope.org/Collectors/CMF/377 - CatalogVariableProvider code + tests, [Pending] http://www.zope.org/Collectors/CMF/378 - manage_doCustomize() : minor additions, [Pending] http://www.zope.org/Collectors/CMF/382 - First Day of Week, [Pending] http://www.zope.org/Collectors/CMF/400 ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
[Zope-CMF] [dev] CMF 2.0 browser views and Five traversal
Hi! CMF 2.0.0-beta uses the current Five traversal behavior to override skin methods with views if views are enabled. Unfortunately the overriding of skin methods will no longer work if Five's lookup order is changed as proposed here: http://codespeak.net/pipermail/z3-five/2006q1/001186.html So we need a different solution for the final release of CMF 2.0.0. Based on the discussion on the Five list I propose this solution: 1.) To become independent of the lookup order views are named different than the corresponding skin methods. 2.) Skins *and* views are always enabled. 3.) A new extension profile hooks up the views instead of the skin methods. Enabling Five traversal and views by default is a big change so we might need an other beta release. Some details: - I'd like to keep the changes the extension profile makes as small as possible. So I don't want to change the visible action targets. All we need are some Method Aliases that point to the views. - We need new names for the views. I'd like to use @@view.html, @@edit.html and @@properties.html for the views that already exist. I think 'metadata_edit_form' and 'folder_edit_form' are both in fact properties views and 'folder_contents' is just a special edit view. I'd like to use the same names for container views as for content views. - I don't know why we have metadata_edit_form and full_metadata_edit_form. I'd like to use the full set for @@properties.html. Any comments are welcome. If there are no objections I'll check in these changes within this week. Cheers, Yuppie ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
[Zope-CMF] Re: index_html behavior on Portal Folders in CMF-2.0.0
Hi David!
David Pratt wrote:
Hi Yuppie. Yes, I will give this a try. It is hard to move completely
away from old ways and I am migrating but there is a learning curve to
this for sure. Once I have set up a marker interface for one folder like
this and have it work, at least I will be more comfortable. I may have
other questions.
You know that the 'edit-markers.html' view is available in CMF if you
enable Five traversal?
Maybe we should add this action to the default profile:
?xml version=1.0?
object name=portal_actions meta_type=CMF Actions Tool
xmlns:i18n=http://xml.zope.org/namespaces/i18n;
object name=object
object name=interfaces meta_type=CMF Action
i18n:domain=cmf_default
property name=title i18n:translate=Interfaces/property
property name=description
i18n:translate=Assign marker interfaces/property
property
name=url_exprstring:${object_url}/edit-markers.html/property
property name=icon_expr/property
property name=available_expr/property
property name=permissions
element value=Manage portal/
/property
property name=visibleTrue/property
/object
/object
/object
Do you still have the invalid ID problem? I was not able to reproduce
it. Do you see these issues also with a default installation or only
with browser views enabled?
If you don't answer questions like these it's hard to fix the issues you
report.
Cheers,
Yuppie
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
[Zope-CMF] Re: [dev] CMF 2.0 browser views and Five traversal
yuppie wrote: Based on the discussion on the Five list I propose this solution: 1.) To become independent of the lookup order views are named different than the corresponding skin methods. 2.) Skins *and* views are always enabled. 3.) A new extension profile hooks up the views instead of the skin methods. This seems like an elegant solution. Enabling Five traversal and views by default is a big change so we might need an other beta release. I would strongly suggest that. Some details: - I'd like to keep the changes the extension profile makes as small as possible. So I don't want to change the visible action targets. All we need are some Method Aliases that point to the views. - We need new names for the views. I'd like to use @@view.html, @@edit.html and @@properties.html for the views that already exist. +1 for saner view names. document_view or document_edit_form is just a lame legacy from the one flat view namespace that portal_skins provide. By the way, unless you make @@view.html the default view name for documents or whatever (using five:defaultViewable and browser:defaultView), why not call it @@index.html?? Philipp ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
Re: [Zope-CMF] CPS 3.4.0 released!
Congratulations Stefane and CPS! Stefane Fermigier wrote: 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). Packaging changes ^ CPS is now
[Zope-CMF] [DCWorkflow]Problem with initial state
Hi, I found something funny yesterday that makes me spend some hours: If you delete the state marked as initial state the variable initial_sate always contains its id. It makes _exectuteTransition raising an error because _getWorkflowStateOf return None. The code of _executeTransition that gives me headaches: old_sdef = self._getWorkflowStateOf(ob) old_state = old_sdef.getId() Regards, -- Encolpe DEGOUTE http://encolpe.degoute.free.fr/ Logiciels libres, hockey sur glace et autres activités cérébrales ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
Re: [Zope-CMF] [DCWorkflow]Problem with initial state
Encolpe Degoute wrote at 2006-3-7 20:33 +0100: I found something funny yesterday that makes me spend some hours: If you delete the state marked as initial state the variable initial_sate always contains its id. Any workflow needs an initial state. Thus, maybe, you should mark a new state as initial once you deleted the old one? In many cases, deleting state is not a good idea (at least not when there are objects in the deleted state). -- Dieter ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
