Re: Optional new-style syntax for WebCatalog 4.0

This WebDNA talk-list message is from

2000

It keeps the original formatting. numero = 31080
interpreted = N
texte = On 30/4/2000 3:34, Grant Hulbert said:>To give everyone a head-start on playing with the new-style syntax, >here's a primer. We are calling it XML syntax only because it's not >HTML, and it tends to follow the guidelines of XML, and it looks a >lot like XML. It's basically just the type of syntax that most >graphical editors like DreamWeaver tend to expect, and *not* chew up >like the original [classic] syntax. I still prefer classic syntax, >because I think it's easier to pick pick out of a bunch of HTML, and >it's a bit tighter.>.........Grant,thanks for the very useful reply. Here is some feedback from using Adobe Golive to edit the TearoomXML examples: - I love it! It is so cool to be able to see all the code neatly put into little blue tags, and get at the parameters by clicking on the tag. - it's straightforward to add these new tags to the Golive HTML database. Once the plug-in arrives (and I work out how to export the Golive database) I'll be happy to provide the tags in Golive format. - The format tag seems to break your rule of named and quoted parameters. - I notice you replace fields such as [price] with . Is that the rule that all variables have a dna_ inserted in front of them in the XML format? - popup menus with auto-select still get badly broken by Golive: =UPS>selected> becomes =UPS>selected>UPS Ground when the page is edited. Looks like we still need for popups. - The following image tag gets broken because of the nested double quotes: >/WebCatalog/Art/TeaRoomImages/> .. but works fine when you change it to and if I had typed the DNA_showif stuff into the src field myself, it would have automatically generated single quotes, so that's not a problem. Just thought you might like to change your sample code so die-hard WYSIWIG editors like myself don't get frightened.Thomas Wedderburn-BisshopCIO, Woomera Net Solutions www.woomeranet.com.auSydney, Australia Phone +61 2 9633 5048 fax +61 2 9633 5248#############################################################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:

Re: Optional new-style syntax for WebCatalog 4.0 (Thomas Wedderburn-Bisshop 2000) Optional new-style syntax for WebCatalog 4.0 (Grant Hulbert 2000)

On 30/4/2000 3:34, Grant Hulbert said:>To give everyone a head-start on playing with the new-style syntax, >here's a primer. We are calling it XML syntax only because it's not >HTML, and it tends to follow the guidelines of XML, and it looks a >lot like XML. It's basically just the type of syntax that most >graphical editors like DreamWeaver tend to expect, and *not* chew up >like the original [classic] syntax. I still prefer classic syntax, >because I think it's easier to pick pick out of a bunch of HTML, and >it's a bit tighter.>.........Grant,thanks for the very useful reply. Here is some feedback from using Adobe Golive to edit the TearoomXML examples: - I love it! It is so cool to be able to see all the code neatly put into little blue tags, and get at the parameters by clicking on the tag. - it's straightforward to add these new tags to the Golive HTML database. Once the plug-in arrives (and I work out how to export the Golive database) I'll be happy to provide the tags in Golive format. - The format tag seems to break your rule of named and quoted parameters. - I notice you replace fields such as [price] with . Is that the rule that all variables have a dna_ inserted in front of them in the XML format? - popup menus with auto-select still get badly broken by Golive: =UPS>selected> becomes =UPS>selected>UPS Ground when the page is edited. Looks like we still need for popups. - The following image tag gets broken because of the nested double quotes: >/WebCatalog/Art/TeaRoomImages/> .. but works fine when you change it to and if I had typed the DNA_showif stuff into the src field myself, it would have automatically generated single quotes, so that's not a problem. Just thought you might like to change your sample code so die-hard WYSIWIG editors like myself don't get frightened.Thomas Wedderburn-BisshopCIO, Woomera Net Solutions www.woomeranet.com.auSydney, Australia Phone +61 2 9633 5048 fax +61 2 9633 5248#############################################################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 Thomas Wedderburn-Bisshop

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:

Multiple results (2001) WebCat2.0 acgi vs plugin (1997) Problems passing [SKU] with $Replace in 2.0 (1997) Can't Update records (1997) PCS Frames (1997) WebCat2.0 [format thousands .0f] no go (1997) Quit revisited (1997) Weird bug, or is there something amiss? (1997) FEA REQ: One .hdr, multiple .db's (2003) WebTen? (1997) WebCat2b13MacPlugin - [math][date][/math] problem (1997) updating checkbox in a db (1998) Context and commands (1998) WebDNA FAQ or FAQs -- was "weird problem" (2004) WebCatalog 2.0 b 15 mac (1997) Change to 5.0 per website licensing (2003) Webcat no longer supported? (2006) [WebDNA] Getting to know ARRAY (2014) [WebDNA] reCAPTCHA and WebDNA (2010) [foundItems] context problem (2000)