Re: Status of variable hierarchy changes?

This WebDNA talk-list message is from

2000


It keeps the original formatting.
numero = 31177
interpreted = N
texte = >>Have you decided whether or not to reinstate the version 3 variable >>hierarchy? Please let us know if and when you do so, it is very >>important to many of us, thanks ... :) > >The default behavior will not be the un-secure style.As long as you give us a *VERY* quick and easy way to fix all our old sites, the default doesn't matter provided we can still use it the 'old-fashioned 3.0 way'.If you let us revert to the old variable hierarchy via a global preference, fine. If you make it easy for us to bbedit entire sites by replacing [text] with [text secure=f] for example, that's fine too.Just don't break our old sites in a way that makes us go thru every template and include file manually to fix what your new default is going to break, because that's an upgrade killer if there ever was one. >Still working >on a way to deal with your true issue, which is to find a nicer way >of filling in default form fields.I'm sorry to read this, because prefilling forms is NOT the true issue! It looks like you got stuck on one of my examples instead of seeing the big picture my example was meant to illustrate ... :(The *real* issue is this: We already have an exceptionally useful variable hierarchy that we know and love in version 3 -- and we do not want to lose it. If you leave the 3.x variable hierarchy intact while adding new (secure) variables to the mix in 4.0, that would result in a genuine enhancement which would benefit all of us.:) ================================ Kenneth Grome, WebDNA Consultant 808-737-6499 http://webdna.net ================================############################################################# 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: Status of variable hierarchy changes? (Nitai @ Eyework 2000)
  2. Re: Status of variable hierarchy changes? (Pat McCormick 2000)
  3. Re: Status of variable hierarchy changes? (Nicolas Verhaeghe 2000)
  4. Re: Status of variable hierarchy changes? (Joseph D'Andrea 2000)
  5. Re: Status of variable hierarchy changes? (Nicolas Verhaeghe 2000)
  6. Re: Status of variable hierarchy changes? (Jesse Proudman 2000)
  7. Re: Status of variable hierarchy changes? (Kenneth Grome 2000)
  8. Re: Status of variable hierarchy changes? (Thomas Wedderburn-Bisshop 2000)
  9. Re: Status of variable hierarchy changes? (Michael Winston 2000)
  10. Re: Status of variable hierarchy changes? (Grant Hulbert 2000)
  11. Status of variable hierarchy changes? (Kenneth Grome 2000)
>>Have you decided whether or not to reinstate the version 3 variable >>hierarchy? Please let us know if and when you do so, it is very >>important to many of us, thanks ... :) > >The default behavior will not be the un-secure style.As long as you give us a *VERY* quick and easy way to fix all our old sites, the default doesn't matter provided we can still use it the 'old-fashioned 3.0 way'.If you let us revert to the old variable hierarchy via a global preference, fine. If you make it easy for us to bbedit entire sites by replacing [text] with [text secure=f] for example, that's fine too.Just don't break our old sites in a way that makes us go thru every template and include file manually to fix what your new default is going to break, because that's an upgrade killer if there ever was one. >Still working >on a way to deal with your true issue, which is to find a nicer way >of filling in default form fields.I'm sorry to read this, because prefilling forms is NOT the true issue! It looks like you got stuck on one of my examples instead of seeing the big picture my example was meant to illustrate ... :(The *real* issue is this: We already have an exceptionally useful variable hierarchy that we know and love in version 3 -- and we do not want to lose it. If you leave the 3.x variable hierarchy intact while adding new (secure) variables to the mix in 4.0, that would result in a genuine enhancement which would benefit all of us.:) ================================ Kenneth Grome, WebDNA Consultant 808-737-6499 http://webdna.net ================================############################################################# 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 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:

RAM variables (1997) OS Accessing FTP from Browser (2000) 2nd WebCatalog2 Feature Request (1996) Change Subtotal (2000) Newbie problem blah blah blah (1997) Bug Report, maybe (1997) WebCat2b13MacPlugIn - [showif][search][/showif] (1997) Installing on IIS 5.1 Windows XP Pro - Username/Password (2006) How do I get WebCatalog to interpret WebDNA tags in.html files? (1997) Country & Ship-to address & other fields ? (1997) Search in 2 or more catalogs (1997) WebDNA Solutions ... sorry! (1997) Replace Statement (1997) weird G3 happenings (1998) RE: [sendmail]- bcc? (1998) transferring values (1998) TRAINING videos - Prove IT. (1998) No luck with taxes (1997) looping table rows (1999) [OT] Test - THE ANSWER _ The winner is .... (2003)