Re: Scoping rules in WebDNA 4.0
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 29351
interpreted = N
texte = >New syntax: >[math]x=12[/math] >[search db=blah] > [founditems] > [GetMathVar name=x] <-- retrieves math variable from explicit math context > [GetFoundItemsVar name=x] <-- retrieves database field x from >enclosing [search] > [/founditems] >[/search] > >So every context which has tag values within it would need a >corresponding Get function, uniquely named, so that one could get >its values. And the syntax would *require* you to explicitly name >the context so you could get at the value (because it's this whole >lazy syntax that seems to mess people up).Sorry to be so blunt, but this would suck to have to do this!A long time ago I made a suggestion for a [variables] tag that would work like the [formvariables] context but on text and math variables as well as formvariables, and in a much simpler manner ...If a simple [variables] tag were developed to list the TYPES and names and values of all the variables in existence at that point on the page, it would be a great debugging tool. If anything, we need a great debugging tool instead of all-new syntax that's harder to use that the existing syntax ...Why not create a [variables] tag and give it some kind of preference that we can turn on and off on a folder-by-folder basis? If you do this, we can leave [variables] tags in our templates and never have to worry about them displaying a list of variable values until we actually need them. Then we simply turn the variables preference on for that folder, and all our [variables] tags display every variable in that position on the page. And when we finish debugging the problem, we turn the variables preference off so those tags no longer display anything.:)================================ Kenneth Grome, WebDNA Consultant 808-737-6499 http://webdna.net ================================############################################################# 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 To switch to the INDEX mode, E-mail to Send administrative queries to
Associated Messages, from the most recent to the oldest:
>New syntax: >[math]x=12[/math] >[search db=blah] > [founditems] > [GetMathVar name=x] <-- retrieves math variable from explicit math context > [GetFoundItemsVar name=x] <-- retrieves database field x from >enclosing [search] > [/founditems] >[/search] > >So every context which has tag values within it would need a >corresponding Get function, uniquely named, so that one could get >its values. And the syntax would *require* you to explicitly name >the context so you could get at the value (because it's this whole >lazy syntax that seems to mess people up).Sorry to be so blunt, but this would suck to have to do this!A long time ago I made a suggestion for a [variables] tag that would work like the [formvariables] context but on text and math variables as well as formvariables, and in a much simpler manner ...If a simple [variables] tag were developed to list the TYPES and names and values of all the variables in existence at that point on the page, it would be a great debugging tool. If anything, we need a great debugging tool instead of all-new syntax that's harder to use that the existing syntax ...Why not create a [variables] tag and give it some kind of preference that we can turn on and off on a folder-by-folder basis? If you do this, we can leave [variables] tags in our templates and never have to worry about them displaying a list of variable values until we actually need them. Then we simply turn the variables preference on for that folder, and all our [variables] tags display every variable in that position on the page. And when we finish debugging the problem, we turn the variables preference off so those tags no longer display anything.:)================================ Kenneth Grome, WebDNA Consultant 808-737-6499 http://webdna.net ================================############################################################# 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 To switch to the INDEX mode, E-mail to Send administrative queries to
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:
SKU lookup (1997)
ErrorMessages.db suggestion (1997)
protect tag on NT (1997)
SetLineItem (1997)
finding the next thursday (2000)
search for all (1998)
I'm new be kind (1997)
Database changes (1998)
Fun with dates (1997)
Separate SSL Server (1997)
[SearchString] problem with [search] context (1997)
Help formatting search results w/ table (1997)
Missing from Docs [folderName] (1997)
Add more fields to an existent data base (1997)
WebCat b13 CGI -shownext- (1997)
Smart caching problems with 2.1b3? (1997)
Multiple hideif's or if (2007)
REPOST: Large founditems loops (2000)
Running 2 two WebCatalog.acgi's (1996)
RAM problems, [appendfile] problems (1998)