RE: [WebDNA] DHL

This WebDNA talk-list message is from

2008

It keeps the original formatting. numero = 100593
interpreted = N
texte = Hello out there in Webdna land,Is anyone using a DHL live shipping integration with store builder?Thank youRoss MarkbreiterThe World Wide Web StoreA full service Internet company."We bring you the world"http://www.worldwidewebstore.comToll Free: 866-628-6139 California: Ph: 818-707-1234North Carolina: Ph: 919-439-4179-----Original Message-----From: Donovan Brooke [mailto:dbrooke@webdna.us] Sent: Thursday, August 21, 2008 5:18 PMTo: talk@webdna.usSubject: Re: [WebDNA] OT: FCKeditorOlin Lagon wrote:[snip] Also, if you are allowing folks to enter data> then display the data with [interpret][/interpret] they can enter webdnaand> go to town on your server.> > One library I started working with (not done yet) is> http://htmlpurifier.org/. Essentially, I'll have to pass the data to a PHP> script, have it cleaned, then passed back to webdna for final processing.> > Best, OlinHey Olin,One of the things I'd like to see in WebDNA's future isa wide offering of "Function Libraries".I'm sure there are a lot of folks that use the [Function ..]context, but for those that have not used it much, it wasa great addition to WebDNA put in place by SMSI in V5.x.A function could include any "widget" that usefull to havehandy.A "Function Library" could take the form of an [include] filethat is focused into a cohesive set of these tools or widgets.this file could either be included at the top of a page, orit could simply be dropped within your "FunctionDefs" folderwithin your "Globals" directory to provide instant accessto the set of tools for all WebDNA parsed pages.I envision, maybe after initial development and well intothe marketing phase (imagine that! ;-) ),that we will soon see a wide variety of these types of toolsbeing offered.Imagine Olin:OlinsHTMLCleaner.incOlinsCookieTools.incOlinsAPIs.incWSC_ImageMagick.inc ;-)Anyway, the HTMLCleaner to PHP made me want to post this. ;-)I see these community "function libraries" as being not only the"open source" for WebDNA, but perhaps even marketable tools inthe future.WebDNA is powerfull, with access to the shell, and many other corefunctions.. the sky is really the limit here IMO.http://dev.webdna.us/ref/pages.html?context=Function.htmlDonovan-- Donovan D. Brooke PH/FAX: 1 (608) 291-2024----------------------------------------------VPWebDNA Software Corporation16192 Coastal HighwayLewes, DE 19958---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list .To unsubscribe, E-mail to:  Associated Messages, from the most recent to the oldest:

RE: [WebDNA] DHL ("Ross Markbreiter" 2008)

Hello out there in Webdna land,Is anyone using a DHL live shipping integration with store builder?Thank youRoss MarkbreiterThe World Wide Web StoreA full service Internet company."We bring you the world"http://www.worldwidewebstore.comToll Free: 866-628-6139 California: Ph: 818-707-1234North Carolina: Ph: 919-439-4179-----Original Message-----From: Donovan Brooke [mailto:dbrooke@webdna.us] Sent: Thursday, August 21, 2008 5:18 PMTo: talk@webdna.usSubject: Re: [WebDNA] OT: FCKeditorOlin Lagon wrote:[snip] Also, if you are allowing folks to enter data> then display the data with [interpret][/interpret] they can enter webdnaand> go to town on your server.> > One library I started working with (not done yet) is> http://htmlpurifier.org/. Essentially, I'll have to pass the data to a PHP> script, have it cleaned, then passed back to webdna for final processing.> > Best, OlinHey Olin,One of the things I'd like to see in WebDNA's future isa wide offering of "Function Libraries".I'm sure there are a lot of folks that use the [Function ..]context, but for those that have not used it much, it wasa great addition to WebDNA put in place by SMSI in V5.x.A function could include any "widget" that usefull to havehandy.A "Function Library" could take the form of an [include] filethat is focused into a cohesive set of these tools or widgets.this file could either be included at the top of a page, orit could simply be dropped within your "FunctionDefs" folderwithin your "Globals" directory to provide instant accessto the set of tools for all WebDNA parsed pages.I envision, maybe after initial development and well intothe marketing phase (imagine that! ;-) ),that we will soon see a wide variety of these types of toolsbeing offered.Imagine Olin:OlinsHTMLCleaner.incOlinsCookieTools.incOlinsAPIs.incWSC_ImageMagick.inc ;-)Anyway, the HTMLCleaner to PHP made me want to post this. ;-)I see these community "function libraries" as being not only the"open source" for WebDNA, but perhaps even marketable tools inthe future.WebDNA is powerfull, with access to the shell, and many other corefunctions.. the sky is really the limit here IMO.http://dev.webdna.us/ref/pages.html?context=Function.htmlDonovan-- Donovan D. Brooke PH/FAX: 1 (608) 291-2024----------------------------------------------VPWebDNA Software Corporation16192 Coastal HighwayLewes, DE 19958---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list .To unsubscribe, E-mail to:  "Ross Markbreiter"

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:

(no subject) (1997) vcode (2003) problem with NT beta (1997) triggering an update of two frames (1998) Sorting Round 2 plus (1998) Ok here is a question? (1997) Summary search -- speed (1997) Multiple catalog databases and showcart (1997) Need correct syntax for writing to header2 (1999) Help name our technology! (1997) WebDNA-Talk Digests (1997) WC2.0 Memory Requirements (1997) Referrer (2000) Listfiles and nothing found (2001) wierd [cart] action! (1997) WebCat2b13MacPlugIn - [include] (1997) Error Msg (1997) PDF Example (2003) Bug or syntax error on my part? (1997) multi-paragraph fields (1997)