Hi littleJava,
thanks for the feedback - Indeed, our demo CSS was only tested with IE 7 and firefox - IE6 doesn't like it.
This is weird, since we are using the "standard" Effect.toggle(..)
function of the latest well-known scriptaculous/prototype library
Concerning the second question: why the web site brasato is not built with the brasatoframework.?
Brasato evolved from an LMS and has server-side state using cookies.
We have a bookmark feature using a "permalink" link, but the urls that the framework generates are not yet bookmarkable.
Therefore Brasato is more suited for session-based applications, and
not for a cms which needs to be session less so that google and co. can
index it properly.
This is a dilemma indeed, and the OLAT team is thinking about how an
application can easily interweave between read-only fixed-url pages and
complex state-ful workflows in a single architectural approach
(together with "only sign-on when needed" feature request)
But you are completely right: "eating our own dogfood" also in the CMS part would be nice.
There is an OLAT subproject (see
http://bugs.olat.org/jira/browse/OLATCMS), which is a stand-alone 100%
java small-footprint CMS.
Have a nice day and cu on the OLAT Mailinglist ;)
Felix