Re: javascript newPopwin and webcat

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 21428
interpreted = N
texte = > But before I quote the job I need to know if any user on this list has >experinced any problems, pitfalls, gotchas that they know of when mixing >javascript and webdna.Just remember that WebDNA tweaks all the text that it thinks looks like WebDNA *first*, then the JavaScript is executed in the visitor's browser. That means you can use WebDNA to 'write' javascript, but you cannot use javascript to 'write' WebDNA, analogous to using WebDNA to 'write' SQL statements.Be careful that you do not use index variables in JavaScript that happen to match WebDNA variable names. Things like array[lineindex], where lineindex is a *javascript* variable, would not give expected results if you happen to be inside a [LineItems] loop.But for the most part, you can just let them work together, because we designed it to allow this situation. For instance, since WebDNA does *not* collapse unknown variables to nothing (despite numerous vocal requests for this 'feature' months ago), you can drop in javascript arrays like array[i] and WebDNA will not mess with that [i] by collapsing it to nothing.Technical Support | ==== eCommerce and Beyond ==== Pacific Coast Software | WebCatalog, WebMerchant, 11770 Bernardo Plaza Court | SiteEdit Pro, PhotoMaster, San Diego, CA 92128 | Typhoon 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: javascript newPopwin and webcat (bobm 1998)
  2. Re: javascript newPopwin and webcat (PCS Technical Support 1998)
  3. javascript newPopwin and webcat (Gary Richter 1998)
> But before I quote the job I need to know if any user on this list has >experinced any problems, pitfalls, gotchas that they know of when mixing >javascript and webdna.Just remember that WebDNA tweaks all the text that it thinks looks like WebDNA *first*, then the JavaScript is executed in the visitor's browser. That means you can use WebDNA to 'write' javascript, but you cannot use javascript to 'write' WebDNA, analogous to using WebDNA to 'write' SQL statements.Be careful that you do not use index variables in JavaScript that happen to match WebDNA variable names. Things like array[lineindex], where lineindex is a *javascript* variable, would not give expected results if you happen to be inside a [lineitems] loop.But for the most part, you can just let them work together, because we designed it to allow this situation. For instance, since WebDNA does *not* collapse unknown variables to nothing (despite numerous vocal requests for this 'feature' months ago), you can drop in javascript arrays like array[i] and WebDNA will not mess with that [i] by collapsing it to nothing.Technical Support | ==== eCommerce and Beyond ==== Pacific Coast Software | WebCatalog, WebMerchant, 11770 Bernardo Plaza Court | SiteEdit Pro, PhotoMaster, San Diego, CA 92128 | Typhoon 619/675-1106 Fax: 619/675-0372 | http://www.smithmicro.com/ PCS Technical Support

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:

label?! (2005) Un[url]ize (1999) Questions To Answer (1997) [showif] / [hideif] (1997) Not really WebCat (1997) [WebDNA] Clean URLS job - will pay (2010) textarea input- nevermind (2002) WCS Newbie question (1997) Site Specific Shopping Cart folder and Orderfiles (2000) BBEdit and WebCatalog 2.0? (1997) Quit revisited (1997) An easy one (1999) How to archive....? (1998) Development terminated. (1998) A multi-processor savvy WebCatalog? (1997) SKU (1997) using showpage and showcart commands (1996) WebCatalog for Postcards ? (1997) WebCat2 Append problem (B14Macacgi) (1997) transferring values (1998)