Re: [Openinteract-help] OpenInteract as CMS

[Andreas N. <an...@kl...>]

Hi Heiko,

from our experiences with OI 1 you should be able to do that. We are 
planning to release a package called roma at some point of time, which is 
our solution for CMS and other topics. Currently, we are still using OI 1 
though, but roma is not tightly bound to OI 1.

What it does is a framework to define content types and links between 
content items.
Each content type can have attributes which you assign can assign s.th. like 
htmlarea ( we use the commercial tool Editlet, but htmlarea also works ).
From these links you can create trees of content including security stuff 
( not sys_security... ) and full text search.

The system is in production use BUT... there is not much documentation. If 
you are interested and /or would like to contribute ( .. like documentation 
;-) ), then we can send you the package. But be warned: it has a learning 
curve..

For the other question: you could use Chris Winters Workflow.pm from CPAN to 
create CMS workflows. Alternatively we have a framework for this called 
NATS - but it also lacks documentation. We will merge this with Workflow.pm 
at some point of time.

cheers

Andreas
----- Original Message ----- 
From: "Heiko Klein" <Hei...@gm...>
To: <ope...@li...>
Sent: Friday, September 10, 2004 2:49 PM
Subject: [Openinteract-help] OpenInteract as CMS


> Hi,
>
> I'm new to openinteract and just ran the tutorial of OI2. OI2 seems to be 
> a very nice perl application server and I would like to continue with it. 
> My main application running on OI2 should be a CMS system, with some 
> applications added later.
>
> Does there exist a CMS framework on top of OI2? (Similar to plone for 
> Zope, OpenCMS for J2EE, ...) OI2 has its 'pages'-example, but I wouldn't 
> call those a full CMS, since they are more or less just a different way of 
> accessing the file-system. I would like to have:
>
> 1) access-restrictions of pages/directories (with users only seeing the 
> places they are allowed to write to)
> 2) setting of expiration dates (with notification when page expires)
> 3) web-based page editor GUI
> 4) versioning system for all pages (pagewise)
> 5) batch uploading of files (i.e. graphics, older pages...)
>
> 1) and 2) seem to be partly included. 3) could be as simple as a 
> javascript-tool, i.e. 
> http://www.interactivetools.com/products/htmlarea/license.html
> 4) shouldn't be to much work. 5) could be solved by uploading zip files, 
> which get unpacked. But I would prefer a API to OI2 (i.e. SOAP) to be able 
> to script OI2 from a remote machine.
>
> I would like to hear if this will be possible for me (decent perl 
> programmer without experience in OI but some experience in 
> web-applications/databases) to create with OI2 within the next 3-6month, 
> or if I should use a specialized CMS i.e. Bricolage for the static pages, 
> and OI2 for the dynamic applications (news/blogs/fora/etc.)
>
> Best regards,
>
> Heiko
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
> Project Admins to receive an Apple iPod Mini FREE for your judgement on
> who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: 
> Sept. 13. Go here: http://sf.net/ppc_contest.php
> _______________________________________________
> openinteract-help mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openinteract-help
>