[Zope-CMF] CMF Collector: Open Issues

2006-03-24 Thread tseaver
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

- workflow interface out of date on 1.5 branch,
  [Pending] http://www.zope.org/Collectors/CMF/407


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

- CachingPolicyManager: Support OFS.Cache.CacheManager,
  [Pending] http://www.zope.org/Collectors/CMF/408



___
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] five_template slots

2006-03-24 Thread Florent Guillaume
IIRC the idea was to have a template usable from standard Zope 3 views that 
expected the standard Zope 3 slots, and css_slot was one of those.


But I'll let Lennart answer, I've never really touched this stuff.

Florent


yuppie wrote:

Hi!


A while ago the five_template for the trunk / CMF 2.0 was replaced by 
the one from CMFonFive.


I still have some difficulties understanding the rationale behind that 
change. I never got an answer to this mail:


http://mail.zope.org/pipermail/zope-cmf/2006-January/023746.html


AFAICS there are two use cases for the five_template:


1.) Provide generic slots used in Five and Zope 3

The five_template shipped with Five provides two slots: 'style_slot' and 
'body'. The old CMF five_template did provide the same two slots. The 
new five_template maps 'style_slot' to a non-existent 'css_slot'.



2.) Provide cmf specific slots in @@standard_macros/page

The new five_template provides 'base' and 'header', mapping them to the 
corresponding slots in main_template. 'body' is mapped to 'main', so all 
slots in main_template can be filled via the five_template. I'm not sure 
if we really should support that use case. At least it is less important 
than the first use case.



Issues:
---

- mapping 'style_slot' to 'css_slot' is an obvious bug, that change 
should be reverted


- the 'header' slot behaves different than in main_template: 
main_template provides default content for 'header', the five_template 
'header' is empty by default. I'd like to keep that in sync, but maybe 
we should remove the default content from main_template. Most skin 
templates override the 'header' slot anyway.


- the Five 'body' slot doesn't map very well to the CMF 'main' slot: 
'header' *and* 'main' would match better.



Proposal:
-

1.) Add a new 'body' slot in main_template that wraps around the 
'header' and the 'main' slot. You can either use 'body' *or* 'header' 
and 'main'.


2.) Remove the default content in main_template's 'header' slot.

3.) Replace five_template by something like this:

metal:macro metal:define-macro=page
html metal:use-macro=context/main_template/macros/master
 head
  metal:slot metal:fill-slot=base
   metal:slot metal:define-slot=base /
  /metal:slot
  metal:slot metal:fill-slot=style_slot
   metal:slot metal:define-slot=style_slot /
  /metal:slot
 /head
 body
  metal:slot metal:fill-slot=body
   metal:slot metal:define-slot=body
metal:slot metal:define-slot=header /
metal:slot metal:define-slot=main /
   /metal:slot
  /metal:slot
 /body
/html
/metal:macro

4.) Change the browser view templates to use 'main' instead of 'body' 
(that no longer maps to 'main').



Any feedback is welcome. If there are no objections I'd like to make the 
proposed changes on Saturday, before the 2.0-beta2 release.



Cheers,

Yuppie

___
Zope-CMF maillist  -  [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-cmf

See http://collector.zope.org/CMF for bug reports and feature requests




--
Florent Guillaume, Nuxeo (Paris, France)   Director of RD
+33 1 40 33 71 59   http://nuxeo.com   [EMAIL PROTECTED]
___
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] [dev] five_template slots

2006-03-24 Thread Lennart Regebro
On 3/23/06, yuppie [EMAIL PROTECTED] wrote:
 - mapping 'style_slot' to 'css_slot' is an obvious bug, that change
 should be reverted

Why is it a bug? That's not obvious to me at all. Both slots are for
putting style sheets in...

 - the 'header' slot behaves different than in main_template:
 main_template provides default content for 'header', the five_template
 'header' is empty by default.

OK, syncing that someway seems reasonable.

 1.) Add a new 'body' slot in main_template that wraps around the
 'header' and the 'main' slot. You can either use 'body' *or* 'header'
 and 'main'.

For 2.0 I'm ok with this, but note that this will mean that everybody
must add this slot to their templates when they upgrade to 2.0, or all
Five products will break.

 4.) Change the browser view templates to use 'main' instead of 'body'
 (that no longer maps to 'main').

Well, they *do* use body so we can't change that.

--
Lennart Regebro, Nuxeo http://www.nuxeo.com/
CPS Content Management http://www.cps-project.org/
___
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: [Zope3-dev] Re: [Zope-CMF] Fighting the Zope 2.9 testrunner

2006-03-24 Thread Chris Withers

Stuart Bishop wrote:

silence it (and open a bug report at the same time). The noisier test output
is, the more likely you are to miss relevant information.


Totally agreed, I was kinda shocked at how many deprecation errors Zope 
2.9 ships with :-(


Chris

--
Simplistix - Content Management, Zope  Python Consulting
   - http://www.simplistix.co.uk

___
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