Hi Daniel,


> Christopher,
>      Your idea sounds great to me, as I am looking to create (or assemble
> it from parts) a content management solution with content management,
> workflow, categorization and personalization, and I am starting to look
> into the apache projects to get parts from it.

Something like the Sybase EP ;-)  
If you are interesting to help me, you are welcome ! I have the same goal & problems.

>      Have you evaluated other projects? (like struts, cocoon, etc)  Why
> have you decided to use turbine?

Turbine is easy to understand and powerfull. Turbine & Velocity are well integrated & 
strong in point of view of OO.
If you are JSP oriented, yes, struts should be interesting otherwise use Velocity for 
simplicity. 
Turbine contains different tools called services that can greatly help you for your 
web app (like security, upload, localization, caching...).
Furthermore, Turbine implements a nice O/R mapping - called Torque -  that you can use 
into your own servlet.

>      If you can send me your small demo, it'll be great for me.

Ok - Give me one week because the code is not yet stable. It is just the starting 
point for this integration.
We can try to make together a proposal for building this integration. What do you 
think about this ?

What I plan to finish after this week is : 
- A new Turbine service which is give you an access to the slide API from your own 
Turbine action classes (retrieve, create, lock, ...).
  Action classes are the controllers defined in the Turbine MVC model.
- Use Velocity templates to display the slide content structure (tree, catalog list)
- Admin tools to add/modify/drop catalogs, contents & their properties + apply 
security (mainly who can access/manage what ?)
- Of course everything is based on MVC.
- Integrate the turbine & slide security (the big deal).

What it is missing ( TO DO - need help ) :
- integrate other slide API for Locking, versioning & later workflow. It is mainly 
building other Velocity templates.
- Building jetspeed portlets used in the end-user pages & admin pages. 
  One portlet can be used to see the Slide content tree and another one for the 
workflow management. Need more discussion.
- What are your requirements for the personalization ? Jetspeed portlets are suffisant 
or not ? 
- Check/Use with webdav clients like Office 2000 or others.

In the mean time, if you can test turbine/slide you will see it works fine on jaguar 
;-)

Christophe

__________________________________________________________________
Get your own FREE, personal Netscape Webmail account today at 
http://webmail.netscape.com/

Reply via email to