Re: [WebDNA] Feature Request: [returnhtml]

This WebDNA talk-list message is from

2016


It keeps the original formatting.
numero = 112900
interpreted = N
texte = 487 --001a113e40b81cd6d505391afef4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable You can write dumptable to a function that does just that. I would not clutter the language with it. Something like this when you pass in [db=3D]: [function name=3Ddb_to_tab&scope=3Dglobal] [!]THIS WILL NEED TO BE WRITTEN TO A FILE[/!] [listfields db=3D[db]][hideif [index]=3D1][tab][/hideif][/listfields] [search db=3D[unurl][db][/unurl]][!] [/!][founditems][interpret][[word]][/interpret][/listwords] [/founditems][/search] [/function] On Thu, Mar 24, 2016 at 4:21 PM, Brian Burton wrote: > Awesome! Can I add two more? > > 1) [dumptable table=3Dblah.tab&type=3Dtext/html] > Displays the contents of the table in either tab delimited format (handy > inside a [writefile]), > or an HTML table (all made by webdna of course) > Debugging tables can be a major pain sometimes, we need some help here. > > 2) Add an optional second line to the .hdr file defining per field in the > same > order as the field names, the field type (text/number/date/autonumber) so > that we don't have to spell it out with each and every search sort we > write. > > Accounts.hdr > ID (tab) Adddate (tab) AddTime (tab) Name (tab) email (tab) zipcode > autonumber (tab) date (tab) time (tab) text (tab) text (tab) number > > > Thanks! > -Brian B. Burton > > > > On Mar 24, 2016, at 1:47 PM, christophe.billiottet@webdna.us wrote: > > > > We note all the ideas, and implement what we think are the best ideas. > > > > - chris > > > > > > > > > > > >> On Mar 24, 2016, at 21:09, Brian Burton wrote: > >> > >> Problem: I have webpages that create a tremendous amount of whitespace > at or near the top of the webpage due to all the webdna stuff going on. > >> Occasionally it bothers me enough that I comment out the carriage > returns, but that is SUPER MESSY code to look at. > >> In a function, we have the ability to limit the output with a > [return][/return] pair. > >> > >> Proposed Solution: > >> What would be a great addition to WebDNA would be a > [returnhtml][/returnhtml] tag pair. It would only be allowed once per > rendered page. > >> On any page that doesn=E2=80=99t have this pair, everything would work= as it > currently does. > >> On any page that does have the pair, WebDNA only returns to Apache > what=E2=80=99s between the pair. > >> > >> Now any amount of webdna code stays nicely safe and hidden, doesn=E2= =80=99t > generate any whitespace, and means we can make very clean HTML output. > >> > >> (also helps move us a step closer to MVC, but ignore the man behind > that curtain :) > >> > >> -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 > > > > --------------------------------------------------------- > > 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 > > > --------------------------------------------------------- > 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 > --001a113e40b81cd6d505391afef4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
You can write dumptable to a function that does just that.= I would not clutter the language with it. Something like this when you pas= s in [db=3D]:

[function name=3Ddb_to_tab&scope= =3Dglobal]
[!]THIS WILL NEED TO BE WRITTEN TO A FILE[/!]
[listfields db=3D[db]][hideif [index]=3D1][tab][/hideif][/listfields]
[search db=3D[unurl][db][/unurl]][!]
=C2=A0 [/!][founditem= s][interpret][[word]][/interpret][/listwords]
[/founditems][/sear= ch]
[/function]


On Thu, Mar 24, 2016 at 4:21 PM, B= rian Burton <brian@burtons.com> wrote:
Awesome! Can I add two more?

1) [dumptable table=3Dblah.tab&type=3Dtext/html]
Displays the contents of the table in either tab delimited format (handy in= side a [writefile]),
or an HTML table (all made by webdna of course)
Debugging tables can be a major pain sometimes, we need some help here.

2) Add an optional second line to the .hdr file defining per field in the s= ame
order as the field names, the field type (text/number/date/autonumber) so that we don't have to spell it out with each and every search sort we w= rite.

Accounts.hdr
ID (tab) Adddate (tab) AddTime (tab) Name (tab) email (tab) zipcode
autonumber (tab) date (tab) time (tab) text (tab) text (tab) number


Thanks!
-Brian B. Burton


> On Mar 24, 2016, at 1:47 PM, christophe.billiottet@webdna.us wrote:
>
> We note all the ideas, and implement what we think are the best ideas.=
>
> - chris
>
>
>
>
>
>> On Mar 24, 2016, at 21:09, Brian Burton <brian@burtons.com> wrote:
>>
>> Problem: I have webpages that create a tremendous amount of whites= pace at or near the top of the webpage due to all the webdna stuff going on= ..
>> Occasionally it bothers me enough that I comment out the carriage = returns, but that is SUPER MESSY code to look at.
>> In a function, we have the ability to limit the output with a [ret= urn][/return] pair.
>>
>> Proposed Solution:
>> What would be a great addition to WebDNA would be a [returnhtml][/= returnhtml] tag pair. It would only be allowed once per rendered page.
>> On any page that doesn=E2=80=99t have this pair, everything would = work as it currently does.
>> On any page that does have the pair, WebDNA only returns to Apache= what=E2=80=99s between the pair.
>>
>> Now any amount of webdna code stays nicely safe and hidden, doesn= =E2=80=99t generate any whitespace, and means we can make very clean HTML o= utput.
>>
>> (also helps move us a step closer to MVC, but ignore the man behin= d that curtain :)
>>
>> -Brian B. Burton
>> ---------------------------------------------------------
>> This message is sent to you because you are subscribed to
>> the mailing list <talk@webdna= ..us>.
>> To unsubscribe, E-mail to: <talk-leave@webdna.us>
>> archives: http://mail.webdna.us/list/talk@webdna.u= s
>> Bug Reporting: support@webdna= ..us
>
> ---------------------------------------------------------
> This message is sent to you because you are subscribed to
> the mailing list <talk@webdna.us<= /a>>.
> To unsubscribe, E-mail to: <
talk-leave@webdna.us>
> archives: http://mail.webdna.us/list/talk@webdna.us
> Bug Reporting:
support@webdna.us<= /a>


---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <
talk@webdna.us&g= t;.
To unsubscribe, E-mail to: <talk= -leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us

--------------------------------------------------------- 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 --001a113e40b81cd6d505391afef4-- . Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] Feature Request: [returnhtml] (dbrooke@euca.us 2016)
  2. Re: [WebDNA] Feature Request: [returnhtml] (christophe.billiottet@webdna.us 2016)
  3. Re: [WebDNA] Feature Request: [returnhtml] (christophe.billiottet@webdna.us 2016)
  4. Re: [WebDNA] Feature Request: [returnhtml] (William DeVaul 2016)
  5. Re: [WebDNA] Feature Request: [returnhtml] ("Matthew A Perosi, Psi Prime" 2016)
  6. Re: [WebDNA] Feature Request: [returnhtml] (Kenneth Grome 2016)
487 --001a113e40b81cd6d505391afef4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable You can write dumptable to a function that does just that. I would not clutter the language with it. Something like this when you pass in [db=3D]: [function name=3Ddb_to_tab&scope=3Dglobal] [!]THIS WILL NEED TO BE WRITTEN TO A FILE[/!] [listfields db=3D[db]][hideif [index]=3D1][tab][/hideif][/listfields] [search db=3D[unurl][db][/unurl]][!] [/!][founditems][interpret][[word]][/interpret][/listwords] [/founditems][/search] [/function] On Thu, Mar 24, 2016 at 4:21 PM, Brian Burton wrote: > Awesome! Can I add two more? > > 1) [dumptable table=3Dblah.tab&type=3Dtext/html] > Displays the contents of the table in either tab delimited format (handy > inside a [writefile]), > or an HTML table (all made by webdna of course) > Debugging tables can be a major pain sometimes, we need some help here. > > 2) Add an optional second line to the .hdr file defining per field in the > same > order as the field names, the field type (text/number/date/autonumber) so > that we don't have to spell it out with each and every search sort we > write. > > Accounts.hdr > ID (tab) Adddate (tab) AddTime (tab) Name (tab) email (tab) zipcode > autonumber (tab) date (tab) time (tab) text (tab) text (tab) number > > > Thanks! > -Brian B. Burton > > > > On Mar 24, 2016, at 1:47 PM, christophe.billiottet@webdna.us wrote: > > > > We note all the ideas, and implement what we think are the best ideas. > > > > - chris > > > > > > > > > > > >> On Mar 24, 2016, at 21:09, Brian Burton wrote: > >> > >> Problem: I have webpages that create a tremendous amount of whitespace > at or near the top of the webpage due to all the webdna stuff going on. > >> Occasionally it bothers me enough that I comment out the carriage > returns, but that is SUPER MESSY code to look at. > >> In a function, we have the ability to limit the output with a > [return][/return] pair. > >> > >> Proposed Solution: > >> What would be a great addition to WebDNA would be a > [returnhtml][/returnhtml] tag pair. It would only be allowed once per > rendered page. > >> On any page that doesn=E2=80=99t have this pair, everything would work= as it > currently does. > >> On any page that does have the pair, WebDNA only returns to Apache > what=E2=80=99s between the pair. > >> > >> Now any amount of webdna code stays nicely safe and hidden, doesn=E2= =80=99t > generate any whitespace, and means we can make very clean HTML output. > >> > >> (also helps move us a step closer to MVC, but ignore the man behind > that curtain :) > >> > >> -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 > > > > --------------------------------------------------------- > > 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 > > > --------------------------------------------------------- > 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 > --001a113e40b81cd6d505391afef4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
You can write dumptable to a function that does just that.= I would not clutter the language with it. Something like this when you pas= s in [db=3D]:

[function name=3Ddb_to_tab&scope= =3Dglobal]
[!]THIS WILL NEED TO BE WRITTEN TO A FILE[/!]
[listfields db=3D[db]][hideif [index]=3D1][tab][/hideif][/listfields]
[search db=3D[unurl][db][/unurl]][!]
=C2=A0 [/!][founditem= s][interpret][[word]][/interpret][/listwords]
[/founditems][/sear= ch]
[/function]


On Thu, Mar 24, 2016 at 4:21 PM, B= rian Burton <brian@burtons.com> wrote:
Awesome! Can I add two more?

1) [dumptable table=3Dblah.tab&type=3Dtext/html]
Displays the contents of the table in either tab delimited format (handy in= side a [writefile]),
or an HTML table (all made by webdna of course)
Debugging tables can be a major pain sometimes, we need some help here.

2) Add an optional second line to the .hdr file defining per field in the s= ame
order as the field names, the field type (text/number/date/autonumber) so that we don't have to spell it out with each and every search sort we w= rite.

Accounts.hdr
ID (tab) Adddate (tab) AddTime (tab) Name (tab) email (tab) zipcode
autonumber (tab) date (tab) time (tab) text (tab) text (tab) number


Thanks!
-Brian B. Burton


> On Mar 24, 2016, at 1:47 PM, christophe.billiottet@webdna.us wrote:
>
> We note all the ideas, and implement what we think are the best ideas.=
>
> - chris
>
>
>
>
>
>> On Mar 24, 2016, at 21:09, Brian Burton <brian@burtons.com> wrote:
>>
>> Problem: I have webpages that create a tremendous amount of whites= pace at or near the top of the webpage due to all the webdna stuff going on= ..
>> Occasionally it bothers me enough that I comment out the carriage = returns, but that is SUPER MESSY code to look at.
>> In a function, we have the ability to limit the output with a [ret= urn][/return] pair.
>>
>> Proposed Solution:
>> What would be a great addition to WebDNA would be a [returnhtml][/= returnhtml] tag pair. It would only be allowed once per rendered page.
>> On any page that doesn=E2=80=99t have this pair, everything would = work as it currently does.
>> On any page that does have the pair, WebDNA only returns to Apache= what=E2=80=99s between the pair.
>>
>> Now any amount of webdna code stays nicely safe and hidden, doesn= =E2=80=99t generate any whitespace, and means we can make very clean HTML o= utput.
>>
>> (also helps move us a step closer to MVC, but ignore the man behin= d that curtain :)
>>
>> -Brian B. Burton
>> ---------------------------------------------------------
>> This message is sent to you because you are subscribed to
>> the mailing list <talk@webdna= ..us>.
>> To unsubscribe, E-mail to: <talk-leave@webdna.us>
>> archives: http://mail.webdna.us/list/talk@webdna.u= s
>> Bug Reporting: support@webdna= ..us
>
> ---------------------------------------------------------
> This message is sent to you because you are subscribed to
> the mailing list <talk@webdna.us<= /a>>.
> To unsubscribe, E-mail to: <
talk-leave@webdna.us>
> archives: http://mail.webdna.us/list/talk@webdna.us
> Bug Reporting:
support@webdna.us<= /a>


---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <
talk@webdna.us&g= t;.
To unsubscribe, E-mail to: <talk= -leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdna.us

--------------------------------------------------------- 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 --001a113e40b81cd6d505391afef4-- . William DeVaul

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:

Year 2070 (2000) Some Questions (1997) [WebDNA] Cheers (2008) Web Developer Product Awards (1997) [SameAsShipping] (2005) syntax question, not in online refernce (1997) Re[2]: when is failing to [URL]ize values in a comparison ri (1999) Calendar (1997) 2.1b3 --> way slow (1997) apostrophe in search item (1997) wierd [cart] action! (1997) Some Advise needed (1997) Question re: FlushDatabases (1997) Help me... (1998) Checking for blank form fields (sort of...) (1998) Classified (1999) WebCat2: multiple currency support (1997) TRAINING videos - Prove IT. (1998) Nested tags count question (1997) Help formatting search results w/ table (1997)