[Kss-devel] KSS without Zope

[Balazs Ree]

On 2007. 05. 11, 10.14- Godefroid Chapelle wrote:

> However, I still think that we could change kss.core to kss.zope and 
use 
> kss.core for the Python only version.
> 
> It is not too late to change namespace imo.
>
 
I agree on changing kss.core to kss.zope later (preferably with a major 
version release). I agree it's not too late, but I would say the name 
change can be done independently from the planned refactorization. Make 
the new package, make kss.core use it, and at some point we can consider 
changing kss.core to kss.zope.

But: I am against naming the python-only package back to kss.core, we 
have infinite number of unused names to choose from and we should not 
call the new python-only package the same as we called a zope-only 
package at one time. Besides kss.core is not so cool either, especially 
because it does not say "the core for what?" but at least atm kss.core 
really contains "the core" of kss but that would not be true for the new 
package (imagine we are talking about "kss core" and "kss core plugins" 
as of javascript).

kss.support, more ok, actually for me this feels the best so far. Also 
think that we may have more subpackages:

kss.support.commands
kss.support.cookjs

or whatever, so support is good because after that you say "support for 
what".

yet another (not too bright) suggestion is kss.base .
 
> Jeroen, while doing the python stuff, could you pay attention to not 
> introduce pylons only stuff except in a kss.pylons package ?
 
Definitely.

And whoever creates a new package, make sure of the egg format.

-- 
Balazs Ree