Re: Automatic [URL]ing by the webdna engine

This WebDNA talk-list message is from

2003


It keeps the original formatting.
numero = 53749
interpreted = N
texte = >If WebDNA automatically inserted [url]s around my [tSearch] variable, it would destroy my search. >- brian Hypothetically, if it were able to be done without effecting the speed and performance of the engine, then I would run 2 global find & replaces in Homesite (or BBEdit or whatever) and replace all instances of "[url]" and "[/url]" with then turn the guinea pig code loose on the new "smart-url-feature"- enabled Dev version of webDNA 8.0 and see what happens. In theory everything would still work as nothing is [url]'ed by me anymore in the raw code, and so "all variables would be created equal". Then, assuming it actually worked like I think it would, I could toggle the "smart-url" on/off in the prefs and if on, then I could assume that I never had to type [url] or [/url] moving forward, because I could assume that webDNA was looking out for me, so to speak. I assume it could even be a pref at the global/sandbox/domain/ level to help easy any website-portability issues. Or, I could just get in the habit of [url]'ing my stuff from now on, like I am supposed to :) -Dan ------------------------------------------------------------ http://www.StrongGraphicDesign.com (208) 319-0137 | Toll-free p/f 877-561-1656 ------------------------------------------------------------ On Thu, 30 Oct 2003 17:40:00 -0800 Brian Fries wrote: >NO NO NO!!!! > >This would slow down the WebDNA parser by adding another complex code parsing pass, and it would >break hundreds if not thousands of pages I have written! > >See my reply on the original "Re: [URL] and [showif] or [hideif] comparisons" subject for my full >treatise, but take this simple example of something I do frequently: > >[if ("[exact]"="T")][then] >[text]tSearch=eqSKUdata=[url][var1][/url][/text] >[/then][else] >[text]tSearch=bwSKUdata=[url][var1][/url][/text] >[/else][/if] > >[search db=product.db&[tSearch]]... > >If WebDNA automatically inserted [url]s around my [tSearch] variable, it would destroy my search. > >- brian > > >On Thursday, October 30, 2003, at 05:06 PM, Kenneth Grome wrote: > >>>Yes. So would it slow everything down enormously if the showif and >>>hideif >>>did it automatically? >> >>URL is not done automatically anywhere. If this feature were >>implemented, the webdna engine would have to be rewritten so that it >>would dynamically insert these tags into our code before that code is >>processed. I assume that something like this would have to be >>implemented::: >> >>1- read the original webdna code into RAM >>2- scan that code to identify the proper locations for dynamic url tag >>insertion >>3- insert [url] and [/url] tags into the properly identified locations >>4- interpret the resulting code and return the results >> >>If the engine were rewritten to perform this task for showifs and >>hideif's, it should *also* be made to similarly url the values in >>every append, replace and delete context -- as well as url everything >>else that should be urled in order to make webdna work properly. >> >>Rewriting the webdna engine like this would probably be a difficult >>task ... but if it were done, it would make our work as webdna >>programmers *much* faster and easier! >> >>It seems to me that an improvement like this would be appreciated by >>EVERYONE (instead of just a handful of webdna programmers with >>specific needs) assuming that SMSI make it work properly of course. >>And I think that if it were implemented, we should also be given a new >>pref that will let us turn it on and/or off ourselves. >> >>What do you guys thing? Is this a feature that SMSI should consider >>placing at (or near) the top of their list of improvements for the >>next release? >>-- >> >>Sincerely, >>Kenneth Grome >>------------------------------------------------------------- >>Outsource your WebDNA programming for $18 an hour or less! >>------------------------------------------------------------- >> >-- Brian Fries, BrainScan Software -- http://www.brainscansoftware.com > -- > > >------------------------------------------------------------- >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 >Web Archive of this list is at: http://webdna.smithmicro.com/ ------------------------------------------------------------- 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 Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: Automatic [URL]ing by the webdna engine ( Alain Russell 2003)
  2. Re: Automatic [URL]ing by the webdna engine ( "Dan Strong" 2003)
  3. Re: Automatic [URL]ing by the webdna engine ( Donovan Brooke 2003)
  4. Re: Automatic [URL]ing by the webdna engine ( Brian Fries 2003)
  5. Automatic [URL]ing by the webdna engine ( Kenneth Grome 2003)
>If WebDNA automatically inserted [url]s around my [tSearch] variable, it would destroy my search. >- brian Hypothetically, if it were able to be done without effecting the speed and performance of the engine, then I would run 2 global find & replaces in Homesite (or BBEdit or whatever) and replace all instances of "[url]" and "[/url]" with then turn the guinea pig code loose on the new "smart-url-feature"- enabled Dev version of webDNA 8.0 and see what happens. In theory everything would still work as nothing is [url]'ed by me anymore in the raw code, and so "all variables would be created equal". Then, assuming it actually worked like I think it would, I could toggle the "smart-url" on/off in the prefs and if on, then I could assume that I never had to type [url] or [/url] moving forward, because I could assume that webDNA was looking out for me, so to speak. I assume it could even be a pref at the global/sandbox/domain/ level to help easy any website-portability issues. Or, I could just get in the habit of [url]'ing my stuff from now on, like I am supposed to :) -Dan ------------------------------------------------------------ http://www.StrongGraphicDesign.com (208) 319-0137 | Toll-free p/f 877-561-1656 ------------------------------------------------------------ On Thu, 30 Oct 2003 17:40:00 -0800 Brian Fries wrote: >NO NO NO!!!! > >This would slow down the WebDNA parser by adding another complex code parsing pass, and it would >break hundreds if not thousands of pages I have written! > >See my reply on the original "Re: [url] and [showif] or [hideif] comparisons" subject for my full >treatise, but take this simple example of something I do frequently: > >[if ("[exact]"="T")][then] >[text]tSearch=eqSKUdata=[url][var1][/url][/text] >[/then][else] >[text]tSearch=bwSKUdata=[url][var1][/url][/text] >[/else][/if] > >[search db=product.db&[tSearch]]... > >If WebDNA automatically inserted [url]s around my [tSearch] variable, it would destroy my search. > >- brian > > >On Thursday, October 30, 2003, at 05:06 PM, Kenneth Grome wrote: > >>>Yes. So would it slow everything down enormously if the showif and >>>hideif >>>did it automatically? >> >>URL is not done automatically anywhere. If this feature were >>implemented, the webdna engine would have to be rewritten so that it >>would dynamically insert these tags into our code before that code is >>processed. I assume that something like this would have to be >>implemented::: >> >>1- read the original webdna code into RAM >>2- scan that code to identify the proper locations for dynamic url tag >>insertion >>3- insert [url] and [/url] tags into the properly identified locations >>4- interpret the resulting code and return the results >> >>If the engine were rewritten to perform this task for showifs and >>hideif's, it should *also* be made to similarly url the values in >>every append, replace and delete context -- as well as url everything >>else that should be urled in order to make webdna work properly. >> >>Rewriting the webdna engine like this would probably be a difficult >>task ... but if it were done, it would make our work as webdna >>programmers *much* faster and easier! >> >>It seems to me that an improvement like this would be appreciated by >>EVERYONE (instead of just a handful of webdna programmers with >>specific needs) assuming that SMSI make it work properly of course. >>And I think that if it were implemented, we should also be given a new >>pref that will let us turn it on and/or off ourselves. >> >>What do you guys thing? Is this a feature that SMSI should consider >>placing at (or near) the top of their list of improvements for the >>next release? >>-- >> >>Sincerely, >>Kenneth Grome >>------------------------------------------------------------- >>Outsource your WebDNA programming for $18 an hour or less! >>------------------------------------------------------------- >> >-- Brian Fries, BrainScan Software -- http://www.brainscansoftware.com > -- > > >------------------------------------------------------------- >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 >Web Archive of this list is at: http://webdna.smithmicro.com/ ------------------------------------------------------------- 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 Web Archive of this list is at: http://webdna.smithmicro.com/ "Dan Strong"

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:

LetterRip and WebCat & more (1998) SHOWIF [var_with_backslash]^[value] (2002) Revisit: speed test (2002) old cart file deletion (2000) WebCatalog NT beta 18 problem (1997) WebDNA-Talk Digest mode broken (1997) [SearchString] problem with [search] context (1997) Up and running ... at last !! (1997) ASP and WebDNA (1998) [WebDNA] Error 500 with SUMM=T (2017) WebCat2 - Getting to the browser's username/password data (1997) RE: Adding headers to email (1997) Problems with emailer cutting off carriage returns (Crossplatform issue?) (1999) Moment of Thanks (1997) Sku numbers (1997) Web Catalog Instability (2000) Digest Format (2003) If search results are blank... (2003) [WebDNA] Sorry WebDNA server not running (2014) FAX orders (1996)