Re: [/application] error?
This WebDNA talk-list message is from 1997
It keeps the original formatting.
numero = 11582
interpreted = N
texte = >Okay ... because I put this in one of my templates and it seems to work >fine ... > >[search db=control.db&[hideif [master]=change]ne[/hideif][showif >[master]=change]eq[/showif]userdatarq=randy&numtype=num&asnumsort=1] > >... but if you don't think I can rely on this technique to work all the >time, then I will watch out. > >Oh, maybe it works fine because the showif/hideif's are inside the >[search], so they are actually forced to be evaluated first ... because >enclosed tags and contexts are evaluated before their enclosing contexts?Yes, it is specifically designed to work that way (and yes you can rely on that working). Because the enclosure is 'perfect', meaning that the [hideif]..[/hideif] is completely contained within the parameters to the search context.You can even put [include] or [AppleScript] inside the parameters to any context. Whatever those things evaluate to in WebDNA is what will be substituted before passing those parameters to the context. Anywhere you can put an [xxx] variable, you can also put [xxx]...[/xxx] contexts. Whatever text the context evaluates to is what gets substituted there in the HTML.Grant Hulbert, V.P. Engineering | ===== Tools for WebWarriors ===== Pacific Coast Software | WebCatalog Pro, WebCommerce Solution 11770 Bernardo Plaza Court | SiteEdit Pro, SiteCheck, PhotoMaster San Diego, CA 92128 | SiteGuard 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com
Associated Messages, from the most recent to the oldest:
>Okay ... because I put this in one of my templates and it seems to work >fine ... > >[search db=control.db&[hideif [master]=change]ne[/hideif][showif >[master]=change]eq[/showif]userdatarq=randy&numtype=num&asnumsort=1] > >... but if you don't think I can rely on this technique to work all the >time, then I will watch out. > >Oh, maybe it works fine because the showif/hideif's are inside the >
[search], so they are actually forced to be evaluated first ... because >enclosed tags and contexts are evaluated before their enclosing contexts?Yes, it is specifically designed to work that way (and yes you can rely on that working). Because the enclosure is 'perfect', meaning that the
[hideif]..[/hideif] is completely contained within the parameters to the search context.You can even put
[include] or [AppleScript] inside the parameters to any context. Whatever those things evaluate to in WebDNA is what will be substituted before passing those parameters to the context. Anywhere you can put an [xxx] variable, you can also put [xxx]...[/xxx] contexts. Whatever text the context evaluates to is what gets substituted there in the HTML.Grant Hulbert, V.P. Engineering | ===== Tools for WebWarriors ===== Pacific Coast Software | WebCatalog Pro, WebCommerce Solution 11770 Bernardo Plaza Court | SiteEdit Pro, SiteCheck, PhotoMaster San Diego, CA 92128 | SiteGuard 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com
Grant Hulbert
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:
Not reading code (1997)
WebCat editing, SiteGuard & SiteEdit (1997)
External Images (1998)
OK, here goes... (1997)
Size images (2002)
Contain in search (2005)
How do you hide [math]stuff[/math] (1997)
[CreateDate], [ListFiles] context tag broken on Linux? (2000)
UPPERCASE (1997)
Group Updates (1998)
Showif, Hideif reverse logic ? (1997)
Quantity (1998)
Trouble with carts (2000)
Hosts who have upgraded to v5.0? (2003)
Fields font size (2003)
Associative lookup style? (1997)
Re[2]: When do we get to request new features? (1999)
Re[2]: 2nd WebCatalog2 Feature Request (1996)
carriage returns in data (1997)
Card clearance, problems - solutions? (1997)