Re: Forms Based sure, but could that mean to a custom DB table?

K. Wasetis wrote:
> OpenCMS [...]
> lacks some of the goodies that the blogger type open source CMSes (*Nuke
> types) have.

I have no interest in blogger type CMSes, I have 'stuff': DB entries,
images w/ metadata, on-line articles (HTML),  on-line documents (.PDFs etc.)
to manage and and I want to involve editor and contributors so
I'm thinking CMS.  Anyone who thinks this coming in from the 'bottom'
into CMS is inappropriate do pipe in.

My interest is not in inventing another on-line newspaper, but in
leveraging the ability of CMS to manage users, manage submission
workflow and deal with page changes even if my case is not as dynamic
as most.

> I think it's solid, especially if you have a preference
> for running/maintaining/extending Java apps over others.

That is what my 'literature survey' seemed to indicate.

[...]
> You pose a pretty specific OpenCMS question and will likely want to join the
> opencms mail-list (go to http://opencms.org and check the 'Development' menu
> at the top for the link.)

Okay, thanks I'll take a look over there.

[...]
> These docs have
> advantages, but the downside is you'll need to spend an hour to install the
> vanilla environment to run OpenCMs (Tomcat and MySQL), which a non-techie
> can handle usually. 

Already have this stuff on Win XP and various Linux boxes, so sounds like a 
great approach.

[...]
> This process will take Java development
> knowledge (which it seems you have), and while it isn't a built-in user
> feature that can be accomplished from the web interface as with some
> commercial tools

A little help from an IDE plugin was all I'd dream of, but I assume
it would actually be something involving some XML configuration and
implementing the appropriate interfaces.  The URL to the discussion forum you 
listed sounded like just the kind of peak 'under the hood'
I wanted to read before I tried any CMS and also confirms the
level of detailed required.

> there is added flexibility in being
> able to define what pre/post actions should happen when one of your content
> items is created/destroyed.

Sounds good.  Why don't all CMS do this?

Thanks also for the links and documentation discussion which I won't quote.
(Geez people can we have a little trimming of your posts, please!)

Ken, it sounds like your a big fan of OpenCMS, some of the discription
you gave is probably off topic from what I need but helped none-the-less
even if it bordered on an advertisement for OpenCMS.

thanks,
-Paul


--
http://cms-list.org/
please trim your posts.