Re: Displaying raw values (long)

This WebDNA talk-list message is from

1998

It keeps the original formatting. numero = 18464
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.>>While I may not be quite as excited about this issue as Ken is, I have run>across this same problem and I must agree with Ken - it's a pain to work>around this behavior all the time.>>However, it is *sometimes* beneficial to see the raw tag when you are>troubleshooting some function because you'll notice which fields or>variables are not behaving as desired. For me this usually occurs from>typos in the field names or not passing a variable properly. But once you>have things working I'd really really like for this behavior to go away.>>Soooo, what I'd like to see is a development *toggle* on this behavior. Let>us toggle it on through a preference setting while we construct new pages>and let us toggle it off after we have done our troubleshooting. That would>be mui cool!Yes I thought of that too, but I can also conceive of a situation in which some of your code won't work when the toggle is set one way, and then your code WILL work when it's set the other way. It all depends upon how it's written and implemented.There's another simple alternative that would show you where your missing [variable]s are located, and that's to surround all your [variable] tags with unusual characters during development, like this:***[variable]***This will make it easy to identify the specific location of a problem, because instead of seeing nothing in that position you will see ******, and that's a pretty good indicator that your [variable] tag is spelled wrong or otherwise not interpreting whatever value you *thoght* it should be interpreting.In fact, if a *toggle* preference were added as you're suggesting, then setting the toggle could actually add those special characters -- automatically -- to all [variable] tags. Then they would (of course) be removed after development simply by changing the toggle to the other position.Personally I think we need a solution to this problem, because placing innumerable [hideif [tag]=[raw][tag][/raw]][tag][/showif] contexts all over our pages forces WebCat to do a whole lot of extra processing that would NOT be necessary if this issue were dealt with in a more efficient way -- hopefully at the global level with a new preference ... :)Sincerely,Ken Grome808-737-6499WebDNA Solutionsmailto:ken@webdna.nethttp://www.webdna.net Associated Messages, from the most recent to the oldest:

Re: Displaying raw values (long) (Jeremy Pocock 1998)
Re: Displaying raw values (long) (Kenneth Grome 1998)
Re: Displaying raw values (long) (Marty Schmid 1998)
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.>>While I may not be quite as excited about this issue as Ken is, I have run>across this same problem and I must agree with Ken - it's a pain to work>around this behavior all the time.>>However, it is *sometimes* beneficial to see the raw tag when you are>troubleshooting some function because you'll notice which fields or>variables are not behaving as desired. For me this usually occurs from>typos in the field names or not passing a variable properly. But once you>have things working I'd really really like for this behavior to go away.>>Soooo, what I'd like to see is a development *toggle* on this behavior. Let>us toggle it on through a preference setting while we construct new pages>and let us toggle it off after we have done our troubleshooting. That would>be mui cool!Yes I thought of that too, but I can also conceive of a situation in which some of your code won't work when the toggle is set one way, and then your code WILL work when it's set the other way. It all depends upon how it's written and implemented.There's another simple alternative that would show you where your missing [variable]s are located, and that's to surround all your [variable] tags with unusual characters during development, like this:***[variable]***This will make it easy to identify the specific location of a problem, because instead of seeing nothing in that position you will see ******, and that's a pretty good indicator that your [variable] tag is spelled wrong or otherwise not interpreting whatever value you *thoght* it should be interpreting.In fact, if a *toggle* preference were added as you're suggesting, then setting the toggle could actually add those special characters -- automatically -- to all [variable] tags. Then they would (of course) be removed after development simply by changing the toggle to the other position.Personally I think we need a solution to this problem, because placing innumerable [hideif [tag]=[raw][tag][/raw]][tag][/showif] contexts all over our pages forces WebCat to do a whole lot of extra processing that would NOT be necessary if this issue were dealt with in a more efficient way -- hopefully at the global level with a new preference ... :)Sincerely,Ken Grome808-737-6499WebDNA Solutionsmailto:ken@webdna.nethttp://www.webdna.net Kenneth Grome

DOWNLOAD WEBDNA NOW!

Re: Displaying raw values (long)

1998

Top Articles:

Related Readings: