<div dir="ltr">I added a lot of logic on SeasidePlatformSupport in Seaside, to handle all the development vs. production config differences.<br>Obviously a lot of this is specific to our application, but it would make sense (in my mind) to have our subclass of WAAdmin, rather than an extension of SeasidePlatformSupport (we still run Seaside 2.6 at the moment).<br>
<br>What would be interesting to know is what differentiates development mode from production mode ? And how would one specify "switch to production" actions ? I'm thinking of things like: don't register the "file libraries" but let apache (or another web server) serve them for you, etc...<br>
<br>Cheers,<br><br>Yann<br><br><div class="gmail_quote">On Mon, Sep 22, 2008 at 7:18 PM, Julian Fitzell <span dir="ltr"><<a href="mailto:julian@fitzell.ca">julian@fitzell.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Mon, Sep 22, 2008 at 8:02 PM, Lukas Renggli <<a href="mailto:renggli@gmail.com">renggli@gmail.com</a>> wrote:<br>
>> More than once, I've wanted a single "button" that I could press that would<br>
>> turn on "production mode." Production mode would turn off the tool bar<br>
>> (leaving the development tools intact) in _all_ applications. Production<br>
>> mode would switch the error handler to a production ready error handler - a<br>
>> simple error message and a stack dumped to a log - for all _all_<br>
>> applications. "Production mode" could also refuse to server up the config<br>
>> page and could even disable the default page for seaside (the browser).<br>
>> Inspectors and _all_ other 'dangerous' development tools would become<br>
>> password protected in production mode.<br>
><br>
> That would be something for WAAdmin (formerly called WAEnvironment).<br>
> And could potentially be exposed to the morphic UI Michael is writing<br>
> ;-)<br>
<br>
</div>Yup, that's what I was thinking. I want to see WAAdmin built out into<br>
a nice suite of useful commands that can then be called by a morphic<br>
UI, a web ui, or a workspace.<br>
<font color="#888888"><br>
Julian<br>
</font><div><div></div><div class="Wj3C7c">_______________________________________________<br>
seaside-dev mailing list<br>
<a href="mailto:seaside-dev@lists.squeakfoundation.org">seaside-dev@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev" target="_blank">http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev</a><br>
</div></div></blockquote></div><br></div>