PIXO Support
This WebDNA talk-list message is from 1997
It keeps the original formatting.
numero = 10998
interpreted = N
texte = I was reading the information at http://dev.clearway.com/pixo/ about PIXO support for plugins, and it looks like a very good thing. It also makes me think that some day in the very near future, plugins such as WebCatalog will need a more flexible method of defining which tag brackets to look for and interpret, and which tag brackets to ignore.For example, let's suppose that you want to use WebCatalog with another PIXO-savvy plugin. No problem, right? Well, there *will* be a problem if both WebCatalog and the other plugin are both pre-programmed to recognize only square brackets as their own special tags.In this situation, the first plugin to see the html would try to interpret *all* the square-bracket tags, even though some of those tags were actually meant for the next plugin.Therefore, the first plugin would either ignore the tags it doesn't recognize, or else it would interpret them incorrectly, or else it would generate an error.It sems to me that this problem can only be resolved if PIXO-savvy plugins are given the ability to use different styles of tag brackets ... depending on the specific application and needs of the user.In other words, WebCatalog and other PIXO plugins will need new preference settings that allow us - not the plugin programmers - to define the type of tag brackets these plugins will interpret.I can see no other reasonable solution to this potential problem, can anyone else?Sincerely, Ken Grome ..... ken@iav.com
Associated Messages, from the most recent to the oldest:
I was reading the information at http://dev.clearway.com/pixo/ about PIXO support for plugins, and it looks like a very good thing. It also makes me think that some day in the very near future, plugins such as WebCatalog will need a more flexible method of defining which tag brackets to look for and interpret, and which tag brackets to ignore.For example, let's suppose that you want to use WebCatalog with another PIXO-savvy plugin. No problem, right? Well, there *will* be a problem if both WebCatalog and the other plugin are both pre-programmed to recognize only square brackets as their own special tags.In this situation, the first plugin to see the html would try to interpret *all* the square-bracket tags, even though some of those tags were actually meant for the next plugin.Therefore, the first plugin would either ignore the tags it doesn't recognize, or else it would interpret them incorrectly, or else it would generate an error.It sems to me that this problem can only be resolved if PIXO-savvy plugins are given the ability to use different styles of tag brackets ... depending on the specific application and needs of the user.In other words, WebCatalog and other PIXO plugins will need new preference settings that allow us - not the plugin programmers - to define the type of tag brackets these plugins will interpret.I can see no other reasonable solution to this potential problem, can anyone else?Sincerely, Ken Grome ..... ken@iav.com
Kenneth Grome
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:
GuestBook example (1997)
headers (2000)
Modifying order output (1997)
Relevancy Rating (1998)
Emailer not working (1998)
Lookup Notfound (1998)
Re:E-mailer application times out (1998)
lookup command (1999)
find with exceptions (1997)
MacWEEK article help needed (1996)
Limit to Field Length in DB (1998)
WebCat2b13MacPlugIn - [include] (1997)
Cleaner URLs (2003)
Emailer Question (1998)
Requiring that certain fields be completed (1997)
[countWords]? (1997)
Multiple cart additions (1997)
Re:2nd WebCatalog2 Feature Request (1996)
[WebDNA] Is anybody running a CAPTCHA? (2017)
[WebDNA] testing (2012)