Re: [WebDNA] maybe silly suggestion? [founditems]
This WebDNA talk-list message is from 2015
It keeps the original formatting.
numero = 111888
interpreted = N
texte = I already do something similar with a preparse function to store things like= properly formatted dates for 1 day, 1 month, 30 minute, 1 year, etc. cookie= s. Is this something along that line, setting variables from a db in a prepa= rse script? Sent from my iPad > On Jan 15, 2015, at 7:23 AM, Donovan Brooke
wrote: >=20 > I guess I don=E2=80=99t understand these =E2=80=9Cimprovements=E2=80=9D be= ing made on whim. >=20 > *constants* (static variables) are a staple feature of any language and We= bDNA already has them.. yes, surviving a reboot. >=20 > What=E2=80=99s the big mystery here? >=20 > Donovan >=20 >=20 >=20 >=20 >> On Jan 15, 2015, at 2:46 AM, christophe.billiottet@webdna.us wrote: >>=20 >> I find the idea interesting. There is quite nothing in WebDNA that cannot= be done with a little bit of creativity, but if a tag (or "codon" to stick w= ith biological language) can simplify coding, then I am for it. >>=20 >> The following is for debate: >>=20 >> We are currently working to add a simple tag that stores variables perman= ently (8.0.3), something that reminds me the Hewlett Packard way of permanen= tly storing variables (back in 1978) on a hp29c (named "Continuous Memory").= This has to survive a reboot, and the variable and the name should be as lo= ng as wanted and it would save the hassle of writing the code to save those i= n a database. However, to avoid "overheating", we would have only one name p= er variable, meaning that if you store name3 as "pink", and you later store n= ame3 as "black", then only the last value will remain and "pink" will be ove= rwritten by "black" >>=20 >> The process will use [sto] and [rcl] (for store and recall) + the name of= the variable + the variable itself >>=20 >> There would be four possible ways to describe such a feature: >>=20 >> [sto name=3Dvariable] >> [sto name]variable[/sto] >> [sto]name=3Dvariable[/sto] >> [sto]name1=3Dvariable1,name2=3Dvariable2,name3=3Dvariable3[/sto] >>=20 >> The last one it obviously better as it allows to store multiple variables= and use long names, if requested. >>=20 >> Recall would work individually: [rcl name2] so we can just get the codon r= eplaced by the variable. >>=20 >> It should be possible from here to build a [stofounditems] within a [sear= ch][/search] cell, but we would need first a [listfounditems] and it could b= ring up a *lot* of data in certain cases, as founditems works like a loop. S= econd, the names will be identical: Imagine a db with 100,000 entries from 1= to 100,000 >>=20 >> [search db=3Dallthethings.db&grnamedata=3D1] >> [founditems] >> [name]=3D[variable] >> [/founditems] >> [/search] >>=20 >> Any idea welcomed there. >>=20 >> Then we could have a [rclfounditems] >>=20 >> Giving a name as Brian suggests, like [stofounditems name=3Dpeoplenamedda= ve] would be complicated: it would mean to create a global name that would c= ontains an unlimited number of names and variables. >>=20 >>=20 >> Well, these are just ideas that go through my head. Debate welcomed. >>=20 >> - chris >>=20 >>=20 >>=20 >>=20 >>> On 14 Jan 2015, at 23:57, Brian Burton wrote: >>>=20 >>> to help separate my controller logic from my display code it would be aw= esome to have a shortcut like: >>> [search db=3Dallthethings.db&blahblahblah][savefounditems name=3Dpeoplen= ameddave][/search] >>>=20 >>>=20 >>>=20 >>>=20 >>> then later in the page, where i=E2=80=99m rendering the html >>> [displayfounditems use=3Dpeoplenameddave] html things [/displayfounditem= s] >>>=20 >>>=20 >>>=20 >>> I know it looks like it=E2=80=99s not saving that much code, but I can s= ee switching which search I want in the controller, and still being able to u= se a universal founditems loop lower in the code. Also the ability to reuse s= earch results (if needed) without doing the same search again.=20 >>>=20 >>> ok, feel free to start telling me how you can do this with a table (you=E2= =80=99re missing the point) or how we don=E2=80=99t need more tags or whatev= er :)=20 >>>=20 >>>=20 >>> -Brian B. Burton >>> --------------------------------------------------------- >>> This message is sent to you because you are subscribed to >>> the mailing list . >>> To unsubscribe, E-mail to: >>> archives: http://mail.webdna.us/list/talk@webdna.us >>> Bug Reporting: support@webdna.us >>=20 >> --------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> archives: http://mail.webdna.us/list/talk@webdna.us >> Bug Reporting: support@webdna.us >=20 > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us
Associated Messages, from the most recent to the oldest:
I already do something similar with a preparse function to store things like= properly formatted dates for 1 day, 1 month, 30 minute, 1 year, etc. cookie= s. Is this something along that line, setting variables from a db in a prepa= rse script? Sent from my iPad > On Jan 15, 2015, at 7:23 AM, Donovan Brooke wrote: >=20 > I guess I don=E2=80=99t understand these =E2=80=9Cimprovements=E2=80=9D be= ing made on whim. >=20 > *constants* (static variables) are a staple feature of any language and We= bDNA already has them.. yes, surviving a reboot. >=20 > What=E2=80=99s the big mystery here? >=20 > Donovan >=20 >=20 >=20 >=20 >> On Jan 15, 2015, at 2:46 AM, christophe.billiottet@webdna.us wrote: >>=20 >> I find the idea interesting. There is quite nothing in WebDNA that cannot= be done with a little bit of creativity, but if a tag (or "codon" to stick w= ith biological language) can simplify coding, then I am for it. >>=20 >> The following is for debate: >>=20 >> We are currently working to add a simple tag that stores variables perman= ently (8.0.3), something that reminds me the Hewlett Packard way of permanen= tly storing variables (back in 1978) on a hp29c (named "Continuous Memory").= This has to survive a reboot, and the variable and the name should be as lo= ng as wanted and it would save the hassle of writing the code to save those i= n a database. However, to avoid "overheating", we would have only one name p= er variable, meaning that if you store name3 as "pink", and you later store n= ame3 as "black", then only the last value will remain and "pink" will be ove= rwritten by "black" >>=20 >> The process will use [sto] and [rcl] (for store and recall) + the name of= the variable + the variable itself >>=20 >> There would be four possible ways to describe such a feature: >>=20 >> [sto name=3Dvariable] >> [sto name]variable[/sto] >> [sto]name=3Dvariable[/sto] >> [sto]name1=3Dvariable1,name2=3Dvariable2,name3=3Dvariable3[/sto] >>=20 >> The last one it obviously better as it allows to store multiple variables= and use long names, if requested. >>=20 >> Recall would work individually: [rcl name2] so we can just get the codon r= eplaced by the variable. >>=20 >> It should be possible from here to build a [stofounditems] within a [sear= ch][/search] cell, but we would need first a [listfounditems] and it could b= ring up a *lot* of data in certain cases, as founditems works like a loop. S= econd, the names will be identical: Imagine a db with 100,000 entries from 1= to 100,000 >>=20 >> [search db=3Dallthethings.db&grnamedata=3D1] >> [founditems] >> [name]=3D[variable] >> [/founditems] >> [/search] >>=20 >> Any idea welcomed there. >>=20 >> Then we could have a [rclfounditems] >>=20 >> Giving a name as Brian suggests, like [stofounditems name=3Dpeoplenamedda= ve] would be complicated: it would mean to create a global name that would c= ontains an unlimited number of names and variables. >>=20 >>=20 >> Well, these are just ideas that go through my head. Debate welcomed. >>=20 >> - chris >>=20 >>=20 >>=20 >>=20 >>> On 14 Jan 2015, at 23:57, Brian Burton wrote: >>>=20 >>> to help separate my controller logic from my display code it would be aw= esome to have a shortcut like: >>> [search db=3Dallthethings.db&blahblahblah][savefounditems name=3Dpeoplen= ameddave][/search] >>>=20 >>>=20 >>>=20 >>>=20 >>> then later in the page, where i=E2=80=99m rendering the html >>> [displayfounditems use=3Dpeoplenameddave] html things [/displayfounditem= s] >>>=20 >>>=20 >>>=20 >>> I know it looks like it=E2=80=99s not saving that much code, but I can s= ee switching which search I want in the controller, and still being able to u= se a universal founditems loop lower in the code. Also the ability to reuse s= earch results (if needed) without doing the same search again.=20 >>>=20 >>> ok, feel free to start telling me how you can do this with a table (you=E2= =80=99re missing the point) or how we don=E2=80=99t need more tags or whatev= er :)=20 >>>=20 >>>=20 >>> -Brian B. Burton >>> --------------------------------------------------------- >>> This message is sent to you because you are subscribed to >>> the mailing list . >>> To unsubscribe, E-mail to: >>> archives: http://mail.webdna.us/list/talk@webdna.us >>> Bug Reporting: support@webdna.us >>=20 >> --------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> archives: http://mail.webdna.us/list/talk@webdna.us >> Bug Reporting: support@webdna.us >=20 > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us
Terry Wilson
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] Permission Settings (2009)
redirect question (2001)
[Fwd: Email Format] (1998)
WebCat2 - many [carts] on one template page? (1997)
SV: Mass Mail (2000)
carriage returns in data (1997)
More on the email templates (1997)
WebCatalog on Mac AIX box (1998)
code to phantom spacing (2001)
Generating Report Totals (1997)
Pref settings? (1998)
WC1.6 to WC2 date formatting -FIXED! (1997)
[WebDNA] server vs fcgi (2018)
Multiple Ad databases? (1997)
Unique SKUs (2000)
Re:Email (1998)
Not reading code (1997)
WCS Newbie question (1997)
What abobut variables named max ??? (2000)
quantity limit (1998)