Re: where to put code

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 19314
interpreted = N
texte = Actually, I've done a ton of reading, but 95% of it has been the online Command Reference. I've done a little reading in the TechRef document (much of this appears to be the same as the online Command Ref docs though). I'll look over Chapters 4 and 5 again, this should help.I've done plenty of HTML stuff with BBEdit for years - before visual tools were available. And usually things make logical sense. And I think WC will eventually make sense. But it's harder when it seems inconsistent.Sue Ann >If you haven't already done so, I think the best thing for you to do is to >read the WebCatalogManual.pdf file -- at least two or three times. This is >not a joke, I am absolutely serious. This is the only reference to the >WebDNA language that actually gives you the solid understanding you need >of the FRAMEWORK and STRUCTURE of the language and how it works. > >Even though the manual should be required reading by all new WebDNA >programmers, many people just don't bother. They skip this valuable >reference manual and jump right into their projects, then they feel lost >and/or confused, forever asking questions that point to their basic >misunderstanding of the foundation of the WebDNA language. In other words, >they never really get it ... so to speak. > >Unless you've been a database programmer for a few years, and unless you >also have some direct HTML programming experience (and not with a page >layout program, but with actual manual HTML coding in a text processor) >and a solid understanding of the http protocol, the background provided by >the WebCatalogManual.pdf reference manual is very important in helping you >to become a swift and effective as a WebDNA programer. > >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: where to put code (Paul Uttermohlen 1998)
  2. Re: where to put code (Charles Kefauver 1998)
  3. Re: where to put code (Dave MacLeay 1998)
  4. Re: where to put code (Peter Ostry 1998)
  5. Re: where to put code (Charles Kefauver 1998)
  6. Re: where to put code (Kenneth Grome 1998)
  7. Re: where to put code (Kenneth Grome 1998)
  8. Re: where to put code (Kevin Furuta 1998)
  9. Re: where to put code (John Hill 1998)
  10. Re: where to put code (Sue Ann Sanders 1998)
  11. Re: where to put code (Sue Ann Sanders 1998)
  12. Re: where to put code (Peter Ostry 1998)
  13. Re: where to put code (Kenneth Grome 1998)
  14. where to put code (Sue Ann Sanders 1998)
Actually, I've done a ton of reading, but 95% of it has been the online Command Reference. I've done a little reading in the TechRef document (much of this appears to be the same as the online Command Ref docs though). I'll look over Chapters 4 and 5 again, this should help.I've done plenty of HTML stuff with BBEdit for years - before visual tools were available. And usually things make logical sense. And I think WC will eventually make sense. But it's harder when it seems inconsistent.Sue Ann >If you haven't already done so, I think the best thing for you to do is to >read the WebCatalogManual.pdf file -- at least two or three times. This is >not a joke, I am absolutely serious. This is the only reference to the >WebDNA language that actually gives you the solid understanding you need >of the FRAMEWORK and STRUCTURE of the language and how it works. > >Even though the manual should be required reading by all new WebDNA >programmers, many people just don't bother. They skip this valuable >reference manual and jump right into their projects, then they feel lost >and/or confused, forever asking questions that point to their basic >misunderstanding of the foundation of the WebDNA language. In other words, >they never really get it ... so to speak. > >Unless you've been a database programmer for a few years, and unless you >also have some direct HTML programming experience (and not with a page >layout program, but with actual manual HTML coding in a text processor) >and a solid understanding of the http protocol, the background provided by >the WebCatalogManual.pdf reference manual is very important in helping you >to become a swift and effective as a WebDNA programer. > >Sincerely, >Ken Grome >808-737-6499 >WebDNA Solutions >mailto:ken@webdna.net >http://www.webdna.net > > > Sue Ann Sanders

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:

upgrading (1997) WEBCAT with SQL backend. Help please! (2000) This list needs a digest: rant, rave... (1997) [WebDNA] Privat IP website behind a public IP website (2014) OT: Digger (2007) minimalist shopping cart. (1997) PCS Frames (1997) Problems with ^ could be solved with [REPLACE CHARACTERS] (1997) WebCat2 beta 11 - new prefs ... (1997) [random] only for 1-100??? (1997) Emailer choke (1997) Pass a form (2003) [WriteFile] problems (1997) Random Images (2000) problems with WebCat-Plugin (1997) A little help on e-mail (HELP!!! :-) ) (1998) Separate server for jpg/gif files (1998) Re(9): Small Bug: ErrorLog.txt/[FORMVARIABLES]/[ORDERFILE] (1998) Other then credit cards-how? (1997) Install Webcatalog under NT4.0 and Microsoft IIS 2.0 (1997)