Re: [WebDNA] maybe silly suggestion? [founditems]

This WebDNA talk-list message is from

2015


It keeps the original formatting.
numero = 111885
interpreted = N
texte = Really? On Jan 15, 2015, at 2:46 AM, christophe.billiottet@webdna.us wrote: > 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 with 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 = permanently (8.0.3), something that reminds me the Hewlett Packard way = of permanently 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 long as wanted and it would save the hassle of = writing the code to save those in a database. However, to avoid = "overheating", we would have only one name per variable, meaning that if = you store name3 as "pink", and you later store name3 as "black", then = only the last value will remain and "pink" will be overwritten 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 replaced by the variable. >=20 > It should be possible from here to build a [stofounditems] within a = [search][/search] cell, but we would need first a [listfounditems] and = it could bring up a *lot* of data in certain cases, as founditems works = like a loop. Second, 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=3Dpeoplenameddave] would be complicated: it would mean to create a = global name that would contains 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 = awesome to have a shortcut like: >> [search db=3Dallthethings.db&blahblahblah][savefounditems = name=3Dpeoplenameddave][/search] >>=20 >>=20 >>=20 >>=20 >> then later in the page, where i=92m rendering the html >> [displayfounditems use=3Dpeoplenameddave] html things = [/displayfounditems] >>=20 >>=20 >>=20 >> I know it looks like it=92s not saving that much code, but I can see = switching which search I want in the controller, and still being able to = use a universal founditems loop lower in the code. Also the ability to = reuse search 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=92re missing the point) or how we don=92t need more tags or = whatever :)=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 Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] maybe silly suggestion? [founditems] (Kenneth Grome 2015)
  2. Re: [WebDNA] maybe silly suggestion? [founditems] (christophe.billiottet@webdna.us 2015)
  3. Re: [WebDNA] maybe silly suggestion? [founditems] (Michael Davis 2015)
  4. Re: [WebDNA] maybe silly suggestion? [founditems] (Kenneth Grome 2015)
  5. Re: [WebDNA] maybe silly suggestion? [founditems] (christophe.billiottet@webdna.us 2015)
  6. Re: [WebDNA] maybe silly suggestion? [founditems] (Stuart Tremain 2015)
  7. Re: [WebDNA] maybe silly suggestion? [founditems] (Dan Strong 2015)
  8. Re: [WebDNA] maybe silly suggestion? [founditems] (Brian Burton 2015)
  9. Re: [WebDNA] maybe silly suggestion? [founditems] (Brian Burton 2015)
  10. Re: [WebDNA] maybe silly suggestion? [founditems] (Dan Strong 2015)
  11. Re: [WebDNA] maybe silly suggestion? [founditems] (Brian Burton 2015)
  12. Re: [WebDNA] maybe silly suggestion? [founditems] (=?utf-8?Q?iPhonzie=40G?= 2015)
  13. Re: [WebDNA] maybe silly suggestion? [founditems] (Brian Burton 2015)
  14. Re: [WebDNA] maybe silly suggestion? [founditems] (Donovan Brooke 2015)
  15. Re: [WebDNA] maybe silly suggestion? [founditems] (Kenneth Grome 2015)
  16. Re: [WebDNA] maybe silly suggestion? [founditems] (Dan Strong 2015)
  17. Re: [WebDNA] maybe silly suggestion? [founditems] (Kenneth Grome 2015)
  18. Re: [WebDNA] maybe silly suggestion? [founditems] (Donovan Brooke 2015)
  19. Re: [WebDNA] maybe silly suggestion? [founditems] (=?utf-8?Q?iPhonzie=40G?= 2015)
  20. Re: [WebDNA] maybe silly suggestion? [founditems] (=?utf-8?Q?iPhonzie=40G?= 2015)
  21. Re: [WebDNA] maybe silly suggestion? [founditems] (christophe.billiottet@webdna.us 2015)
  22. Re: [WebDNA] maybe silly suggestion? [founditems] (Kenneth Grome 2015)
  23. Re: [WebDNA] maybe silly suggestion? [founditems] (=?utf-8?Q?iPhonzie=40G?= 2015)
  24. Re: [WebDNA] maybe silly suggestion? [founditems] (=?utf-8?Q?iPhonzie=40G?= 2015)
  25. Re: [WebDNA] maybe silly suggestion? [founditems] (Stephen Reiss 2015)
  26. Re: [WebDNA] maybe silly suggestion? [founditems] (Terry Wilson 2015)
  27. Re: [WebDNA] maybe silly suggestion? [founditems] (Terry Wilson 2015)
  28. Re: [WebDNA] maybe silly suggestion? [founditems] (Lawrence Banahan 2015)
  29. Re: [WebDNA] maybe silly suggestion? [founditems] ("Psi Prime Inc, Matthew A Perosi " 2015)
  30. Re: [WebDNA] maybe silly suggestion? [founditems] (Donovan Brooke 2015)
  31. Re: [WebDNA] maybe silly suggestion? [founditems] (Donovan Brooke 2015)
  32. Re: [WebDNA] maybe silly suggestion? [founditems] (Kenneth Grome 2015)
  33. Re: [WebDNA] maybe silly suggestion? [founditems] (Terry Wilson 2015)
  34. Re: [WebDNA] maybe silly suggestion? [founditems] (Donovan Brooke 2015)
  35. Re: [WebDNA] maybe silly suggestion? [founditems] (Donovan Brooke 2015)
  36. Re: [WebDNA] maybe silly suggestion? [founditems] (Terry Wilson 2015)
  37. Re: [WebDNA] maybe silly suggestion? [founditems] (Kenneth Grome 2015)
  38. Re: [WebDNA] maybe silly suggestion? [founditems] (Donovan Brooke 2015)
  39. Re: [WebDNA] maybe silly suggestion? [founditems] (Donovan Brooke 2015)
  40. Re: [WebDNA] maybe silly suggestion? [founditems] (christophe.billiottet@webdna.us 2015)
  41. Re: [WebDNA] maybe silly suggestion? [founditems] (Kenneth Grome 2015)
  42. [WebDNA] maybe silly suggestion? [founditems] (Brian Burton 2015)
Really? On Jan 15, 2015, at 2:46 AM, christophe.billiottet@webdna.us wrote: > 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 with 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 = permanently (8.0.3), something that reminds me the Hewlett Packard way = of permanently 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 long as wanted and it would save the hassle of = writing the code to save those in a database. However, to avoid = "overheating", we would have only one name per variable, meaning that if = you store name3 as "pink", and you later store name3 as "black", then = only the last value will remain and "pink" will be overwritten 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 replaced by the variable. >=20 > It should be possible from here to build a [stofounditems] within a = [search][/search] cell, but we would need first a [listfounditems] and = it could bring up a *lot* of data in certain cases, as founditems works = like a loop. Second, 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=3Dpeoplenameddave] would be complicated: it would mean to create a = global name that would contains 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 = awesome to have a shortcut like: >> [search db=3Dallthethings.db&blahblahblah][savefounditems = name=3Dpeoplenameddave][/search] >>=20 >>=20 >>=20 >>=20 >> then later in the page, where i=92m rendering the html >> [displayfounditems use=3Dpeoplenameddave] html things = [/displayfounditems] >>=20 >>=20 >>=20 >> I know it looks like it=92s not saving that much code, but I can see = switching which search I want in the controller, and still being able to = use a universal founditems loop lower in the code. Also the ability to = reuse search 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=92re missing the point) or how we don=92t need more tags or = whatever :)=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 Donovan Brooke

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:

emailer (1997) I'm having trouble using [url][interpret][math] together in lookup (1997) What changes does $purchase make? (1998) Redirect frame targets (1998) WebCatalog can't find database (1997) international time (1997) [AppendFile] problem (WebCat2b13 Mac .acgi) (1997) Recursion & WebDNA (1999) Resume Catalog ? (1997) Protect (1997) syntax question, not in online refernce (1997) question: search return in order (1997) writefile to create static pages (2003) Help! WebCat2 bug (1997) Java Path (2004) Country & Ship-to address & other fields ? (1997) Version 2.1.3 question :-) (2003) RFE: [include file=filename.inc&strip=t] (2002) Summ=T Problem (1997) Replace context problem ... (1997)