RE: [WebDNA] Looking for Govinda
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 106849
interpreted = N
texte = Thank you very much, Govinda. I am studying this stuff very carefully now, using the resources you've referred. http://www.loripalmquist.blogspot.com/ If you visit this blog, you'll see where I'm going with all this. Lori -----Original Message----- From: Govinda [mailto:govinda.webdnatalk@gmail.com] Sent: Saturday, July 02, 2011 8:50 AM To: talk@webdna.us Subject: Re: [WebDNA] Looking for Govinda Hi Lori I don't know about Brian Burton's tutorials.. but he'll likely see your post and maybe reply after awhile (he is an in-frequent contributor here). You could try searching the archives of this talklist for his last post.. get his email address.. and then ask him directly. (?) Anyway, I meant to reply after your last post: If you are totally familiar with HTML lists.. ..and you notice that the list item in question is just any ole list item.. (
...) .. and you still said you did not know what this is for: [plantName] ..then it just means that you did not know what the square bracketed parts are for.. i.e. this: [waterUseClass] and this: [plantName] Well.. the short answer is that those are database (db) field names, and at the time when webdna is parsing the file... those two strings ("[waterUseClass]" and "[plantName]") get replaced with the values of those fields stored in the iterating record of the database that is being searched on. Which database? ... the one referenced in the [search...] context. See, the [search] finds some records.. and the [founditems] context then loops on each of those found records... and as it is looping on each of them, that record's fields' values are available to you! ... by way of simply sticking in the name of the field inside square brackets. If you find great tutorials, then by all means! But if you still want hand holding, then there is nothing shameful about that.. so long as you keep an appreciative tone (even a super terse one).. and guys like me still enjoy helping!.. even really slowly... which I do. So everything is fine whether you find tutorials or not.. My recommendation (short of the tutorial that just happens to perfectly speak to you) is just to focus on the one little thing you are not understanding. Coding is easy if you just keep breaking down problems into smaller and smaller problems. Now, let me ask, do you know what this is for: [plantName] ? If still not.. then I can reply back with something even simpler to break the problem down further.. into even smaller, more digestible parts. -Govinda On 2011-07-01, at 10:13 AM, Lori Palmquist wrote: > Thank you so much for your patience, and the very detailed explanation and > reference links, Govinda. I understand and apply html very well. What I > don't understand so well is how to weave WebDNA into it so they can interact > correctly. > > I will read and study all the references and docs. I feel like I'm in a > different country with this stuff, trying to find my way around without > knowing the language. I feel so fortunate to have someone point me in the > right direction now and then, and even help me with the language. The help > I've gotten from you so far has empowered me tremendously to do much more on > my own than I thought I could do. I love WebDNA, and am excited at the > possibilities it offers me in creating some web applications I've been > wanting to create for quite some time. > > Good luck with your move. > > Lori > > > > > -----Original Message----- > From: Govinda [mailto:govinda.webdnatalk@gmail.com] > Sent: Thursday, June 30, 2011 10:04 PM > To: talk@webdna.us > Subject: Re: [WebDNA] Looking for Govinda > > Hi Lori > > Not sure what happened with the forum (?)..but anyway you'll enjoy it here > because more people hang out here and help and share tips. :-) > Just address everyone when you need help and someone is likely to jump in.. > or at least ask you to clarify so they can understand what you are stuck on. > As for me, I am in and out these days.. mostly out.. so in case it ever > happens that no one else replies.. and I seem to be out.. it just means I > need another half day or whole day+ to reply. (We are packing/moving here > now.) > > First off, I am guessing you need to study more HTML (1) to understand how > some of the plain HTML tags work.. to then know how to use webdna to > generate them 'on the fly' (3) (dynamically). > > Also tell me if you understand (or just note) what is in (2) below. > > (1) - read up on tables if you need to know how they work. Here is a good > place to study them: > http://www.w3schools.com/html/html_tables.asp > > ..and here you will discover what that " class="[waterUseClass]">[plantName]" was for: > HTML lists: > http://www.w3schools.com/html/html_lists.asp > > Basically, if you want a list to be replaced by a table then you need to > swap list items (...) for table rows (| ... |
). > The ...
is the wrapper that defines that we are creating an > (ordered) list. While the is the wrapper that defines > that we are creating a table... but those wrappers do not show any content > directly. It is the tags *inside* the wrappers that have the job of showing > data in itemized fashion. Do play with the "Try-It-Yourself Examples" on > the www.w3schools.com site. ..and notice what a resource that site is for > you! Not just HTML!... but later CSS, javascript.. all kinds of things you > may need sooner or later. > > > (2) - OK, now here is something that you just simply MUST wrap your head > around if you want to really get anywhere with Webdna or any server side web > language: > When a user tries to go to an URL in his/her browser.. clicks a link... > submits a form.. anything.. then their browser requests the page from the > server. The server takes a look at the extension of the page (e.g. ".html", > or ".tpl", ".dna").. and then decides what to do with the page.. whether to > serve it straight to the browser, as is.. or else to first send to another > piece of software, before then sending to the browser. In the case of your > ".tpl" page on your host server.. the server is saying, "hey these are .tpl > pages.. and I am supposed to hand these off to the webdna engine/parser > before finally handing over to the browser.... so that is what happens. > The file goes to webdna where the webdna "parser" evaluates all the webdna > tags.. replaces those tags (like e.g. "[date]") with whatever they are > supposed to do (like e.g. just stick in today's date, "07/01/2011").. and > then once all the webdna tags are evaluated (all the work they do is done, > and all appropriate output is written into the file at the spots where those > tags were), then the server finally hands the resultant text file to the > browser. > > > (3) - The discussion in (2) above can be seen in examples here: > > say we have this code: > ---------------------------------------------------------------- > [loop start=1&end=3&advance=1] > Hi Lori! > [/loop] > > [loop start=1&end=5&advance=1] > - [index]
> [/loop] >
> ---------------------------------------------------------------- > > It produces this in the browser: > > ---------------------------------------------------------------- > Hi Lori! Hi Lori! Hi Lori! > a. 1 > b. 2 > c. 3 > d. 4 > e. 5 > ---------------------------------------------------------------- > > Why? Because webdna gets the raw code and evaluates the webdna tags.. and > then hands whatever is the final output to the browser. If the webdna > parser ("webdna") did not evaluate the webdna tags, then you would get this > in your browser: > ---------------------------------------------------------------- > [loop start=1&end=3&advance=1] > Hi Lori! > [/loop] > > > [loop start=1&end=5&advance=1] > - [index]
> [/loop] >
> ---------------------------------------------------------------- > ...just the same characters as you see in your source file when you are > editing it. (By the way (BTW) what are you using to edit your files? A > text editor?.. which one?) > > But when webdna does evaluate that code.. then it does whatever is inside > the [loop]...[/loop] webdna context as many times as you have told it to > (see here: http://www.webdna.us/page.dna?numero=245) ... and upon each > "iteration" (loop), some webdna tags *inside* the [loop]...[/loop] change > value. Like for example the [index] tag changes its value to the number > corresponding to the number of the iteration that it is on (that it is > currently looping on)... so "[index]" becomes "1" on the > first loop, "2" on the second loop, "3" on the third > loop, and so on. You can inspect the final source code (HTML) that the > browser receives (whatever was left after webdna was done evaluating the > file).. in your browser by selecting the appropriate command in your browser > which allows you to do that. Which browser are you using? I use firefox > for most of my development.. and so the command to see the source HTML *in > the browser* (after webdna is done with it) is: > > View > Page Source > > (or command-U on a mac). > > If you look in whatever browser you are using (if not firefox) then you will > easily find the equivalent command (maybe called 'View Source' or some such > thing). > > When I view the page's source HTML (what webdna output to the browser) for > my sample code above, then I see this: > > ---------------------------------------------------------------- > Hi Lori! > > Hi Lori! > > Hi Lori! > > > > > > - 1
> > - 2
> > - 3
> > - 4
> > - 5
> >
> ---------------------------------------------------------------- > > ...which *rendered* in the regular browser window looks like this: > ---------------------------------------------------------------- > Hi Lori! Hi Lori! Hi Lori! > a. 1 > b. 2 > c. 3 > d. 4 > e. 5 > ---------------------------------------------------------------- > > Do you understand this *perfectly*? > > If not, then, for now, stop all development of your website. > > ... and read the docs here: > www.w3schools.com > > ...and here: > http://www.webdna.us/page.dna?numero=1 > > ..and ask questions here (on this webdna talklist (e-mailing list)) > > ..until you do get the above absolutely perfectly. > What exactly do you not understand in the above discussion? > > > THEN we can better answer your questions (in your previous email, below). > > If I even understand what you have done since we were last chatting on the > forum, then I would say: > sticking: > " > > | waterUse> | > BotanicalName> | > CommonName> | > Exposure> | >
> " > > ..inside a [foundItems] loop is just going to output that exact static text > as many times as the number of records that the [search..] finds. Right? > If you want data from a database to be inserted while looping on a > [foundItems] loop, then you need to use square brackets ("[" and "]") .. > around the database field names whose data you want to output. > > > To "automatically" purge old data from a database, a webdna trigger can be > just what you need. You can read about them here: > http://www.webdna.us/page.dna?numero=290 > Basically a webdna trigger is just a way you can cause some webdna code to > be evaluated on a regular time schedule, that you determine. > > But before tackling that, you probably need to learn how to delete data from > a database in the first place. Have you yet even tried a manual delete? > Like say a user builds a plant list.. and then realizes they added some > plant that they did not want in their list.. why not give them a link > within the table row for that plant in their final list.. which they can > click to delete just that one item (plant) from their list.. and then show > them the resultant (modified) plant list. Try it! > > Also, when you ask for help.. always post the full code for what you are > needing help with. By "full" I do not mean the entirety of the file > (unless asked for that).. but I mean all of the *relevant* code for what you > are working on (what you are trying to do that is not working). ... AND > the resultant static text that is that code's output. See my examples above > to get a feel for that. > > If you are not sure.. then just try and know that there is lots of > forgiveness for anyone sincerely trying. :-) > Just embarrass yourself and be really blunt while saying just where you are > with it. ;-) > There always will be someone above you and someone below.. same for every > one of us here. > > -Govinda > > P.S. A forum (or talklist) "thread" refers to a series of back and forth > messages (by 2 or more users) under one subject line (usually one topic). > That is not a string. A "string", in coders terms, refers to a series of > characters... like your name is the string "L" + "o" + "r" + "i" = "Lori" > There are 4 characters in that string. "3hf85g3jb$G*^\)*" is another > string, 16 characters in length. > > P.P.S. I just looked up and saw the time. LOL. Now my wife is either fast > asleep or also Looking for Govinda. Bless her. > > >> What do you mean "unable to continue a string I had going with Govinda on > the WebDNA Html Forum"? Did the forum stop working for you? I'm the > overworked guy who has to fix it :-) >> >> Thanks, >> -Dan >> >> On 6/30/2011 12:36 PM, Lori Palmquist wrote: >>> I was unable to continue a string I had going with Govinda on the WebDNA > Html Forum, so I'm looking for him here. Following is the message for him: >>> >>> Hi Govinda, >>> >>> I have a couple more questions for you: >>> 1. How can I have the plantlist results show up in the form of a table, > instead of an ordered list? I tried changing the
tags to > tags, then I inserted the following after all the > "switch" and "case" code within [foundItems]: >>> >>> | waterUse> | >>> BotanicalName> | >>> CommonName> | >>> Exposure> | >>>
>>> >>> I wasn't quite sure what to do with the following code, however, so I > left it: >>> [plantName] >>> >>> This strategy didn't work, however. >>> >>> >>> 2. Is there a way to automatically purge old data from the > Usersplantlists database? I don't need to keep this data after the initial > visit where the user creates, then prints the list. >>> >>> Lori >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> --------------------------------------------------------- This message is > sent to you because you are subscribed to the mailing list . To unsubscribe, > E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug > Reporting: support@webdna.us >> --------------------------------------------------------- This message is > sent to you because you are subscribed to the mailing list . To unsubscribe, > E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug > Reporting: support@webdna.us > > - Govinda > -------------- > Old WebDNA talklist archives: > http://dev.webdna.us/TalkListArchive/index.tpl?db=webdna-talk > > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us > > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us - Govinda -------------- Old WebDNA talklist archives: http://dev.webdna.us/TalkListArchive/index.tpl?db=webdna-talk --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us
Associated Messages, from the most recent to the oldest:
Thank you very much, Govinda. I am studying this stuff very carefully now, using the resources you've referred. http://www.loripalmquist.blogspot.com/ If you visit this blog, you'll see where I'm going with all this. Lori -----Original Message----- From: Govinda [mailto:govinda.webdnatalk@gmail.com] Sent: Saturday, July 02, 2011 8:50 AM To: talk@webdna.us Subject: Re: [WebDNA] Looking for Govinda Hi Lori I don't know about Brian Burton's tutorials.. but he'll likely see your post and maybe reply after awhile (he is an in-frequent contributor here). You could try searching the archives of this talklist for his last post.. get his email address.. and then ask him directly. (?) Anyway, I meant to reply after your last post: If you are totally familiar with HTML lists.. ..and you notice that the list item in question is just any ole list item.. (...) .. and you still said you did not know what this is for: [plantName] ..then it just means that you did not know what the square bracketed parts are for.. i.e. this: [waterUseClass] and this: [plantName] Well.. the short answer is that those are database (db) field names, and at the time when webdna is parsing the file... those two strings ("[waterUseClass]" and "[plantName]") get replaced with the values of those fields stored in the iterating record of the database that is being searched on. Which database? ... the one referenced in the [search...] context. See, the [search] finds some records.. and the [founditems] context then loops on each of those found records... and as it is looping on each of them, that record's fields' values are available to you! ... by way of simply sticking in the name of the field inside square brackets. If you find great tutorials, then by all means! But if you still want hand holding, then there is nothing shameful about that.. so long as you keep an appreciative tone (even a super terse one).. and guys like me still enjoy helping!.. even really slowly... which I do. So everything is fine whether you find tutorials or not.. My recommendation (short of the tutorial that just happens to perfectly speak to you) is just to focus on the one little thing you are not understanding. Coding is easy if you just keep breaking down problems into smaller and smaller problems. Now, let me ask, do you know what this is for: [plantName] ? If still not.. then I can reply back with something even simpler to break the problem down further.. into even smaller, more digestible parts. -Govinda On 2011-07-01, at 10:13 AM, Lori Palmquist wrote: > Thank you so much for your patience, and the very detailed explanation and > reference links, Govinda. I understand and apply html very well. What I > don't understand so well is how to weave WebDNA into it so they can interact > correctly. > > I will read and study all the references and docs. I feel like I'm in a > different country with this stuff, trying to find my way around without > knowing the language. I feel so fortunate to have someone point me in the > right direction now and then, and even help me with the language. The help > I've gotten from you so far has empowered me tremendously to do much more on > my own than I thought I could do. I love WebDNA, and am excited at the > possibilities it offers me in creating some web applications I've been > wanting to create for quite some time. > > Good luck with your move. > > Lori > > > > > -----Original Message----- > From: Govinda [mailto:govinda.webdnatalk@gmail.com] > Sent: Thursday, June 30, 2011 10:04 PM > To: talk@webdna.us > Subject: Re: [WebDNA] Looking for Govinda > > Hi Lori > > Not sure what happened with the forum (?)..but anyway you'll enjoy it here > because more people hang out here and help and share tips. :-) > Just address everyone when you need help and someone is likely to jump in.. > or at least ask you to clarify so they can understand what you are stuck on. > As for me, I am in and out these days.. mostly out.. so in case it ever > happens that no one else replies.. and I seem to be out.. it just means I > need another half day or whole day+ to reply. (We are packing/moving here > now.) > > First off, I am guessing you need to study more HTML (1) to understand how > some of the plain HTML tags work.. to then know how to use webdna to > generate them 'on the fly' (3) (dynamically). > > Also tell me if you understand (or just note) what is in (2) below. > > (1) - read up on tables if you need to know how they work. Here is a good > place to study them: > http://www.w3schools.com/html/html_tables.asp > > ..and here you will discover what that " class="[waterUseClass]">[plantName]" was for: > HTML lists: > http://www.w3schools.com/html/html_lists.asp > > Basically, if you want a list to be replaced by a table then you need to > swap list items (...) for table rows (| ... |
). > The ...
is the wrapper that defines that we are creating an > (ordered) list. While the is the wrapper that defines > that we are creating a table... but those wrappers do not show any content > directly. It is the tags *inside* the wrappers that have the job of showing > data in itemized fashion. Do play with the "Try-It-Yourself Examples" on > the www.w3schools.com site. ..and notice what a resource that site is for > you! Not just HTML!... but later CSS, javascript.. all kinds of things you > may need sooner or later. > > > (2) - OK, now here is something that you just simply MUST wrap your head > around if you want to really get anywhere with Webdna or any server side web > language: > When a user tries to go to an URL in his/her browser.. clicks a link... > submits a form.. anything.. then their browser requests the page from the > server. The server takes a look at the extension of the page (e.g. ".html", > or ".tpl", ".dna").. and then decides what to do with the page.. whether to > serve it straight to the browser, as is.. or else to first send to another > piece of software, before then sending to the browser. In the case of your > ".tpl" page on your host server.. the server is saying, "hey these are .tpl > pages.. and I am supposed to hand these off to the webdna engine/parser > before finally handing over to the browser.... so that is what happens. > The file goes to webdna where the webdna "parser" evaluates all the webdna > tags.. replaces those tags (like e.g. "[date]") with whatever they are > supposed to do (like e.g. just stick in today's date, "07/01/2011").. and > then once all the webdna tags are evaluated (all the work they do is done, > and all appropriate output is written into the file at the spots where those > tags were), then the server finally hands the resultant text file to the > browser. > > > (3) - The discussion in (2) above can be seen in examples here: > > say we have this code: > ---------------------------------------------------------------- > [loop start=1&end=3&advance=1] > Hi Lori! > [/loop] > > [loop start=1&end=5&advance=1] > - [index]
> [/loop] >
> ---------------------------------------------------------------- > > It produces this in the browser: > > ---------------------------------------------------------------- > Hi Lori! Hi Lori! Hi Lori! > a. 1 > b. 2 > c. 3 > d. 4 > e. 5 > ---------------------------------------------------------------- > > Why? Because webdna gets the raw code and evaluates the webdna tags.. and > then hands whatever is the final output to the browser. If the webdna > parser ("webdna") did not evaluate the webdna tags, then you would get this > in your browser: > ---------------------------------------------------------------- > [loop start=1&end=3&advance=1] > Hi Lori! > [/loop] > > > [loop start=1&end=5&advance=1] > - [index]
> [/loop] >
> ---------------------------------------------------------------- > ...just the same characters as you see in your source file when you are > editing it. (By the way (BTW) what are you using to edit your files? A > text editor?.. which one?) > > But when webdna does evaluate that code.. then it does whatever is inside > the [loop]...[/loop] webdna context as many times as you have told it to > (see here: http://www.webdna.us/page.dna?numero=245) ... and upon each > "iteration" (loop), some webdna tags *inside* the [loop]...[/loop] change > value. Like for example the [index] tag changes its value to the number > corresponding to the number of the iteration that it is on (that it is > currently looping on)... so "[index]" becomes "1" on the > first loop, "2" on the second loop, "3" on the third > loop, and so on. You can inspect the final source code (HTML) that the > browser receives (whatever was left after webdna was done evaluating the > file).. in your browser by selecting the appropriate command in your browser > which allows you to do that. Which browser are you using? I use firefox > for most of my development.. and so the command to see the source HTML *in > the browser* (after webdna is done with it) is: > > View > Page Source > > (or command-U on a mac). > > If you look in whatever browser you are using (if not firefox) then you will > easily find the equivalent command (maybe called 'View Source' or some such > thing). > > When I view the page's source HTML (what webdna output to the browser) for > my sample code above, then I see this: > > ---------------------------------------------------------------- > Hi Lori! > > Hi Lori! > > Hi Lori! > > > > > > - 1
> > - 2
> > - 3
> > - 4
> > - 5
> >
> ---------------------------------------------------------------- > > ...which *rendered* in the regular browser window looks like this: > ---------------------------------------------------------------- > Hi Lori! Hi Lori! Hi Lori! > a. 1 > b. 2 > c. 3 > d. 4 > e. 5 > ---------------------------------------------------------------- > > Do you understand this *perfectly*? > > If not, then, for now, stop all development of your website. > > ... and read the docs here: > www.w3schools.com > > ...and here: > http://www.webdna.us/page.dna?numero=1 > > ..and ask questions here (on this webdna talklist (e-mailing list)) > > ..until you do get the above absolutely perfectly. > What exactly do you not understand in the above discussion? > > > THEN we can better answer your questions (in your previous email, below). > > If I even understand what you have done since we were last chatting on the > forum, then I would say: > sticking: > " > > | waterUse> | > BotanicalName> | > CommonName> | > Exposure> | >
> " > > ..inside a [founditems] loop is just going to output that exact static text > as many times as the number of records that the [search..] finds. Right? > If you want data from a database to be inserted while looping on a > [founditems] loop, then you need to use square brackets ("[" and "]") .. > around the database field names whose data you want to output. > > > To "automatically" purge old data from a database, a webdna trigger can be > just what you need. You can read about them here: > http://www.webdna.us/page.dna?numero=290 > Basically a webdna trigger is just a way you can cause some webdna code to > be evaluated on a regular time schedule, that you determine. > > But before tackling that, you probably need to learn how to delete data from > a database in the first place. Have you yet even tried a manual delete? > Like say a user builds a plant list.. and then realizes they added some > plant that they did not want in their list.. why not give them a link > within the table row for that plant in their final list.. which they can > click to delete just that one item (plant) from their list.. and then show > them the resultant (modified) plant list. Try it! > > Also, when you ask for help.. always post the full code for what you are > needing help with. By "full" I do not mean the entirety of the file > (unless asked for that).. but I mean all of the *relevant* code for what you > are working on (what you are trying to do that is not working). ... AND > the resultant static text that is that code's output. See my examples above > to get a feel for that. > > If you are not sure.. then just try and know that there is lots of > forgiveness for anyone sincerely trying. :-) > Just embarrass yourself and be really blunt while saying just where you are > with it. ;-) > There always will be someone above you and someone below.. same for every > one of us here. > > -Govinda > > P.S. A forum (or talklist) "thread" refers to a series of back and forth > messages (by 2 or more users) under one subject line (usually one topic). > That is not a string. A "string", in coders terms, refers to a series of > characters... like your name is the string "L" + "o" + "r" + "i" = "Lori" > There are 4 characters in that string. "3hf85g3jb$G*^\)*" is another > string, 16 characters in length. > > P.P.S. I just looked up and saw the time. LOL. Now my wife is either fast > asleep or also Looking for Govinda. Bless her. > > >> What do you mean "unable to continue a string I had going with Govinda on > the WebDNA Html Forum"? Did the forum stop working for you? I'm the > overworked guy who has to fix it :-) >> >> Thanks, >> -Dan >> >> On 6/30/2011 12:36 PM, Lori Palmquist wrote: >>> I was unable to continue a string I had going with Govinda on the WebDNA > Html Forum, so I'm looking for him here. Following is the message for him: >>> >>> Hi Govinda, >>> >>> I have a couple more questions for you: >>> 1. How can I have the plantlist results show up in the form of a table, > instead of an ordered list? I tried changing the
tags to > tags, then I inserted the following after all the > "switch" and "case" code within [founditems]: >>> >>> | waterUse> | >>> BotanicalName> | >>> CommonName> | >>> Exposure> | >>>
>>> >>> I wasn't quite sure what to do with the following code, however, so I > left it: >>> [plantName] >>> >>> This strategy didn't work, however. >>> >>> >>> 2. Is there a way to automatically purge old data from the > Usersplantlists database? I don't need to keep this data after the initial > visit where the user creates, then prints the list. >>> >>> Lori >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> --------------------------------------------------------- This message is > sent to you because you are subscribed to the mailing list . To unsubscribe, > E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug > Reporting: support@webdna.us >> --------------------------------------------------------- This message is > sent to you because you are subscribed to the mailing list . To unsubscribe, > E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug > Reporting: support@webdna.us > > - Govinda > -------------- > Old WebDNA talklist archives: > http://dev.webdna.us/TalkListArchive/index.tpl?db=webdna-talk > > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us > > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us - Govinda -------------- Old WebDNA talklist archives: http://dev.webdna.us/TalkListArchive/index.tpl?db=webdna-talk --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us
"Lori Palmquist"
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:
More DateMath problems (1997)
Re:listfiles-looking for slick solution (1997)
Lost and Recovered. (1998)
WebTen? (1997)
[authenticate] (1999)
Re:affiliate marketing program (1998)
Separate SSL Server (1997)
Emailer port change (1997)
oops private message leaked into talk list (1997)
GuestBook example (1997)
[addlineitems] (1997)
Show shoppingcart after remove last item (1997)
Bug? (1997)
[OT] - CommuniGate skins (2003)
Sorting Numbers (1997)
Quit revisited (1997)
category index, drop down list (2005)
WebCat2b13MacPlugIn - [showif][search][/showif] (1997)
Failing Email (2004)
WebCatalog 4 Install Problems - Not Answered ?? (2000)