eTemplate as your 'macro' processor?
-=- matt
Matthew Taylor
Multimedia Learning Center
Northwestern University
> From: Hugi fiór›arson <[EMAIL PROTECTED]>
> Date: Thu, 8 May 2008 17:48:36 +0000
> To: Development WebObjects
> Subject: Macros in WO
>
> So, if you
For clarification, some code.
http://svn.karlmenn.is/Hugi/trunk/src/is/karlmenn/hugi/Application.java
user/pw : temp/temp
The method "handlemacros( WORequest, WOResponse )" is the meat.
- hugi
// Hugi Thordarson
// http://hugi.karlmenn.is/
On 8.5.2008, at 19:11, Hugi Þórðarson wrote:
Whoo
Whoops, I forgot to mention that. Yes, the whole point is to support
dynamic content. It's a content management system, and none-
programmers are using the syntax to do stuff only WO programmers would
be able to do otherwise. Like write {km:currentdate} into the content
of a web page (a data
But. What I keep thinking is: "Hugi, you're doing this the wrong
way. A Macro is nothing but a component, arguments are just bindings
- and you're reinventing WO-inline syntax in a bad way".
My first thought .. I don't see the point? If you're talking about
supporting this in dynamic content
Where to begin
If anyone here has used Confluence, you'll be familiar with its
content macros. I love them, and I've been working on integrating them
in my WO projects. I'm interested in knowing if someone has actually
implemented something like these macros in WO, bec
