Re: [Zope3-dev] AW: Proposal, free views

2007-09-26 Thread Dieter Maurer
Philipp von Weitershausen wrote at 2007-9-25 18:49 +0200:
 ...
I think we should just not raise any deprecation warnings at all.  
Just the imports for BBB and be done with it.

I like this very much :-)



-- 
Dieter
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com



Re: [Zope3-dev] AW: Proposal, free views

2007-09-25 Thread Brian Sutherland
On Mon, Sep 24, 2007 at 01:13:00AM +0200, Roger Ineichen wrote:
 I think we will split packages in its base parts.
 For exapmle this means we will create a package zope.session
 that contains the python api and degrade zope.app.session
 to contain the zmi views. 

Personally, I think this is the way to go. i.e. to separate the UI from
the python API in separate eggs.

That way the python API egg can have relatively few dependencies, and
thus be more useful to more people.  The UI egg is then useful to
whoever wants to bring in all the dependencies and conform to the UI.

It's very strange the way Zope3 mixes high-level code (css, html,
pagetemplates) with low-level python APIs. Basically forcing you to have
(and manage) lots of dependencies even if you only want the python API.

-- 
Brian Sutherland
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com



Re: [Zope3-dev] AW: Proposal, free views

2007-09-25 Thread Philipp von Weitershausen

On 25 Sep 2007, at 18:41 , Brian Sutherland wrote:

On Mon, Sep 24, 2007 at 01:13:00AM +0200, Roger Ineichen wrote:

I think we will split packages in its base parts.
For exapmle this means we will create a package zope.session
that contains the python api and degrade zope.app.session
to contain the zmi views.


Personally, I think this is the way to go. i.e. to separate the UI  
from

the python API in separate eggs.

That way the python API egg can have relatively few dependencies, and
thus be more useful to more people.  The UI egg is then useful to
whoever wants to bring in all the dependencies and conform to the UI.

It's very strange the way Zope3 mixes high-level code (css, html,
pagetemplates) with low-level python APIs. Basically forcing you to  
have
(and manage) lots of dependencies even if you only want the python  
API.


After pondering about a while, I think this is probably a very good  
solution. It should help us reduce the package interdependencies  
quite a lot, at least on the Python-only level.


It should also add meaning back to the zope.app namespace.

Note that I've seen checkins that add deprecation warnings. Even  
worse, they're talking about removing stuff in the future. I thought  
we had reached the consensus that we weren't going to remove stuff  
anymore. In other words, that we were never ever going to break  
backwards-compatibility again.


I think we should just not raise any deprecation warnings at all.  
Just the imports for BBB and be done with it.


___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com



Re: [Zope3-dev] AW: Proposal, free views

2007-09-25 Thread Jim Fulton


On Sep 25, 2007, at 12:49 PM, Philipp von Weitershausen wrote:
...
Note that I've seen checkins that add deprecation warnings. Even  
worse, they're talking about removing stuff in the future. I  
thought we had reached the consensus that we weren't going to  
remove stuff anymore. In other words, that we were never ever going  
to break backwards-compatibility again.


I think we should just not raise any deprecation warnings at all.  
Just the imports for BBB and be done with it.


We said we would only break backward compatibility under dire  
circumstances. :)


I think that deprecation warnings are fine to let people know This  
isn't the way you should be doing this. That other way is better.   
It helps people use packages according to the state of the art, which  
will continue to evolve and it will make developers feel better,  
which is worth something. :)


Also, if we ever *do* need to make a backward-incompatible change to  
a package, we'll have some license to clean up rotten apis.


Jim

--
Jim Fulton
Zope Corporation


___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com