[Zope-CMF] Re: CMF roadmap

[Tres Seaver]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Jens Vagelpohl wrote:
> 
> On 15 Feb 2006, at 23:53, Martin Aspeli wrote:
> 
> There's one specific item that I couldn't find enough  information
> on to make a comment, which is events support.  Florent, what is
> the status on the trunk and the 1.6 branch?


 In 1.6 and 2.0 events are not used beyond what Zope has. So  events
 are not used to trigger cataloging on modifications for  instance.

 Also, manage_afterAdd & co still exist and have not been  converted
 to events, so are still flagged using  five:deprecatedManageAddDelete.

 As mentioned, Tres has a branch where he works on this.
>>>
>>>
>>> Is this something we need to wait for for the first 2.0 beta in  1.5
>>> weeks?
>>
>>
>> High +1 on getting this fixed for 2.0. There's a lot of contrived 
>> cataloging code out there (*cough* Archetypes) and it would be 
>> beneficial to have a clean model for events in CMF, not just for 
>> cataloging things.
> 
> 
> I do realize there are always parties who would *like* something to 
> happen, but this was a question directed at the people who *do* make  it
> happen. If we're not sticking to some kind of schedule but wait  till
> all wish lists are considered we won't get anywhere I am afraid.

I have just checked in the stab I made on another branch[1]:  perhaps
some of the interested parties can help work out the remaining glitches
(some test failures) and extend it further (e.g., to handle workflow
notifiication).


[1] svn+ssh://svn.zope.org/repos/main/CMF/branches/tseaver-catalog_events

Tres.
- --
===
Tres Seaver  +1 202-558-7113  [EMAIL PROTECTED]
Palladion Software   "Excellence by Design"http://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFD9AMp+gerLs4ltQ4RAqPIAKCg14oqaG3guVQ9p36JuxzMylm+CgCfWB/8
OgS2inOzZmULcWbCil/omL0=
=Qxq3
-END PGP SIGNATURE-

___
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: Re: CMF roadmap

[Jens Vagelpohl]

On 15 Feb 2006, at 23:53, Martin Aspeli wrote:
There's one specific item that I couldn't find enough  
information on to make a comment, which is events support.  
Florent, what is the status on the trunk and the 1.6 branch?


In 1.6 and 2.0 events are not used beyond what Zope has. So  
events are not used to trigger cataloging on modifications for  
instance.


Also, manage_afterAdd & co still exist and have not been  
converted to events, so are still flagged using  
five:deprecatedManageAddDelete.


As mentioned, Tres has a branch where he works on this.


Is this something we need to wait for for the first 2.0 beta in  
1.5 weeks?


High +1 on getting this fixed for 2.0. There's a lot of contrived  
cataloging code out there (*cough* Archetypes) and it would be  
beneficial to have a clean model for events in CMF, not just for  
cataloging things.


I do realize there are always parties who would *like* something to  
happen, but this was a question directed at the people who *do* make  
it happen. If we're not sticking to some kind of schedule but wait  
till all wish lists are considered we won't get anywhere I am afraid.


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

[Zope-CMF] Re: Re: CMF roadmap

[Martin Aspeli]

On Wed, 15 Feb 2006 14:16:26 -, Jens Vagelpohl  
<[EMAIL PROTECTED]> wrote:




On 15 Feb 2006, at 14:12, Florent Guillaume wrote:


Jens Vagelpohl wrote:
There's one specific item that I couldn't find enough information on  
to make a comment, which is events support. Florent, what is the  
status on the trunk and the 1.6 branch?


In 1.6 and 2.0 events are not used beyond what Zope has. So events are  
not used to trigger cataloging on modifications for instance.


Also, manage_afterAdd & co still exist and have not been converted to  
events, so are still flagged using five:deprecatedManageAddDelete.


As mentioned, Tres has a branch where he works on this.


Is this something we need to wait for for the first 2.0 beta in 1.5  
weeks?


High +1 on getting this fixed for 2.0. There's a lot of contrived  
cataloging code out there (*cough* Archetypes) and it would be beneficial  
to have a clean model for events in CMF, not just for cataloging things.


Martin

--
(muted)

___
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] creating mailPassword and registeredNotify emails

[yuppie]

Hi!


Yesterday I fixed mailPassword and registeredNotify on the trunk. Since 
'registered_notify_template' and 'mail_password_template' now might 
contain unicode translations all values passed to them have to be 
decoded and the rendered return value has to be encoded. I decided to 
wrap the templates in scripts for this.


'registered_notify_template' and 'mail_password_template' are no good 
names for scripts, '_template' is always used for page templates. So I 
decided to call more neutral method names from mailPassword and 
registeredNotify.


'mail_password' is already used, so I choose completely new names: 
'member_password_mail' and 'member_registered_mail'.



Now my questions:

1.) If used with Localizer or PTS the old templates should still work. 
Do we have to provide backwards compatibility for the old template 
names? In a plain CMF environment backwards compatibility isn't possible 
anyway.


2.) I'm not sure about the new names. Meanwhile I tend to use shorter 
names: 'password_email' and 'registered_email'. The names for the 
related templates are too long right now. Any preferences?



If nobody cares I'll use 'password_email' and 'registered_email' and 
provide no backwards compatibility.



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: SVN: CMF/trunk/CMFDefault/RegistrationTool.py oops! this fallbacks are broken and I guess we don't need them anyway

[Florent Guillaume]

Yvo Schubbe wrote:

Modified: CMF/trunk/CMFDefault/RegistrationTool.py
===
--- CMF/trunk/CMFDefault/RegistrationTool.py2006-02-14 21:47:30 UTC (rev 
41621)
+++ CMF/trunk/CMFDefault/RegistrationTool.py2006-02-14 22:19:40 UTC (rev 
41622)
@@ -131,8 +131,7 @@
 # Rather than have the template try to use the mailhost, we will
 # render the message ourselves and send it from here (where we
 # don't need to worry about 'UseMailHost' permissions).
-method = getattr(self, 'member_password_mail',
- getattr(self, 'mail_password_template'))
+method = getattr(self, 'member_password_mail')


Well, self.member_password_mail is simpler :)

Florent


 kw = {'member': member, 'password': member.getPassword()}
 
 if getattr(aq_base(method), 'isDocTemp', 0):

@@ -173,8 +172,7 @@
 # Rather than have the template try to use the mailhost, we will
 # render the message ourselves and send it from here (where we
 # don't need to worry about 'UseMailHost' permissions).
-method = getattr(self, 'member_registered_mail',
- getattr(self, 'registered_notify_template'))
+method = getattr(self, 'member_registered_mail')
 kw = {'member': member, 'password': password, 'email': email}
 
 if getattr(aq_base(method), 'isDocTemp', 0):



--
Florent Guillaume, Nuxeo (Paris, France)   Director of R&D
+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] Re: CMF roadmap

[Jens Vagelpohl]

On 15 Feb 2006, at 14:12, Florent Guillaume wrote:


Jens Vagelpohl wrote:
There's one specific item that I couldn't find enough information  
on to make a comment, which is events support. Florent, what is  
the status on the trunk and the 1.6 branch?


In 1.6 and 2.0 events are not used beyond what Zope has. So events  
are not used to trigger cataloging on modifications for instance.


Also, manage_afterAdd & co still exist and have not been converted  
to events, so are still flagged using five:deprecatedManageAddDelete.


As mentioned, Tres has a branch where he works on this.


Is this something we need to wait for for the first 2.0 beta in 1.5  
weeks?


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

[Zope-CMF] Re: CMF roadmap

[Florent Guillaume]

Jens Vagelpohl wrote:

Hi all,

I finally sat down and put up a CMF roadmap page. It is pretty condensed 
right now, and I'm asking for feedback:


http://www.zope.org/Products/CMF/docs/roadmap

There's one specific item that I couldn't find enough information on to 
make a comment, which is events support. Florent, what is the status on 
the trunk and the 1.6 branch?


In 1.6 and 2.0 events are not used beyond what Zope has. So events are not 
used to trigger cataloging on modifications for instance.


Also, manage_afterAdd & co still exist and have not been converted to 
events, so are still flagged using five:deprecatedManageAddDelete.


As mentioned, Tres has a branch where he works on this.

Florent

--
Florent Guillaume, Nuxeo (Paris, France)   Director of R&D
+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] Re: Create new portal property with a Python script

[Hans Schou]

suresh wrote:


Hans Schou wrote:


pom.Ewire = pom.EwireIDURL[0]# I get an error here on this line



You should use manage_changeProperties() for this.


Yes, thanks, it was:
pom.manage_changeProperties(Ewire=pom.EwireIDURL[0])

Some day I even might understand why there is a different syntax 
sometimes...


/hans

___
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: GenericSetup Python 2.4 only?

[yuppie]

Stefan H. Holek wrote:

The use of "sorted" makes GS only work with Python 2.4. Intentional?



No. Of course not intentional.

Thanks for catching that, should be fixed now.

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] GenericSetup Python 2.4 only?

[Stefan H. Holek]

The use of "sorted" makes GS only work with Python 2.4. Intentional?


Stefan

--
Anything that happens, happens.  --Douglas Adams


___
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] CMF Collector: Open Issues

[tseaver]

The following supporters have open issues assigned to them in this collector
(http://www.zope.org/Collectors/CMF).

Assigned and Open


  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

- "Implicitly acquiring allow_discussion in isDiscussionAllowedFor",
  [Pending] http://www.zope.org/Collectors/CMF/398

- "Legal chars not permitted in email addresses",
  [Pending] http://www.zope.org/Collectors/CMF/401


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

- "FSDTML Method: 304 support",
  [Pending] http://www.zope.org/Collectors/CMF/402



___
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: Create new portal property with a Python script

[suresh]

Hans Schou wrote:


pom.Ewire = pom.EwireIDURL[0]# I get an error here on this line


You should use manage_changeProperties() for this.

Suresh

___
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