Re: [WebMacro-user] Problems upgrading Melati to WebMacro 2.0b1

[Keats <ke...@xa...>]

I'd be willing to change the default behaviour of $Form to return empty
strings instead of nulls, as this seems more useful.  Any objections?

I would also add a method to check if a parameter exist, e.g.,
$Form.Exists.formVar.

btw, what problems are you having with FastWriter?  You should be able to
just ignore it altogether with 2.0.

Keats
----- Original Message ----- 
From: "Tim Pizey" <ti...@pa...>
To: <web...@li...>
Sent: Friday, February 27, 2004 10:09 AM
Subject: Re: [WebMacro-user] Problems upgrading Melati to WebMacro 2.0b1


On Friday 27 February 2004 2:50 pm, Keats wrote:
> Hey Tim,
>
> I'm not aware of any change to the $Form tool, but perhaps some other
> change impacted this.

Something has definitely changed since 1.1,
$Form.unusedVariable produced "", now throws exception.

>Anyway the recommended approach AFAIK is:
>
> #if ($Form.unusedVariable){ -- do something -- }
>
> This is a bit tedious.  I have added a method to the Form class called
> getNoNull(), so you can just say:
>
>   $Form.NoNull.someField
>
> which will return the value of "someField" or an empty string.  I can
> commit this if noone objects.

What about changing the behavior of $Form
(not the general behaviour of null handling) ?

>
> Keats


thanks
TimP
I am having a  horrible time with the FastWriter code.