Re: New syntax feedback for 4.0
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 29361
interpreted = N
texte = Grant,I think this is the most logical way to go, it allows us to use what we already know with the smallest of changes.>
> >Also, doing a global find/replace on existing code to the new standard, would be a breeze.- Charles >Hey guys, we are entering into the decision phase for our DreamWeaver >syntax for 4.0, and I'd like to open up a small discussion to help me >decide which way to go. This information is confidential, and should >not be discussed outside this list. > >Background: WebDNA's [] syntax tends to make most GUI editors like >DreamWeaver get confused. We decided Mohammed should go to the >mountain in this case, so we are modifying WebCatalog's syntax to >match what GUI editors expect to see. > >So for 4.0, one can optionally write two different kinds of snytax in WebDNA: > >[Loop start=1&end=10] >[index] >[/Loop] > >or > >
> > > >This works well for most contexts, but there are a few exceptions >that can confuse most parsers. Specifically, ShowIf can contain >characters like > which look just like HTML to a parser: > >
3> > ^ looks a lot like followed by a 3 > >...so one solution is to force all contexts to use named/quoted parameters: > >3> > >..but that's really starting to look stupid. I'm not so worried >about the amount of typing involved, because the GUI editor is going >to be doing most of the work anyway, but it still looks pretty weird, >and I think it's hard to follow. > >Another solution would be to change the syntax of ShowIf itself: > > > >...but I don't like this one because it requires a lot more than a >simple global search and replace in a text editor to make this kind >of change to pre-existing old-style WebDNA code. > >There's also a hybrid approach that would allow both a named- and >non-named syntax to be allowed: > >3> or 3> > >The first is more easily readable by people hand-tying the code, and >the second is more easily parsed by GUI editors. I'm leaning toward >that one. > >Thanks for your feedback! > >Grant Hulbert, Director of Engineering ********************************** >Smith Micro, Internet Solutions Div | eCommerce (WebCatalog) >16855 West Bernardo Drive, #380 | ------------------------- >San Diego, CA 92127 | Software & Site Development >Main Line: (858) 675-1106 | http://www.smithmicro.com > Fax: (858) 675-0372 ********************************** > >############################################################# >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 > >To switch to the INDEX mode, E-mail to > >Send administrative queries to ############################################################# 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 To switch to the INDEX mode, E-mail to Send administrative queries to
Associated Messages, from the most recent to the oldest:
Grant,I think this is the most logical way to go, it allows us to use what we already know with the smallest of changes.> > >Also, doing a global find/replace on existing code to the new standard, would be a breeze.- Charles >Hey guys, we are entering into the decision phase for our DreamWeaver >syntax for 4.0, and I'd like to open up a small discussion to help me >decide which way to go. This information is confidential, and should >not be discussed outside this list. > >Background: WebDNA's [] syntax tends to make most GUI editors like >DreamWeaver get confused. We decided Mohammed should go to the >mountain in this case, so we are modifying WebCatalog's syntax to >match what GUI editors expect to see. > >So for 4.0, one can optionally write two different kinds of snytax in WebDNA: > >[Loop start=1&end=10] >[index] >[/Loop] > >or > > > > > >This works well for most contexts, but there are a few exceptions >that can confuse most parsers. Specifically, ShowIf can contain >characters like > which look just like HTML to a parser: > >3> > ^ looks a lot like followed by a 3 > >...so one solution is to force all contexts to use named/quoted parameters: > >3> > >..but that's really starting to look stupid. I'm not so worried >about the amount of typing involved, because the GUI editor is going >to be doing most of the work anyway, but it still looks pretty weird, >and I think it's hard to follow. > >Another solution would be to change the syntax of ShowIf itself: > > > >...but I don't like this one because it requires a lot more than a >simple global search and replace in a text editor to make this kind >of change to pre-existing old-style WebDNA code. > >There's also a hybrid approach that would allow both a named- and >non-named syntax to be allowed: > >3> or 3> > >The first is more easily readable by people hand-tying the code, and >the second is more easily parsed by GUI editors. I'm leaning toward >that one. > >Thanks for your feedback! > >Grant Hulbert, Director of Engineering ********************************** >Smith Micro, Internet Solutions Div | eCommerce (WebCatalog) >16855 West Bernardo Drive, #380 | ------------------------- >San Diego, CA 92127 | Software & Site Development >Main Line: (858) 675-1106 | http://www.smithmicro.com > Fax: (858) 675-0372 ********************************** > >############################################################# >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 > >To switch to the INDEX mode, E-mail to > >Send administrative queries to ############################################################# 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 To switch to the INDEX mode, E-mail to Send administrative queries to
Charles Kline
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:
[WebDNA] Best practice re: password storage (2013)
formulas.db problem solved (1998)
How about this? (1998)
2nd WebCatalog2 Feature Request (1996)
[WebDNA] Authentication across domains (2009)
Country & Ship-to address & other fields ? (1997)
[sendmail] v. [writefile] (2000)
cookie length (1998)
2 things: CartSweep and Manual (2003)
WebCat2 beta 11 - new prefs ... (1997)
Nested tags count question (1997)
PCS Customer submissions ? (1997)
[WebDNA] passing a variable in an include - precedence (2015)
SiteGuard Use Question (1997)
Country & Ship-to address & other fields ? (1997)
[WebDNA] Bug reporting (2009)
[URGENT] Different Results From Math Tag Depending On OS (2006)
[date] for today's date, while inside old order file (1998)
LinkExchange (1997)
Mac v. NT (1998)