Re: where to put code

This WebDNA talk-list message is from

1998

It keeps the original formatting. numero = 19318
interpreted = N
texte = To answer the question:You ask a general question that cannot be easily answered. WebDNA goes whereever it's needed. Where it's needed can vary quite a bit. A lot of it comes down to style. In general, I try to not place lots of parameters in URL's. I try to keep the total number of pages to a minimum. I also try to write generic WebDNA code that performs different functions based upon different input rather than multiple sections of WebDNA - each performing a specific function.Regarding Ken's response:While I agree with the basic concept of Ken's response (reading the manual and practicing WebDNA will definitely make you a stronger WebCatalog user), the tone of the response does not reflect Pacific Coast Software's feelings, in any way, towards this talk list.The purpose of this talk list is to provide a forum for everyone to discuss WebCatalog and WebDNA, especially beginners. We want to encourage everyone to use this valuable resource. There is no prerequisite for asking questions on the list. We may not be able to answer every message, and the response may be as simple as there's a section in the manual that covers this, but please feel free to use this list to answer any question you have.Lastly, be considerate of everyone on the list. John.>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 John A. Hill, V.P. Marketing Pacific Coast SoftwareeCommerce / Web Developer Tools http://www.smithmicro.com Associated Messages, from the most recent to the oldest:

Re: where to put code (Paul Uttermohlen 1998)
Re: where to put code (Charles Kefauver 1998)
Re: where to put code (Dave MacLeay 1998)
Re: where to put code (Peter Ostry 1998)
Re: where to put code (Charles Kefauver 1998)
Re: where to put code (Kenneth Grome 1998)
Re: where to put code (Kenneth Grome 1998)
Re: where to put code (Kevin Furuta 1998)
Re: where to put code (John Hill 1998)
Re: where to put code (Sue Ann Sanders 1998)
Re: where to put code (Sue Ann Sanders 1998)
Re: where to put code (Peter Ostry 1998)
Re: where to put code (Kenneth Grome 1998)
where to put code (Sue Ann Sanders 1998)

To answer the question:You ask a general question that cannot be easily answered. WebDNA goes whereever it's needed. Where it's needed can vary quite a bit. A lot of it comes down to style. In general, I try to not place lots of parameters in URL's. I try to keep the total number of pages to a minimum. I also try to write generic WebDNA code that performs different functions based upon different input rather than multiple sections of WebDNA - each performing a specific function.Regarding Ken's response:While I agree with the basic concept of Ken's response (reading the manual and practicing WebDNA will definitely make you a stronger WebCatalog user), the tone of the response does not reflect Pacific Coast Software's feelings, in any way, towards this Talk List.The purpose of this Talk List is to provide a forum for everyone to discuss WebCatalog and WebDNA, especially beginners. We want to encourage everyone to use this valuable resource. There is no prerequisite for asking questions on the list. We may not be able to answer every message, and the response may be as simple as there's a section in the manual that covers this, but please feel free to use this list to answer any question you have.Lastly, be considerate of everyone on the list. John.>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 John A. Hill, V.P. Marketing Pacific Coast SoftwareeCommerce / Web Developer Tools http://www.smithmicro.com John Hill

DOWNLOAD WEBDNA NOW!

Re: where to put code

1998

Top Articles:

Related Readings: