5.0 feature request: Macro

This WebDNA talk-list message is from

2001

It keeps the original formatting. numero = 40199
interpreted = N
texte = At 10:56 AM -0800 11/20/2001, Scott Anderson wrote:>Yes, but we are not ready to announce an ETA as this time.>>The 4.5 feature set is fixed, but we are still open to suggestions for the>5.0 feature set. I have been keeping track of feature suggestions made on>this list, so please keep them coming!I mentioned this a long while back, so it could be on your list, but here's my requested feature of the day...[macro name=XXX¶m1=YYY¶m2=ZZZ...]macro contents with access to passed-in parameters [YYY] and [ZZZ][/macro]This would essentially allow us to extend the WebDNA language through interpreted code snippets. Functionally it's the same as calling an INCLUDE file with parameters, but syntactically the calls look like regular WebDNA commands.For example, I've got an INCLUDE file that checks whether an entered email address is syntactically valid. Currently, I call it like this:[showif F=[include ^include/gCheckEmail&iAddress=[url][myAddressVar]]] ** The email is bad **[/showif]With the macro definition, I could define the following:[macro name=ValidEmail¶m1=address][include ^include/gCheckEmail&iAddress=[url][address][/url]][/macro]Then, I could check an email with this syntax:[showif F=[ValidEmail address=[url][myAddressVar][/url]]] ** The email is bad **[/showif]The benefits increase with the addition of more parameters.I use include files constantly for creating modular code. Having a way to define these as macro calls within the WebDNA language would make this much more fluid.It would also be nice to be able to define end-context code for situations where a context-format is more appropriate for the macro. For example, I often use a convertchars database to strip white space (tabs and returns) from contexts like replace, allowing me to enter the code in a more readable format. This looks like:[replace db=my.db&eqfielddatarq=[value]][ConvertChars db=^db/gTrim.db] field1=[value1] &field2=[value2] &field3=[value3][/ConvertChars][/replace]If I could define the macros:[macro name=Trim][ConvertChars db=^db/gTrim.db][/macro][macro name=/Trim][/ConvertChars][/macro]Then my code could look like this:[replace db=my.db&eqfielddatarq=[value]][Trim] field1=[value1] &field2=[value2] &field3=[value3][/Trim][/replace]- Brian-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/ Associated Messages, from the most recent to the oldest:

5.0 feature request: Macro (Brian Fries 2001)

At 10:56 AM -0800 11/20/2001, Scott Anderson wrote:>Yes, but we are not ready to announce an ETA as this time.>>The 4.5 feature set is fixed, but we are still open to suggestions for the>5.0 feature set. I have been keeping track of feature suggestions made on>this list, so please keep them coming!I mentioned this a long while back, so it could be on your list, but here's my requested feature of the day...[macro name=XXX¶m1=YYY¶m2=ZZZ...]macro contents with access to passed-in parameters [YYY] and [ZZZ][/macro]This would essentially allow us to extend the WebDNA language through interpreted code snippets. Functionally it's the same as calling an INCLUDE file with parameters, but syntactically the calls look like regular WebDNA commands.For example, I've got an INCLUDE file that checks whether an entered email address is syntactically valid. Currently, I call it like this:[showif F=[include ^include/gCheckEmail&iAddress=[url][myAddressVar]]] ** The email is bad **[/showif]With the macro definition, I could define the following:[macro name=ValidEmail¶m1=address][include ^include/gCheckEmail&iAddress=[url][address][/url]][/macro]Then, I could check an email with this syntax:[showif F=[ValidEmail address=[url][myAddressVar][/url]]] ** The email is bad **[/showif]The benefits increase with the addition of more parameters.I use include files constantly for creating modular code. Having a way to define these as macro calls within the WebDNA language would make this much more fluid.It would also be nice to be able to define end-context code for situations where a context-format is more appropriate for the macro. For example, I often use a convertchars database to strip white space (tabs and returns) from contexts like replace, allowing me to enter the code in a more readable format. This looks like:[replace db=my.db&eqfielddatarq=[value]][ConvertChars db=^db/gTrim.db] field1=[value1] &field2=[value2] &field3=[value3][/ConvertChars][/replace]If I could define the macros:[macro name=Trim][ConvertChars db=^db/gTrim.db][/macro][macro name=/Trim][/ConvertChars][/macro]Then my code could look like this:[replace db=my.db&eqfielddatarq=[value]][Trim] field1=[value1] &field2=[value2] &field3=[value3][/Trim][/replace]- Brian-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/ Brian Fries

DOWNLOAD WEBDNA NOW!

5.0 feature request: Macro

2001

Top Articles:

Related Readings: