[Zope-CMF] Re: CMF 1.5 beta coming -- last call before feature freeze!

[yuppie]

Hi!


Grégoire Weber wrote:
>>I had a closer look at the permalink stuff. And I don't think this idea 
>>is mature enough to ship permalinks with CMF 1.5.
>>
>>- Permalinks should have speaking names, not numbers.
>>
>>- Permalinks should point to the primary location of the object. 
>>Combined with a centralized content repository they make more sense.
>>
>>- Implementing permalinks as aliases causes a lot of problems:
>>
>>   o  do search engines index both locations?
>>
>>   o  do relative links work?
>>
>>   o  is the navigation consistent?
> 
> 
> I know. I'd liked to expose the unique id functionality a little bit.
> That's why I introduced the permalink feature. The question is if this
> is the right name.

It's the Right Thing to expose framework functionality in CMFDefault. 
This way the features are better tested (the permalink feature helped to 
find the Unauthorized bug) and people can see how to use them.

The problem with CMFUid is that its function is to work in the 
background. IMHO the changes in Favorite are a much better example of 
how to use CMFUid.

>>This is the old way to do it. The CMF 1.5 way looks like this:
>>
>>...
>>ti = obj.getTypeInfo()
>>method = ti.getMethodPath('view')[0]
>>...
> 
> 
> ok
> 
> 
>>And BTW: tal:on-error is a bare except!
> 
> 
> I know and I don't like it neither. It's to catch exceptions 
> if someone did not to install CMFUid.

Did tal:condition="python: uidtool and not isFolderish" of your first 
checkin not do that job?

> How to proceed? Shall the changes be reverted? I personally
> would like people to see the new functionality.
> 
> I'm here on a modem. I'll check e-mail at 20:00 (european time).
> I can act if I hear something till then!

I don't think this is urgent, changing this after the beta release 
should be fine. This gives us more time to think about a better solution.


Just my 2 cents.

Yuppie