>> The company I currently work for is interested in exploring
>> cheaper/stabler/friendlier/shinier alternatives to Vignette.
>
>Woo hoo! Note that Turbine is not a CMS like Vignette is. You certainly
>could build one on top of Turbine, but it isn't one. So, don't be
>disappointed when you find out Turbine doesn't have it.
The CMS component isn't at issue (thanks for the warning, though).
I'm mostly interested in cutting over our code base to an environment
that doesn't suck ass.
>> I dug into Jetspeed, but the bulk of our page space doesn't
>> fit the portal analog. I then dug into Turbine (which on first
>> glance mirrors a perl app I helped develop 2 years ago,
>> called 'switchboard', which also implements action-events)
>> which looks juicy.
>
>Yep.
switchboard used a 'mode' or 'screen' definition file since
it was primarily a RAD tool used to create multiple screen
form submission CGI's. It was nice because you could
construct a form flow with a mode_def file and build the html
for each mode without knowing how to code. an html grunt could
do it. Which, if any, of the Apache projects most closely mimics
this functionality??? If a switchboard analog doesn't exist
I'll gladly add a java-ized version of it.
>> Unfortunately, I'm experiencing 'technical difficulties.'
>Grab the TDK. Everything is already setup and ready for you to use.
><http://java.apache.org/turbine/tdk/>
>thanks,
>-jon
you rock... thanks for the quick response.
J
