Re: hideif/showif causes error if wrapped around searches
This WebDNA talk-list message is from 2003
It keeps the original formatting.
numero = 52858
interpreted = N
texte = Yes, it was more of a wishful thinking that the hideif could work like a comment tag and either hide or unhide code. Hmm, just thought, why not use: [showif [hidesearch]=T][!][/showif] [search....] [showif [hidesearch]=T][/!][/showif] ? Matthew A Perosi wrote: > Well, I'd say from a programming point of view your idea is just a > wrong > use of nested programming code. > Even HTML gets upset with you now-a-days when you incorrectly nest > tags. > Don't get me wrong, I think your idea is rather cool, but I just don't > think any of the programming languages I know would allow > function/procedure/code nesting like what you are looking for. > > End result: rewrite the code OR start using include files more so > your replicated code only shows up 1 time per template; only when > needed. > > Matt Perosi > > Gary Krockover wrote: > >> I know I'll never find this answer in the archives and I don't >> recall it >> even coming up before but I'm sure others have noticed this behavior. >> >> If you wrap a hideif or a showif around a [search] and it's closing >> [/search], you'll get an error about the nesting of the tags >> hideif/showif >> and /search. Por que? >> >> Example: >> >> [hideif [hidesearch]=T] (and it does) >> [search db=...] >> [founditems] >> [/hideif] >> Something else >> [hideif [hidesearch]=T] >> [/founditems] >> [/search] >> [/hideif] >> >> What am I trying to do? Add a sort for a page without having to >> make two >> pages with different searches on each. So a form post, with the >> search and >> a hidden field of hidesearch=T. The page is the home page, so when >> it is >> first hit I want the search performed automatically and sorted one >> way, user can click a button to sort it the other way, hiding the >> original search and using the one in the form. >> >> What's the preferred method here? >> >> Thanks, >> GK >> >> >> ------------------------------------------------------------- >> 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/ ------------------------------------------------------------- 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:
Yes, it was more of a wishful thinking that the hideif could work like a comment tag and either hide or unhide code. Hmm, just thought, why not use: [showif [hidesearch]=T][!][/showif] [search....] [showif [hidesearch]=T][/!][/showif] ? Matthew A Perosi wrote: > Well, I'd say from a programming point of view your idea is just a > wrong > use of nested programming code. > Even HTML gets upset with you now-a-days when you incorrectly nest > tags. > Don't get me wrong, I think your idea is rather cool, but I just don't > think any of the programming languages I know would allow > function/procedure/code nesting like what you are looking for. > > End result: rewrite the code OR start using include files more so > your replicated code only shows up 1 time per template; only when > needed. > > Matt Perosi > > Gary Krockover wrote: > >> I know I'll never find this answer in the archives and I don't >> recall it >> even coming up before but I'm sure others have noticed this behavior. >> >> If you wrap a hideif or a showif around a [search] and it's closing >> [/search], you'll get an error about the nesting of the tags >> hideif/showif >> and /search. Por que? >> >> Example: >> >> [hideif [hidesearch]=T] (and it does) >> [search db=...] >> [founditems] >> [/hideif] >> Something else >> [hideif [hidesearch]=T] >> [/founditems] >> [/search] >> [/hideif] >> >> What am I trying to do? Add a sort for a page without having to >> make two >> pages with different searches on each. So a form post, with the >> search and >> a hidden field of hidesearch=T. The page is the home page, so when >> it is >> first hit I want the search performed automatically and sorted one >> way, user can click a button to sort it the other way, hiding the >> original search and using the one in the form. >> >> What's the preferred method here? >> >> Thanks, >> GK >> >> >> ------------------------------------------------------------- >> 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/ ------------------------------------------------------------- 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/
"Gary Krockover"
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:
MacFinder -- a new WebDNA web site (1998)
Re[2]: Bugs still *not* fixed as promised ... (2000)
showif field is number (1997)
Late on Friday.... brain fried (2002)
WebTen and WebCat (1997)
Not really WebCat (1997)
[LOOKUP] (1997)
database files in secure folder (1997)
Include Not Including (2000)
Calculating multiple shipping... (1997)
WebCat2 beta 11 - new prefs ... (1997)
[WebDNA] TCPDoh (2009)
Help name our technology! (1997)
if/then/else in founditems (2001)
Calculating a total (2000)
WebCat2 - Getting to the browser's username/password data (1997)
Re:Has this happened to you? (1997)
Credit card arrangement (2005)
problems with 2 tags shakur (1997)
Quit revisited (1997)