Re: [Freemarker-devel] Subprojects
Generates text that depends on changing data (like dynamic HTML).
Brought to you by:
revusky
From: Daniel D. <dd...@fr...> - 2002-12-31 02:20:28
|
Tuesday, December 31, 2002, 12:16:55 AM, Jonathan Revusky wrote: > On Mon, 2002-12-30 at 17:53, Daniel Dekany wrote: >> Monday, December 30, 2002, 3:47:19 PM, Jonathan Revusky wrote: [snip] > Like, maybe we could implement the recursive template-matching type > stuff in FM, but replace what there is incrementally, so that when our > FM template hits an element that it doesn't know how to process, it > delegates to the XSLT machinery. Gradually, we would add macros and/or > transforms such that it knows how to process all elements and the XSLT > would melt away. But I don't know if this is feasible... (I somehow > doubt it...) %-/ I hardly believe that we can mix that messy-huge XSL with some FTL stuff... or rather, I hardly believe that it would be easier than writing something from scratch. > My worry is that, if we can't define a set of incremental steps from > here to there, it's really difficult. The reason I'd like to get started > on this is that I feel like a lot of secondary effects could come out of > this in terms of making FreeMarker more capable -- using it to tackle a > reasonably significant documentation generation sort of thing. That's sure. Just, this is again that we have to see the priorities of things. Personally I would like to see matured name-spaces, date/time support, terse formatting, communication between child and parent user-defined directives, good FreemarkerServlet, and all bugs in the tracker fixed. Everything else is a 100th order thing from my POV in the FM space. [snip] >> elements and roles can do (for starting, at least). What I would keep >> is the idea that the whole Manual is one big XML. > > Well, AFAICS; this is almost a non-issue. Several smaller XML's can be > treated as one big XML via entities, right? [snip] If you remember the old stuff has used separate XML for each page... now, this is what I don't want. Of course, the "one big XML" would use more physical files and entities, like the current DocBook stuff does, this was not a question. -- Best regards, Daniel Dekany |