Re: #setprops directive committed

Eric got it right.  I didn't want to weigh down the directive with too many
features and options.  But the include thing is handy and we might consider it
for a future enhancement.  A cool thing with the #include approach is that you
can have nested includes, so maybe a generic template sets some properties and
then includes others from a locale subdirectory for example.

btw,

It looks like I got this code committed just in the nick of time, as my laptop
got ripped off last night. :-{

Unfortunately I don't think I have a good backup for some of the other WM stuff
I've been playing with.  Those of you who sent me code to look at, please send
it again.  I was close to committing new exception classes, and the improved
logging class and DefaultDirective.  Also, Marc, if you still have the Taglibs
stuff I sent you, I'd appreciate a copy back.

Someday I'll learn to keep backups!

Keats

Quoting "Eric B. Ridge" <[email protected]>:

> On Oct 18, 2005, at 12:52 AM, Marcello H wrote:
> 
> > The #setprops directive would also be nice if the data is really  
> > coming
> > out of a property file; something like
> >
> > #setprops as file "myprops.ini"
> 
> Just do this:
> 
> #setprops $p {
>      #include as text "myprops.ini"
> }
> 
> Just note that "myprops.ini" will need to be in your "TemplatePath"
> 
> eric
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads, discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________
> Webmacro-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/webmacro-user
> 




-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl