Re: project based pier

Hi, lets try to keep it as simple as possible, maybe you can just ask more questions if things are too simplistic. Doing SqueakSource in Pier, the simple way: - Each project would be a PRPage, with Wiki, Blog, News etc as children - For Blog you would use PierBlog - You implement a command (say, CreateProject, subclass of PRCommand) that adds a preconfigured set of pages (Wiki, Blog, News) to a project. - You restrict / modify the set of available commands inside a project page - You use PierUnixSecurity for users, access rights etc. - More specialized pages like Versions would perhaps be a custom subclass of PRStructure that displays itself in a special way (overriding renderContentOn:) Regarding memory / performance: I don't have real experience with this, but as long as everything fits in main memory you should be fine. Regarding persistence: you can use the Pier image-based persistency (some package in Lukas' monticello repository). That saves the whole image after executing commands (using a condition on the frequency of the saving, e.g,. at most every hour). If you are thinking about combining Pier with some other persistency mechanism (we've done Sandstone recently) things get more involved. In any case, I'd make a list of what going with Pier buys me in terms of saved development effort -- in comparison to doing it using basic seaside only. I guess that's what you're doing at the moment anyway ;-) HTH Matthias On Mon, Jan 18, 2010 at 12:43 PM, Nick Ager <nick.ager(a)gmail.com> wrote: