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:
HTML Editors (1997)
missing records (1998)
RequiredFields template (1997)
Tea Room trouble (1997)
Conditional searching & displaying (1997)
Tiny Store (1998)
Associative lookup style? + bit more (1997)
[addlineitem] (1999)
Location of Browser Info.txt file (1997)
docs for WebCatalog2 (1997)
Less than or equal to........ (1997)
forms and variables (1998)
Re:HTTP header line is too long? (1997)
Help with dates (2001)
WCf2 and nested tags (1997)
Setting up shop (1997)
Am I going senile? (Price recalc based on quantity) (1997)
[protect] on NT? (1997)
Re:Signal Raised (1997)
Rounding problem (1998)