Discussions

News: Open Source CMS Daisy 1.2 released

  1. Open Source CMS Daisy 1.2 released (4 messages)

    New in this release are:

    In the Daisy Wiki:

    * an easy-to-use graphical site navigation tree editor to define site hierarchies and navigation
    * user self-registration with password and account reminder
    * a general document commenting facility with public and private comments
    * enhanced support for human-readable website URLs

    In the repository:

    * comprehensive support for arbitrary-sized document parts (or "BLOBs"), with streaming support both on front- and backend (making Daisy capable of hosting media libraries)
    * generalized database access layer to easily run Daisy on top of any standards-conforming relational database engine
    * improved full-text indexing support for MS Office document formats

    And of course, many other minor feature enhancements, issues and performance improvements have been implemented as well.

    For the next release (summer 2005), planned features are:

    * publish-only website publishing for easy publication of non-editable Daisy sites (using the Wiki as a powerful editing application)
    * Daisy Books: management and production of manuals and paper documentation
    * more sophisticated repository versioning and querying
    * support for facetted classification and navigation using Daisy's metadata support
    * furthermore, we expect to upgrade Daisy's internals to reflect the current state of the art in component containers and messaging frameworks

    Daisy is available under the Apache License 2.0 from http://cocoondev.org/daisy/, with commercial support services available from http://outerthought.org/daisy.html

    Threaded Messages (4)

  2. congratulations[ Go to top ]

    For all who involved in this amazing CMS solution: CONGRATULATIONS
    ok,it is really good and best of all it is really well documented,which is rarly found in the opensource world

    actually i have a couple of questions to ask..
    instead of the database backed repository ,are u planning to use webdav as a storage ,if so it will give u a native HTTP API
    second ,if i wanna provide a complete user interfacewhere can i begin with in the wiki api? actually where is the classes that do the real work, and where can we inject or hook an MVC framwork,where it can really find its actions in the API
    thanks
    joe
  3. congratulations[ Go to top ]

    @Joe: the Java API is documented here: http://cocoondev.org/daisy/docs/repository/technical/28.html + there's JavaDoc as well of course. If you want to take a look at how we hook the Java API into Cocoon's pipeline machinery, have a look at the different "Apples" in http://svn.cocoondev.org/viewsvn/trunk/daisy/applications/daisywiki/frontend/src/java/org/outerj/daisy/frontend/?root=daisy Apples are a bit comparable to Servlets, only they call upon a Cocoon pipeline upon return. That's "quite" MVC-like IMHO. ;-)

    We don't have any plans w.r.t. WebDAV ATM - we do provide a ReST API ourselves: http://cocoondev.org/daisy/docs/repository/technical/21.html

    Thanks for the nice comments!
  4. Nice, but ...[ Go to top ]

    The "out of the box" functionality of daisy is fantastic if you want some nice content/document management and wiki type functionality. Very frustratingly I have found the big problem comes when you try to configure or extent it. Changing the logo is pretty straight forward, but after that it seems to be a steep up hill from there. Extending functionality (of the DaisyWiki) requires delving into the murky depths of cocoon. What Daisy would benefit from is a clear "plugin" architecture, but my guess is that this is not possible or quite difficult using Cocoon.

    I'm interested to see what "current state of the art in component containers and messaging frameworks" delivers.
  5. Nice, but ...[ Go to top ]

    @Richard: in the next release, we plan to work on the publishing side of things. That said, there's little chance we'll switch away from Cocoon in favor of other frameworks out there, since it's far easier for us to support people willing to invest a little bit of time in learning the Cocoon way of things, rather than providing people with fashionable web framework machinery that gives them the ability to shoot themselves in the feet. The XSLT-skinning machinery for skinning is pretty easy to use ATM, but we plan to make it easier to produce completely differently looking websites using Daisy (and Cocoon). But the Java API is equally well supported of course, and could be used in any webframework out there, if it is able to easily render web pages out of XML data. HTH!