Re: Displaying raw values

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 18502
interpreted = N
texte = >>>It seems to be inherently *wrong* to make a tag-interpreting software like >>>WebCatalog display the raw [tag] when there doesn't happen to be any value >>>set for that tag. > >I just had to do the exact same thing. It was for 45 keywords, and I did a >[search db=xxx.db&wofielddata=[showif >[key1]![raw][key1][/raw]][key1][/showif] [showif >[key2]![raw][key2][/raw]][key2][/showif] [showif >etc. 45 times > >And the same chunk for the wa search parameter, and for the Your search of >[keywords] found [numfound]. Sure seemed like unwieldy code. > >How about a context like [hideunusedtags][/hideunusedtags] to wrap around >whole chunks of problematic code like the above? Then we still get the >troubleshooting ability everywhere else.That could work, and the proposal I sent to Grant yesterday should offer the same kind of results too, it just uses a different method, that's all. The ultimate solution selected by PCS will probably be determined by which method is the most practical to create, and by how much flexibility and future expandability each method offers ... :)Sincerely, Ken Grome 808-737-6499 WebDNA Solutions mailto:ken@webdna.net http://www.webdna.net Associated Messages, from the most recent to the oldest:

    
  1. Re: Displaying raw values (Kenneth Grome 1998)
  2. Re: Displaying raw values (Terry Wilson 1998)
  3. Re: Displaying raw values (long) (Jeremy Pocock 1998)
  4. Re: Displaying raw values (long) (Kenneth Grome 1998)
  5. Re: Displaying raw values (long) (Marty Schmid 1998)
  6. Displaying raw values (long) (Kenneth Grome 1998)
>>>It seems to be inherently *wrong* to make a tag-interpreting software like >>>WebCatalog display the raw [tag] when there doesn't happen to be any value >>>set for that tag. > >I just had to do the exact same thing. It was for 45 keywords, and I did a >[search db=xxx.db&wofielddata=[showif >[key1]![raw][key1][/raw]][key1][/showif] [showif >[key2]![raw][key2][/raw]][key2][/showif] [showif >etc. 45 times > >And the same chunk for the wa search parameter, and for the Your search of >[keywords] found [numfound]. Sure seemed like unwieldy code. > >How about a context like [hideunusedtags][/hideunusedtags] to wrap around >whole chunks of problematic code like the above? Then we still get the >troubleshooting ability everywhere else.That could work, and the proposal I sent to Grant yesterday should offer the same kind of results too, it just uses a different method, that's all. The ultimate solution selected by PCS will probably be determined by which method is the most practical to create, and by how much flexibility and future expandability each method offers ... :)Sincerely, Ken Grome 808-737-6499 WebDNA Solutions mailto:ken@webdna.net http://www.webdna.net 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:

Can't use old cart file (was One more try) (1997) decrypt trouble - solved (2006) wierd [cart] action! (1997) Cool new site (1996) CAlendar (2003) A question on sub-categories (1997) Just Testing (1997) Search and path arguments (1998) Secure Server (1997) [WebDNA] Search Problem (2011) Multi-processor Mac info ... (1997) UnitShopCost (2007) Combining Searches (1998) [WebDNA] o search engines index .db files? (2009) Multi-processor Mac info ... (1997) Summing fields (1997) Next X hits (1996) Help! WebCat2 bug (Ben's input) (1997) WebCat2b13MacPlugin - [math][date][/math] problem (1997) Bannersleuth (2000)