Re: [WebDNA] maybe silly suggestion? [founditems]
This WebDNA talk-list message is from 2015
It keeps the original formatting.
numero = 111932
interpreted = N
texte = --Apple-Mail=_EBCB828A-D67E-4882-9EF1-BA2CC290CC5A Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 I=E2=80=99m all for breaking things up into reusable modules and files, = but there=E2=80=99s a point where it just gets silly. How great would it = be if you DIDN'T need to include private functions (i.e. functions only = used on one page) at the top of the page, but could instead put them at = the bottom of the page, below all the logic and view code=E2=80=A6 = *sigh* the disadvantages of a script interpreter that goes from top to = bottom, no exceptions! -BBB > On Jan 15, 2015, at 3:40 PM, Dan Strong
wrote: >=20 > [include file=3DfunctionsLocalToThispage.inc] --Apple-Mail=_EBCB828A-D67E-4882-9EF1-BA2CC290CC5A Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 I=E2=80=99m all for breaking things up into reusable modules = and files, but there=E2=80=99s a point where it just gets silly. How = great would it be if you DIDN'T need to include private functions (i.e. = functions only used on one page) at the top of the page, but could = instead put them at the bottom of the page, below all the logic and view = code=E2=80=A6 *sigh* the disadvantages of a script interpreter that goes = from top to bottom, no exceptions!
-BBB
[include = file=3DfunctionsLocalToThispage.inc]
<= br class=3D"">
--Apple-Mail=_EBCB828A-D67E-4882-9EF1-BA2CC290CC5A Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 I=E2=80=99m all for breaking things up into reusable modules and files, = but there=E2=80=99s a point where it just gets silly. How great would it = be if you DIDN'T need to include private functions (i.e. functions only = used on one page) at the top of the page, but could instead put them at = the bottom of the page, below all the logic and view code=E2=80=A6 = *sigh* the disadvantages of a script interpreter that goes from top to = bottom, no exceptions! -BBB > On Jan 15, 2015, at 3:40 PM, Dan Strong wrote: >=20 > [include file=3DfunctionsLocalToThispage.inc] --Apple-Mail=_EBCB828A-D67E-4882-9EF1-BA2CC290CC5A Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 I=E2=80=99m all for breaking things up into reusable modules = and files, but there=E2=80=99s a point where it just gets silly. How = great would it be if you DIDN'T need to include private functions (i.e. = functions only used on one page) at the top of the page, but could = instead put them at the bottom of the page, below all the logic and view = code=E2=80=A6 *sigh* the disadvantages of a script interpreter that goes = from top to bottom, no exceptions!
-BBB
[include = file=3DfunctionsLocalToThispage.inc]
<= br class=3D"">
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:
Conditional searching & displaying (1997)
Need help (1998)
Sharing DBs across domains (2001)
Format question WC Mac f3 (1997)
Re2: frames & carts (1997)
FTP and [shell] (2003)
learning PHP (2007)
Another form question (2000)
can WC render sites out? (1997)
writefile and texte (1997)
WebCatalog/WebMerchant 2.1 (1998)
Setting up WebCatalog with Retail Pro data (1996)
OT: Variables in printed URL (2007)
Repost: Orderfile, Grandtotal: How do I get it to all add up. (2000)
any idea (2004)
Dynamic PDFs? (2002)
AOL and referrers on target=_blank (2000)
Botched cart numbers in webmerchant 2.1x email with webcat 3 (1998)
WebCat2b13MacPlugIn - [showif][search][/showif] (1997)
international time (1997)