[WebDNA] Enhancements to "list" contexts ...
This WebDNA talk-list message is from 2015
It keeps the original formatting.
numero = 111813
interpreted = N
texte = Hi Chris, You asked for our suggestions to improve WebDNA. Here are a few of my thoughts (with more to come in later posts): - Since [formvariables] and [listfiles] both offer the optional parameters "name=xxx&exact=T/F" as a way to limit what they find, it would be nice to have the same optional parameters in a few of our other "list" contexts too, such as: listmimeheaders listvariables listdatabases listfields listcookies - For all contexts that offer the "name=xxx&exact=T/F" options, a new "opposite=T" parameter would be useful when we want to return the opposite results. - Sorting options would be useful in these list contexts, too. We already use these sort options in our searches, so adding them to our list contexts would keep the syntax consistent: asnamesort=1/2/3/etc. denamesort=1/2/3/etc. assizesort=1/2/3/etc. desizesort=1/2/3/etc. asmoddatesort=1/2/3/etc. demoddatesort=1/2/3/etc. BY THE WAY, TO GET REALLY SERIOUS ABOUT THIS KIND OF ENHANCEMENT: Just add an optional "search=T" parameter to all our list contexts. This would tell WebDNA to recognize the same parameters we already use in our regular database/table searches. This would allow us to do things like this: [listfiles path=/to/server/logs/&search=T&bwnamedatarq=error.log&gemoddatedatarq=12/21/2014&moddatetype=date&gesizedatarq=1200000&assizesort=1&asmoddatesort=2] Obviously this is a far more powerful enhancement than simply adding the "name=xxx&exact=T/F" and "opposite=T" parameters to our list contexts, and for this reason it may be a little "too much". But it would definitely make the WebDNA syntax more consistent across all contexts that create lists. - Another thought I have is to add a new [notfound] context to our searches. This would list all the database/table records that are not listed in the [founditems] context. Would this feature be useful to anyone other than me? Happy New Year everyone! Regards, Kenneth Grome WebDNA Solutions http://www.webdnasolutions.com Web Database Systems and Linux Server Management
Associated Messages, from the most recent to the oldest:
Hi Chris, You asked for our suggestions to improve WebDNA. Here are a few of my thoughts (with more to come in later posts): - Since
[formvariables] and
[listfiles] both offer the optional parameters "name=xxx&exact=T/F" as a way to limit what they find, it would be nice to have the same optional parameters in a few of our other "list" contexts too, such as: listmimeheaders listvariables listdatabases listfields listcookies - For all contexts that offer the "name=xxx&exact=T/F" options, a new "opposite=T" parameter would be useful when we want to return the opposite results. - Sorting options would be useful in these list contexts, too. We already use these sort options in our searches, so adding them to our list contexts would keep the syntax consistent: asnamesort=1/2/3/etc. denamesort=1/2/3/etc. assizesort=1/2/3/etc. desizesort=1/2/3/etc. asmoddatesort=1/2/3/etc. demoddatesort=1/2/3/etc. BY THE WAY, TO GET REALLY SERIOUS ABOUT THIS KIND OF ENHANCEMENT: Just add an optional "search=T" parameter to all our list contexts. This would tell WebDNA to recognize the same parameters we already use in our regular database/table searches. This would allow us to do things like this: [listfiles path=/to/server/logs/&search=T&bwnamedatarq=error.log&gemoddatedatarq=12/21/2014&moddatetype=date&gesizedatarq=1200000&assizesort=1&asmoddatesort=2] Obviously this is a far more powerful enhancement than simply adding the "name=xxx&exact=T/F" and "opposite=T" parameters to our list contexts, and for this reason it may be a little "too much". But it would definitely make the WebDNA syntax more consistent across all contexts that create lists. - Another thought I have is to add a new [notfound] context to our searches. This would list all the database/table records that are not listed in the
[founditems] context. Would this feature be useful to anyone other than me? Happy New Year everyone! Regards, Kenneth Grome WebDNA Solutions http://www.webdnasolutions.com Web Database Systems and Linux Server Management
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:
NT considerations (1997)
Sort Order on a page search (1997)
Smith Micro, possible listserver problems ... (2000)
WebCat2b12plugin - [search] is broken ... not! (1997)
Three new problems, maybe a fourth (1997)
Fwd: Problems with Webcatalog Plug-in (1997)
[TaxableTotal] - not working with AOL and IE (1997)
different ship dates and shopping carts -- how to? (1997)
String manipulation in Webcatalog (2001)
problem serving foreign languages text (1997)
[subtotal] problems -- help? (1998)
[WebDNA] path traversal (2020)
WebCat2 Append problem (B14Macacgi) (1997)
Triggers (1999)
[WebDNA] AC paymethod is missing (2008)
Emailer (WebCat2) (1997)
Linux Beta4 Problem (2000)
Attn: Bug in GeneralStore example b15 (1997)
Frames and WebCat (1997)
RE: Web Logs (1998)