OpenACS 4.0... OpenACS 4.0... I must keep reminding myself of this
vast effort that many have undertaken; but it is hard to do when my
days (and nights) are spent in 3.x code. I did not think to
check into the implementation (installation+configuration) model for
4.0. Have my ideas already been addressed; i.e. "a library/repository
of complete out-of-the-box OpenACS configuration solutions"?
I really like Don's idea of a "configuration wizard" although I
suspect building a generic-does-it-all-OpenACS-configuration-tool is
more complex than just building 2-3
you-get-what-you-see-and-better-like-it-OpenACS-configuration
solutions (i.e. the new openacs.org), no?
Perhaps we could agree on 1 basic (highly useful) OpenACS
configuration model and work toward building the config scripts for
it, to start; is this the new openacs.org model, Talli?
4.0 presents another issue to consider... how much effort do we put
forth on building a "configuration wizard" or scripts for 3.x that
will be of value? Should I, instead, focus my time learning the 4.0
architechture, so that my efforts (on config scripts) have a more long
term impact?
Don, I will be happy to transcribe my ultra-mini-howtos to the
computer (from napkins and BK whopper wrappers) and forward them to
the community, or rather their links, no? Their purpose is to guide
the somewhat-initiated OpenACS site-manager through the absolute
minimum steps required to setup key OpenACS modules. Despite the great
efforts of those who created web-forms (and all the config options),
my users (my clients) find them too confusing, so I had to create
something more simple. I am not sure how helpful they will be, but I
will let the community decide this for themselves.
I look forward to your feedback! -nate
