Re: Don't know if this is a sily question...
This WebDNA talk-list message is from 2003
It keeps the original formatting.
numero = 50780
interpreted = N
texte = I'm not sure what you mean by careful crafting when all you have to do is wrap a [raw] context around the text variable value. There's nothing in this simple task that I would consider careful crafting any more than any other common webdna coding task.Also, you seem to be suggesting that the function solution can perform 'recursively' but the text variable solution cannot. I have to disagree with this. I have never seen a situation in which the text variable solution does not work recursively. Do you have an example that you can post to the list so we can see what you're talking about here?My conclusion is that the text variable solution does the exact same thing as the function solution -- and it works in v4 and v5 -- unlike the function solution which works ONLY in v5.Oh, and if there is any question as to the use of the text variable solution in multiple pages, it is a simple task to put the code into an include file -- so it can be included in *any* webdna template on the same server.Furthermore the text variable solution can be used on multiple webdna servers -- by using tcpconnect to retrieve the template that has the text variable code in it, and then interpreting that code inside the local webdna template on the local server.>Yes, the text variable method is a useful technique, but takes >careful crafting. I also have used similar techniques for years, but >the new [function] context makes it sooo much easier, especially >when you get more complex with the reusable code blocks, and when >you want to do something recursive. It's worth the price of >admission for me. > >- brian > >On Thursday, May 29, 2003, at 10:18 AM, Kenneth Grome wrote: > >>>As a related comment, using WebDNA 5 I find myself more often >>>using [function]s where I used to use [include]s to handle >>>recurring tasks. The formal use of parameters, the local scope >>>variables, and the ability to define functions within the page >>>itself as well as in a shared include file are compelling features. >>> >>>As a simple example: >>> >>>[function name=MyLink] >>>[return]
>>db=....&value=[thevalue]&returnfield=ID]>[lookup >>>db=....&value=[thevalue]&returnfield=title][/return] >>>[/function] >>> >>>[search ...] >>>[founditems] >>>[MyLink thevalue=[whatever]] >>>[/founditems] >>>[/search] >>> >>>- brian >> >> >>I've been doing something similar for years, without v5's function context: >> >>[text]myLink=[raw]
>db=....&value=[thevalue]&returnfield=ID]>[lookup >>db=....&value=[thevalue]&returnfield=title][/raw][/text] >> >>[search ...] >>[founditems] >>[myLink] >>[/founditems] >>[/search] >> >>This has always been an easy way to create a variable once at the >>top of the page, and then use it any number of times further down >>on the same page -- while preventing the webdna code inside the >>text variable from being interpreted until the variable tag is used >>further down on the page -- such as inside the founditems context >>in this example. >>-- >> >>Sincerely, >>Kenneth Grome >>------------------------------------------------------------- >>My programmers will write WebDNA code for you at $27 an hour! >>------------------------------------------------------------- >> >>------------------------------------------------------------- >>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://webdna.smithmicro.com/ >> > > >------------------------------------------------------------- >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://webdna.smithmicro.com/ -- Sincerely, Kenneth Grome ------------------------------------------------------------- My programmers will write WebDNA code for you at $27 an hour! -------------------------------------------------------------------------------------------------------------------------- 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://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
I'm not sure what you mean by careful crafting when all you have to do is wrap a [raw] context around the text variable value. There's nothing in this simple task that I would consider careful crafting any more than any other common webdna coding task.Also, you seem to be suggesting that the function solution can perform 'recursively' but the text variable solution cannot. I have to disagree with this. I have never seen a situation in which the text variable solution does not work recursively. Do you have an example that you can post to the list so we can see what you're talking about here?My conclusion is that the text variable solution does the exact same thing as the function solution -- and it works in v4 and v5 -- unlike the function solution which works ONLY in v5.Oh, and if there is any question as to the use of the text variable solution in multiple pages, it is a simple task to put the code into an include file -- so it can be included in *any* webdna template on the same server.Furthermore the text variable solution can be used on multiple webdna servers -- by using tcpconnect to retrieve the template that has the text variable code in it, and then interpreting that code inside the local webdna template on the local server.>Yes, the text variable method is a useful technique, but takes >careful crafting. I also have used similar techniques for years, but >the new [function] context makes it sooo much easier, especially >when you get more complex with the reusable code blocks, and when >you want to do something recursive. It's worth the price of >admission for me. > >- brian > >On Thursday, May 29, 2003, at 10:18 AM, Kenneth Grome wrote: > >>>As a related comment, using WebDNA 5 I find myself more often >>>using [function]s where I used to use [include]s to handle >>>recurring tasks. The formal use of parameters, the local scope >>>variables, and the ability to define functions within the page >>>itself as well as in a shared include file are compelling features. >>> >>>As a simple example: >>> >>>[function name=MyLink] >>>[return]>>db=....&value=[thevalue]&returnfield=ID]>[lookup >>>db=....&value=[thevalue]&returnfield=title]
[/return] >>>[/function] >>> >>>[search ...] >>>[founditems] >>>[MyLink thevalue=[whatever]] >>>[/founditems] >>>[/search] >>> >>>- brian >> >> >>I've been doing something similar for years, without v5's function context: >> >>[text]myLink=[raw]>db=....&value=[thevalue]&returnfield=ID]>[lookup >>db=....&value=[thevalue]&returnfield=title]
[/raw][/text] >> >>[search ...] >>[founditems] >>[myLink] >>[/founditems] >>[/search] >> >>This has always been an easy way to create a variable once at the >>top of the page, and then use it any number of times further down >>on the same page -- while preventing the webdna code inside the >>text variable from being interpreted until the variable tag is used >>further down on the page -- such as inside the founditems context >>in this example. >>-- >> >>Sincerely, >>Kenneth Grome >>------------------------------------------------------------- >>My programmers will write WebDNA code for you at $27 an hour! >>------------------------------------------------------------- >> >>------------------------------------------------------------- >>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://webdna.smithmicro.com/ >> > > >------------------------------------------------------------- >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://webdna.smithmicro.com/ -- Sincerely, Kenneth Grome ------------------------------------------------------------- My programmers will write WebDNA code for you at $27 an hour! -------------------------------------------------------------------------------------------------------------------------- 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://webdna.smithmicro.com/
Kenneth Grome
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Where's Cart Created ? (1997)
any limitations on # of users.db entries (1999)
remotely add + sign (1997)
process SSI (1998)
calculating tax rates, mail order solutions and version 2 (1997)
New index for docs (1997)
Re:How to Display text in empty fields (1997)
WebCat2 - Getting to the browser's username/password data (1997)
WebCatalog and WebMerchant reviewed by InfoWorld (1997)
no global [username] or [password] displayed ... (1997)
looping through the headers of an orderfile (2000)
Pricing (1998)
Catalogs and W* (1996)
Very serious bug with the [protect] tag (2003)
Forms Search Questions (1997)
emailer w/F2 (1997)
WebCat2b13 Mac plugin - [sendmail] and checkboxes (1997)
Kaaaaahhhhhhhnnnnnnn! (1997)
AutoCommit Preference? (1998)
HELP WITH DATES (1997)