[z3-five] Restructuring

[Martijn Faassen]

Philipp von Weitershausen wrote:
> Martijn Faassen wrote:
[snip]
>> Examples, please? How is the current structure of modules in a package 
>> getting into our way?
> 
> Because we end up with either huge modules (e.g. Five.browser and 
> Five.browserconfigure) or, in case we decide to move them out to just 
> modules, we end up with a polluted namespace in which we have
> 
> browser
> browserconfigure
> form
> formconfigure
> formmacros
> skinmacros
> 
> Not to mention all the ZPT templates that are by now floating around the 
> Five package. 

Thanks for the examples. :)

> The idea is not to introduce many single-file packages. Au contraire, I 
> only want to flesh big chunks, which are, as I've now done yesterday in 
> a quick gheddon:
> 
> - browser (this includes the whole browser configuration story, the 
> absolute_url views, the custom PageTemplate implementation).

> - form (this includes form views, form configuration and the templates)
> 
> - skin (this includes the standard macros view, the standard template 
> [five_template] etc.)
>

Why is adding in browser and not in form? I'm just seriously asking the 
question as I'm not sure myself.

[snip]

> If you could, please take a look at my branch, 
> http://codespeak.net/svn/z3/Five/branch/philikon-restructuring/. Having 
> slept over the small gheddon and looking at it now, I don't feel it 
> needs any more structure, but I sure wouldn't want to miss what it has 
> now. Three subpackages isn't that bad!

Okay, you've convinced me, if we can limit it to a small amount of 
subpackages, I imagine it could improve things. From what I was hearing 
I wasn't clear we weren't going to end up with any number of packages, 
but a small amount makes sense, especially related to the page template 
issue you pointed out to me.

Thanks,

Martijn