[Zope-CMF] CMF Collector: Open Issues

2005-10-16 Thread tseaver
The following supporters have open issues assigned to them in this collector
(http://www.zope.org/Collectors/CMF).

Assigned and Open


  efge

- CMFSetup: provide non-ascii im- and exports,
  [Accepted] http://www.zope.org/Collectors/CMF/292

- CMFSetup doesn't correctly detect DCWorkflow on export,
  [Accepted] http://www.zope.org/Collectors/CMF/298


  jens

- FSPropertiesObject.py cannot handle multiline input for lines, text 
attributes,
  [Accepted] http://www.zope.org/Collectors/CMF/271


  mhammond

- Windows DevelopmentMode penalty in CMFCore.DirectoryView,
  [Accepted] http://www.zope.org/Collectors/CMF/366


  mj

- CMFSetup doesn't correctly detect DCWorkflow on export,
  [Accepted] http://www.zope.org/Collectors/CMF/298


Pending / Deferred Issues

- CMFCalendar weekday locale issue,
  [Pending] http://www.zope.org/Collectors/CMF/237

- 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

- PortalCatalog.ZopeFindAndApply should probably also search in 
opaqueItems,
  [Pending] http://www.zope.org/Collectors/CMF/296

- WorkflowTool should recurse into opaqueItems,
  [Pending] http://www.zope.org/Collectors/CMF/297

- add External Methods to workflow script handling,
  [Pending] http://www.zope.org/Collectors/CMF/329

- 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


Pending / Deferred Features

- Favorite.py: queries and anchors in remote_url,
  [Pending] http://www.zope.org/Collectors/CMF/26

- Allow flexible date editing in Event.py (CMFCalendar),
  [Pending] http://www.zope.org/Collectors/CMF/40

- DefaultDublinCore should have Creator property,
  [Pending] http://www.zope.org/Collectors/CMF/61

- Make changeFromProperties accept sequences too,
  [Pending] http://www.zope.org/Collectors/CMF/99

- 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

- Permissions in PortalFolder: invokeFactory(),
  [Pending] http://www.zope.org/Collectors/CMF/175

- 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

- Action._listsActions() should be more safe,
  [Pending] http://www.zope.org/Collectors/CMF/253

- Expose Document text_format metadata,
  [Pending] http://www.zope.org/Collectors/CMF/285

- customization of type of homefolder on creation,
  [Pending] http://www.zope.org/Collectors/CMF/288

- Allow contentFilter to use review_state,
  [Pending] http://www.zope.org/Collectors/CMF/294

- CMFTopic Does Not Cache,
  [Pending] 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,
  [Pending] 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



___
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: CMF and Five views: hooking up POST

2005-10-16 Thread yuppie

Jens Vagelpohl wrote:
Doing some more work on Five views for CMF right now. I have the edit 
view hooked up and working find for my sample content type. The view 
class given to me by Tres defines a POST method, but I can't seem to get 
that hooked up correctly.


These sentences don't make any sense to me: What is your goal? Why do 
you need to 'hook up' POST if your edit view works already?


When should your POST method be called and what does that POST method? 
Are you working on something special or just on a normal edit view?



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: [CMF-checkins] SVN: CMF/branches/1.5/C CMFSetup: added support for configuring content type registry.

2005-10-16 Thread yuppie

Hi Tres!


Tres Seaver wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Stefan H. Holek wrote:
Right, so at what point is the content-type-registry supposed to be 
added now? Plone Site creation breaks after this checkin with:


  File /Users/zope/plonehd/Products/CMFCore/utils.py, line 83, in 
getToolByName

raise AttributeError, name
AttributeError: content_type_registry


Plone needs to kick off a CMFSetup profile which creates all the tools
before trying to use them.  Over time, there will be *nothing* left in
the PortalGenerator class:  everything it used to do will be handled in
a profile.

For BBB, we should chat about what actually happens here.


I can't see any need to remove code from PortalGenerator on the 1.5 
branch. So far CMFSetup was an optional component of CMF 1.5. Are you 
sure you wanted to remove that code from the 1.5 branch?



Regarding the trunk (CMF 2.0):

Up to now I tried to keep manage_addCMFSite and PortalGenerator intact 
for BBB, but this becomes more and more a big burden. So meanwhile I 
would agree with dropping support for manage_addCMFSite, PortalGenerator 
and related code completely.


This would mean that all products built on top of the CMF have to ship 
with a GenericSetup profile for CMF 2.0.



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: CMF and Five views: hooking up POST

2005-10-16 Thread Jens Vagelpohl


On 16 Oct 2005, at 16:21, yuppie wrote:


Jens Vagelpohl wrote:

Doing some more work on Five views for CMF right now. I have the  
edit view hooked up and working find for my sample content type.  
The view class given to me by Tres defines a POST method, but I  
can't seem to get that hooked up correctly.




These sentences don't make any sense to me: What is your goal? Why  
do you need to 'hook up' POST if your edit view works already?


When should your POST method be called and what does that POST  
method? Are you working on something special or just on a normal  
edit view?


The goal is very simple: The edit form posts to itself. If a POST is  
received, I want to edit the content item with the values from  
itself. Very same principle as we have now, with the exception that  
the current setup looks into the REQUEST to find button names to  
decide on what to do.


Again, I'm working with a class Tres gave me which has a POST method  
on the editing view class.


jens

___
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 + Acqusition

2005-10-16 Thread Dieter Maurer
Victor Safronovich wrote at 2005-10-11 14:04 +0600:
  I have a question about DCWorkflow, WorkflowTool and Acqusition.

  My  object,  during  change  state,  move  to  another folder and should 
 change
  acqusition wrapper.

  workflow_tool = getToolByName( my_object, 'portal_workflow')
  workflow_tool.doActionFor( my_object, 'some_action' )
  # during doActionFor raised ObjectMoved but i don`t know about that in here
  # because WorkflowTool._invokeWithNotification shallow it.

But it returns what objectMoved.getResult() returns.

   You can use this to communicate with the doActionFor caller.


The much more reliable way however is to perform
the necessary unindexing and recataloging inside the action
itself (and not let this as task of the caller).

-- 
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


Re: [Zope-CMF] Re: RestrictedPython, TALES Expressions and CMF

2005-10-16 Thread Dieter Maurer
Tres Seaver wrote at 2005-10-11 08:58 -0400:
 ...
'call_with_ns' should be invoked only for objects with either a
'__render_with_namespace__' attribute (PythonScripts fit here) or those
with 'isDocTemp' true.  Its only real purpose is to set up the namespace
before calling a DTMLMethod;  I don't even understand why PythonScripts
have such a method.

Probably, because they can bind the DTML namespace...

-- 
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


[Zope-CMF] Re: CMF and Five views: hooking up POST

2005-10-16 Thread yuppie

Hi Jens!


Jens Vagelpohl wrote:


On 16 Oct 2005, at 16:21, yuppie wrote:


Jens Vagelpohl wrote:

Doing some more work on Five views for CMF right now. I have the edit 
view hooked up and working find for my sample content type. The view 
class given to me by Tres defines a POST method, but I can't seem to 
get that hooked up correctly.




These sentences don't make any sense to me: What is your goal? Why do 
you need to 'hook up' POST if your edit view works already?


When should your POST method be called and what does that POST method? 
Are you working on something special or just on a normal edit view?


The goal is very simple: The edit form posts to itself. If a POST is 
received, I want to edit the content item with the values from itself. 
Very same principle as we have now, with the exception that the current 
setup looks into the REQUEST to find button names to decide on what to do.


Again, I'm working with a class Tres gave me which has a POST method on 
the editing view class.


Don't know why Tres gave you a class with a POST method.

Are you aware of the goldegg-folder_contents branch? CMFDefault/browser 
shows a working example. (Well. While refactoring the code I broke some 
logic, but the view itself works.)



HTH

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