Hello and Happy New Year to the list.

Thank you Julian, Nick, and Lukas for the port to Seaside 3.0.

I'd like to give a hand to finalize this port, and started by "Pier-Setup" as follows:

- Dependencies (in addition to the core Pier packages): Pier-Blog, Pier-Documents, Pier-Google, and Pier-Book.
- Starting point: http://hudson.lukas-renggli.ch/job/Seaside%203.0/.
- Loaded from http://source.lukas-renggli.ch/pier2: Pier-Blog-NickAger.135 and Pier-Documents-NickAger.17.
- Loaded from http://source.lukas-renggli.ch/pieraddons: Pier-Google-lr.16, Pier-Book-lr.112, Pier-Setup-lr.71. Had just to edit one method (please see the attached file).
- Executed "PRLoader setupPier"
- Pointed to http://localhost:8080/pier. As far as I could test, it just works fine, including Gadgets.
- Loaded Pier-Design-lr.8 to have the "Edit Design" command. It works, except for the stylesheet rendering issue already reported by Nick.

Questions:
1) Would it make sense to isolate PRBookDistribution in a separate package, to avoid the current dependency between Pier-Setup & Pier-Book?
2) Would it make sense to have a PierBasicDistribution, without dependencies to Pier-Blog, Pier-Documents, Pier-Google? (PierDistribution could obviously then be a subclass of PierBasicDistribution).
3) Should I upload the above packages?
3.b) If yes, in which repository: http://source.lukas-renggli.ch/pier2 or http://source.lukas-renggli.ch/pier2-addon? For the moment all core and addon packages are in the same repository, which is somehow more practical compared to Pier 1.

Remaining issues:
A) Load scripts in PRLoader need to by adapted to the new repositories.
B) Testing PREventDistribution and PRBookDistribution.

I'm going to take care of (B).

Cheers,
Reza