[Seaside] Re: What's the (technical) purpose of adding t/seaside/ to the path

Jason Johnson jbjohns at libsource.com
Fri Jul 20 13:51:51 UTC 2007

Michael Lucas-Smith wrote:
>> But the thing is, they will probably want *something*, and as soon as 
>> you want that you are talking about configuration.  But again, I 
>> point back to the fact that if you are deploying then someone has to 
>> know how to deploy with your chosen web server, whether that be 
>> Apache, Webtoolkit, Commanche, whatever.  And knowing how to rewrite 
>> URLs is part of knowing your deployment.
> That's a fair argument. I still think you'll turn away some pedants by 
> having the URL there in the default image, but it is a nice advert. 
> I'll just note it as something to be document for VisualWorks.
> Michael
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Actually you "in the default image" gave me an idea.  Can't the people 
making the packages for the various platforms have the install pop up a 
box asking where the user wants the URL?  In fact, doesn't it already on 

More information about the Seaside mailing list