Hi Jim

Jim Benson wrote:
> Chris,
> 
> This is a pretty complex question, I think the really defining part is how
> much time you're willing to spend on the project is the deciding factor.

The time I worked on my own Homepage system was quite OK. So I hope it 
will better with Squeak :-)

>>From a common sense viewpoint, and a little bit of experience, I can tell
> you that if you aren't going to be using the Swiki functionality directly it
> doesn't make much sense to use Swiki as your code base. I can also tell you
> that placing Squeak code directly in your pages is a pretty brave move;
> you've exposed the entire server to the clients.  One rogue infinite loop
> submitted by a client will make your server slightly less responsive.

mmhhh ... your right! That's difficult. What about to allow calling 
defined methods? For example <squeak> printSitemap </squeak>. If the 
user is not root, or the Method doesn't exist, it is ignored

> Just a comment on your point: "pages sit in a tree (swiki has a graph
> structure)". That part might be challenging.

I've done this before. Shouldn't be too difficult :-)

> Jim
> 
> BTW, I think you came would be happier with Zope than SWiki from what you're
> describing.

If Zope is really better than Squeak, then I will stay in PHP and let it be.

> ----- Original Message -----
> From: "Chris Burkert" <christian.burkert at s2000.tu-chemnitz.de>
> To: <squeak-dev at lists.squeakfoundation.org>
> Sent: Tuesday, March 04, 2003 9:27 AM
> Subject: [Q] CMS/Swiki development
> 
> 
> 
>>Hi
>>
>>I plan to develop a kind of Swiki that is more what I want (nothing
>>against swiki, but it's not really the thing I want :-) I think the best
>>is with commanche.
>>
>>1) What would you say is the best starting point (It should be faster
>>than swiki)?
>>- start from scratch
>>- change the existing swiki
>>- build with seaside
>>
>>2) What do you say about regular expressions. Is the plugin build in in
>>the default VM or does the admin has to compile a new VM? Then I had to
>>use Streams.
>>
>>Here's what I want.
>>- (Commanche) sessions
>>- pages sit in a tree (swiki has a graph structure)
>>- userlogin
>>- permissions (from user to admin)
>>- permissions are bound to a user/page combination and are
>>   inherited down the tree.
>>- Squeakcode in <squeak> ^'Hello World!' </squeak>
>>- only few special characters like
>>- ... other points
>>
>>about users
>>- User can see additional infos
>>- Editor can edit existing pages
>>- Author can create new pages
>>- Root can do everything
>>it should be easy to integrate new Userschemes
>>
>>Regards
>>            Chris Burkert
>>
>>PS: I built something similar in PHP (running on my Homepage) but PHP
>>suckz! So the important question is 1)
>>--
>>------------------------------------------------------------------------
>>Student of applied Computer Science at Chemnitz University of Technology
>>      http://www.chrisburkert.de/            chris at chrisburkert.de
>>------------------------------------------------------------------------
>>"I invented the term Object-Oriented, and I can tell you I did not have
>>  C++ in mind." - Alan Kay --> http://www.whysmalltalk.com/

Regards
            Chris Burkert
-- 
------------------------------------------------------------------------
Student of applied Computer Science at Chemnitz University of Technology
      http://www.chrisburkert.de/            chris at chrisburkert.de
------------------------------------------------------------------------
"I invented the term Object-Oriented, and I can tell you I did not have
  C++ in mind." - Alan Kay --> http://www.whysmalltalk.com/