DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=33147>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=33147 ------- Additional Comments From [EMAIL PROTECTED] 2007-11-01 05:36 ------- (In reply to comment #6) > The major question is: Do we try to mimic the behaviour of Forrest (maybe by > including XSLTs etc. using svn:externals) or do we create our own documentatin > publishing concepts? > > Maybe we can use a combination of both. For instance, the SVN logs could still > be published with Forrest - content management doesn't make much sense here. i'm not really qualified to comment, since i still haven't got the point of forrest... to me it's just a huge complication. i'd say let's drop it entirely and hack some showcase doctype for dynamic data into lenya. the data source would be "svn log --xml" (or rather, a file that is created regularly by a unix cron task), and then toss it into an xslt. i have a generic "dynamic data" doctype lying around that basically contains an xquery (i was using eXist, could easily be changed to connect to an SQL db or read a file or whatever) and has an xslt associated to it via a metadata field (this xslt is also stored in the lenya repository). that means i can add new data sources and presentation on-the-fly without re-deploying. wdyt? -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
