Re: Re[3]: Problem with new formvariables

This WebDNA talk-list message is from

2000


It keeps the original formatting.
numero = 31217
interpreted = N
texte = Running a semi-moderated forum like this one as a company's central customer support forum is a double edged sword. On one hand, it would make a logical argument that since the variable hierarchy is not in the documentation, it should not have been adopted by the customers who are using it. My answer to that is that there are many things not in the documentation, and this list has been used as the official breeding ground of creative solutions, tips, tricks, strategies, and so on. I suggest that when many of the top programmers on this list regularly and repeatedly describe solutions on this list in technical detail without rebuttal from the Smith Micro team that it is tantamount to official documentation. If this list was an independent developers list, that would be another thing. But this list is really the heart of everything Webcatalog. And just for clarification, this hierarchy is not Ken's abomination. I discovered it on my own, as I'm sure many programmers did if they did even the slightest experimentation beyond modification of the tiny store. Ken, I and others have regularly published on this list the details of this hierarchy, which has been an essential logical building block of WebDNA, whether documented or not, without so much of a word of caution from the Smith Micro programmers (at least not that I can remember). Maybe there should be a header at the top of every message that says, Use the technical information you learn on this list at your own risk. Smith Micro denies responsibility for any logical deduction or creative solution that list members may publish.!! [text secure=T]problem=solved[/text] !!This problem can be [problem] very easily with the above solution.Mike> Joe - > > Show me in the docs where there is any discussion of form vs text variables. > This priority of variables feature is something that Ken worked out on his > own > (see Grant e-mail). This is not a _documented_ feature, it is a side effect > of > adding [text] and [math] to WebCat for v.2 -> v.3. > > My suggestion this morning for compatibility () is a > reasonable accomodation for those people who do not want to redo the _logic_ > of > their templates. Some editting will be involved, but if you have to upgrade > the > server you are already there and can do it. It may even be worth SM/PCS's > time > to write a small program for each platform that can be used to turn on the > compatibility mode for existing templates. A single line Perl script or a > find/sed script will do it under any Unix; NT has Perl as well. Only the Mac > needs anything fancy. Hell, I'm sure a clever guy like Ken can come up with a > template that walks the directory tree, loads the pages under [raw] and > rewrites > them with the new flag. > > The more I think about it, the less I like the idea of a system option that > turns off the secure mode of operation. With that in place, no one who > currently uses this feature will stop using it, so the same people will bitch > and moan when WebCat5 comes out! And I dislike having the new tags use a > version specific flag, because it is just asking for trouble for the next > version. > > John Peacock > > ____________________Reply Separator____________________ > Subject: Re[2]: Problem with new formvariables > Author: > Date: 5/2/2000 11:41 AM > > At 9:51 AM 5/2/00, jpeacock@univpress.com wrote: >> \Everyone >> that used this _undocumented_ feature is probably going to have to edit old >> sites to work under the new secure regime. > > This is not an undocumented feature. It is the published behaviour of > variables. > > ___Joe___ ############################################################# 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:

    
  1. Re[3]: Re[3]: Problem with new formvariables (jpeacock@univpress.com 2000)
  2. Re[2]: Re[3]: Problem with new formvariables (jpeacock@univpress.com 2000)
  3. Re[2]: Re[3]: Problem with new formvariables (jpeacock@univpress.com 2000)
  4. Re: Re[2]: Re[3]: Problem with new formvariables (Jesse Proudman 2000)
  5. Re: Re[3]: Problem with new formvariables (Mike Davis 2000)
  6. Re: Re[3]: Problem with new formvariables (Jesse Proudman 2000)
  7. Re: Re[3]: Problem with new formvariables (Nicolas Verhaeghe 2000)
  8. Re: Re[3]: Problem with new formvariables (Jesse Proudman 2000)
  9. Re: Re[3]: Problem with new formvariables (Nicolas Verhaeghe 2000)
  10. Re[3]: Problem with new formvariables (jpeacock@univpress.com 2000)
Running a semi-moderated forum like this one as a company's central customer support forum is a double edged sword. On one hand, it would make a logical argument that since the variable hierarchy is not in the documentation, it should not have been adopted by the customers who are using it. My answer to that is that there are many things not in the documentation, and this list has been used as the official breeding ground of creative solutions, tips, tricks, strategies, and so on. I suggest that when many of the top programmers on this list regularly and repeatedly describe solutions on this list in technical detail without rebuttal from the Smith Micro team that it is tantamount to official documentation. If this list was an independent developers list, that would be another thing. But this list is really the heart of everything Webcatalog. And just for clarification, this hierarchy is not Ken's abomination. I discovered it on my own, as I'm sure many programmers did if they did even the slightest experimentation beyond modification of the tiny store. Ken, I and others have regularly published on this list the details of this hierarchy, which has been an essential logical building block of WebDNA, whether documented or not, without so much of a word of caution from the Smith Micro programmers (at least not that I can remember). Maybe there should be a header at the top of every message that says, Use the technical information you learn on this list at your own risk. Smith Micro denies responsibility for any logical deduction or creative solution that list members may publish.!! [text secure=T]problem=solved[/text] !!This problem can be [problem] very easily with the above solution.Mike> Joe - > > Show me in the docs where there is any discussion of form vs text variables. > This priority of variables feature is something that Ken worked out on his > own > (see Grant e-mail). This is not a _documented_ feature, it is a side effect > of > adding [text] and [math] to WebCat for v.2 -> v.3. > > My suggestion this morning for compatibility () is a > reasonable accomodation for those people who do not want to redo the _logic_ > of > their templates. Some editting will be involved, but if you have to upgrade > the > server you are already there and can do it. It may even be worth SM/PCS's > time > to write a small program for each platform that can be used to turn on the > compatibility mode for existing templates. A single line Perl script or a > find/sed script will do it under any Unix; NT has Perl as well. Only the Mac > needs anything fancy. Hell, I'm sure a clever guy like Ken can come up with a > template that walks the directory tree, loads the pages under [raw] and > rewrites > them with the new flag. > > The more I think about it, the less I like the idea of a system option that > turns off the secure mode of operation. With that in place, no one who > currently uses this feature will stop using it, so the same people will bitch > and moan when WebCat5 comes out! And I dislike having the new tags use a > version specific flag, because it is just asking for trouble for the next > version. > > John Peacock > > ____________________Reply Separator____________________ > Subject: Re[2]: Problem with new formvariables > Author: > Date: 5/2/2000 11:41 AM > > At 9:51 AM 5/2/00, jpeacock@univpress.com wrote: >> \Everyone >> that used this _undocumented_ feature is probably going to have to edit old >> sites to work under the new secure regime. > > This is not an undocumented feature. It is the published behaviour of > variables. > > ___Joe___ ############################################################# 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 Mike Davis

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:

Updating fields from different platforms (1998) WCS Newbie question (1997) Search all Fields in a db (1997) same bill to and ship to? (1998) japanese characters (1997) flushdatabases (2000) Multiple Users.db Possible? (1997) Preventing code execution (2003) Searching for a search solution (2000) Re1000001: Setting up shop (1997) Trigger Validation Text Broken (2003) I'm new be kind (1997) [format 40s]text[/format] doesn't work (1997) Renumbering/changing sort order of lineitems (2004) [if][/if] weirdness (2000) Anyone get WebDNA working on a windows XP Home box? (2006) Summing fields (1997) Maybe off topic but how to charge (1997) WAP and IIS server (2002) View order not right (1997)