Re: [WebDNA] improvements

This WebDNA talk-list message is from

2015


It keeps the original formatting.
numero = 111948
interpreted = N
texte = --089e0160b88e30ba51050cc93229 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi all, I'm enjoying reading all the views here about WebDNA improvements, and I'm both grateful and impressed by Christophe's commitment to keeping the language alive. A few things I would like / agree with: *1. [setcookie]* Ensure that it supports all possible options i.e 'secure' and 'HttpOnly', though admittedly these can be set now using workarounds involving [setmimeheaders]. *2. [grep]* A new [regex] that supports standard grep is a great idea. *3. [setmimeheader]* (This may be fixed in latest versions) Ensure that all possible mime header options are supported. *4. [sendmail]* Add the ability to set the Return-Path *5. HTML Parser* The ability to properly parse HTML would be incredibly useful. Maybe a [tag] that uses one of the better HTML parsers out there. *6. Cryptography* Access to a wider set of cryptography tools so we can use current best practice for secure salted password hashing ( https://crackstation.net/hashing-security.htm). At the moment we have security through obscurity as the cryptography used by [encrypt] has never been properly explained. There are a number of other things that should be easier in WebDNA, these probably don't need new tags but just some tutorials showing the best practice in use out there: *1. Cookie based login / authentication* The best method for cookie based username / password login (i.e. not realm based security). A lot of us have implemented this, but it would be good to have a best practice guide. *2. Oauth Authentication* I still struggle when trying to use Oauth to access various API's. I usually manage to hack my way through each challenge, but again a best practice would be great. *3. API Wrappers* WebDNA API wrappers for the most common / popular APIs, i.e. Twitter, Facebook, MailChimp, Flickr, etc *4. Shell Tools* An overview of how to use some of the most useful [shell] tools out there (I use imagemagick, wkhtmltopdf, ghostscript, and unoconv) Finally, and this may over-complicate WebDNA, but I would love some way of easily defining data types for WebDNA fields - similar to SQL data types. I spend a lot of time writing code that validates and checks data, if there was a way of hard baking this that would be great. Anyhow there's my thoughts. Take care - Tom =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Digital Revolutionaries 1st Floor, Castleriver House 14-15 Parliament Street Temple Bar,Dublin 2 Ireland ---------------------------------------------- [t]: + 353 1 4403907 [e]: [w]: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D On 16 January 2015 at 14:00, wrote: > If we work on the [switch] cell to introduce the full set of comparisons > available with [showif], will you all still need the [elseif] ? > I ask because if seems to me this is something missing with [switch] that > should have been there in the first place, but the [elseif] concept could > show a little bit heavy and less elegant=E2=80=A6 > > - chris > > > > On 15 Jan 2015, at 20:58, iPhonzie@G wrote: > > > > The do/while and repeat/until scenarios can be easily enough managed > with [loop], so that doesn=E2=80=99t bother me enough to need the additio= nal tags, > but I would love to see [break] available in EVERY looping context - > founditems, listwords, formvariables, etc. > > > > > > [elseif] would be a great addition for situations where you have a > number of mutually exclusive conditions that are to complex for [switch].= I > have lots of code that looks like this: > > > > [if (condition1)] > > [then] > > do stuff 1 > > [/then] > > [else] > > [if (condition2)] > > [then] > > do stuff 2 > > [/then] > > [else] > > [if (condition3)] > > [then] > > do stuff 3 > > [/then] > > [else] > > do default stuff > > [/else] > > [/if] > > [/else] > > [/if] > > [/else] > > [/if] > > > > This would be much nicer if I could write: > > > > [if (condition1)] > > [then] > > do stuff 1 > > [/then] > > [elseif (condition2)] > > do stuff 2 > > [/elseif] > > [elseif (condition3)] > > do stuff 3 > > [/elseif] > > [else] > > do default stuff > > [/else] > > [/if] > > > > > > This could similarly be addressed with an alternative form of > switch/case. One possibility would be if no parameters are in the [switch= ] > tag, then [if]-style comparisons could be put into each [case] tag: > > > > [switch] > > [case (condition1)] > > do stuff 1 > > [/case] > > [case (condition2)] > > do stuff 2 > > [/case] > > [case (condition3)] > > do stuff 3 > > [/case] > > [default] > > do default stuff > > [/default] > > [/switch] > > > > > > =E2=80=94 Brian Fries > > > > On January 15, 2015 at 9:34:47 AM, Psi Prime Inc, Matthew A Perosi ( > matt@psiprime.com) wrote: > > > >> There have been plenty of time when I needed a [do]/[while] or a > >> [repeat]/[until] statement. > >> > >> The [removehtml] needs to be improved to recognize the new format for > >> HTML. Instead of removing HTML tags formatted like this: > >> > >> it needs to also recognize this new format like this: > >> > >> > >> Secure cookies are a good idea and I could use those too. > >> > >> -Matt > >> > >> > >> On 1/15/2015 11:23 AM, christophe.billiottet@webdna.us wrote: > >> > Some possible ideas; please explain specifically what you want with > "[elseif] to [if] context" and the [switch] > >> > > >> > The "commerce tags" are not supported anymore. Also, PostGres is not > on the roadmap at this time. > >> > > >> > You have had an opportunity earlier. > >> > > >> > - chris > >> > > >> > > >> > > >> > > >> >> On 15 Jan 2015, at 18:56, Donovan Brooke wrote: > >> >> > >> >> If resources are going to be put into development rather than > marketing, why not make some *standardized* improvements that will attrac= t > new users. > >> >> I=E2=80=99m talking about things that programmers look for in a lan= guage. > >> >> > >> >> Off the top of my head: > >> >> [elseif] to [if] context. > >> >> > >> >> Database support, starting with PostGres > >> >> ie. [SQLConnect dbtype=3DPostGres] > >> >> > >> >> [sendmail] (local) override (instead of global server setting) of > things like smtp port/auth, TLS settings, etc.. We already have the roadm= ap > to make that local. > >> >> > >> >> [switch..] context with more comparison options. > >> >> > >> >> Add Md5 (and other newer encryption, digest, etc.) to encrypt.. > >> >> for md5, just copy APOP. APOP is not very descriptive. > >> >> [encrypt method=3Dmd5][/encrypt] > >> >> > >> >> secure param for setcookie > >> >> > >> >> Some other improvements off the top of my head: > >> >> > >> >> For the commerce tags (which, yes, they are still very > useful):=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6.. > >> >> [listHeaders][/listHeaders] > >> >> ie.: > >> >> [orderfile cart=3D[cart]] > >> >> [listHeaders name=3DAccountnum] > >> >> [name]=3D[value]
> >> >> [/listheaders] > >> >> [/orderfile] > >> >> > >> >> would produce: > >> >> accountnum=3D > >> >> > >> >> =3D=3D > >> >> Ability to set a flag to use a WebDNA Database with [orderfile] > instead of the > >> >> order files that are created. > >> >> > >> >> =3D=3D > >> >> Ability to specify a unique ID within [addlineitems..], instead of > sku > >> >> [addlineitems uniqueID=3Dp_id&p_id=3DX&cart=3D[cart]][/addlineitems= ] > >> >> =E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2= =80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80= =A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6= =E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6... > >> >> > >> >> > >> >> "Best Match" used in WebDNA Search system is munged when using the > Summ=3DT param. <=E2=80=94 I don=E2=80=99t think that ever got fixed. > >> >> > >> >> Improvements to [removehtml]: > >> >> specify only parts of the html syntax... such as: > >> >> [removehtml comments] > >> >> > >> >> New SiteBuilder? > >> >> > >> >> code for Payment and Shipping Gateway API=E2=80=99s. > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> --------------------------------------------------------- > >> >> 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 > >> > > >> > > >> > > >> > -- > >> > Matthew A Perosi > >> > Corporate Consultant > >> > Mobile Marketing Expert > >> > Senior Web Developer > >> > SEO Analyst & Educator > >> > matt@psiprime.com > >> > > >> > Psi Prime, Inc. > >> > 323 Union Blvd. > >> > Totowa, NJ 07512 > >> > > >> > Direct: 888.872.0274 > >> > Fax: 888.488.5924 > >> > > >> > http://www.perosi.com > >> --------------------------------------------------------- > >> 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.u= s > > --------------------------------------------------------- > 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 > --089e0160b88e30ba51050cc93229 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi all,

I'm enjoying reading all th= e views here about WebDNA improvements, and I'm both grateful and impre= ssed by Christophe's commitment to keeping the language alive.

A few things I would like / agree with:

1= . [setcookie]
Ensure that it supports all possible options i.= e 'secure' and 'HttpOnly', though admittedly these can be s= et now using workarounds involving [setmimeheaders].

2. [grep]
A new [regex] that supports standard grep is = a great idea.

3. [setmimeheader]
<= div>(This may be fixed in latest versions) Ensure that all possible mime he= ader options are supported.

4. [sendmail]=
Add the ability to set the Return-Path

= 5. HTML Parser
The ability to properly parse HTML would be= incredibly useful.=C2=A0 Maybe a [tag] that uses one of the better HTML pa= rsers out there.

6. Cryptography
= Access to a wider set of cryptography tools so we can use current best prac= tice for secure salted password hashing (https://crackstation.net/hashing-security.htm).= =C2=A0 At the moment we have security through obscurity as the cryptography= used by [encrypt] has never been properly explained.


There are a number of other things that sho= uld be easier in WebDNA, these probably don't need new tags but just so= me tutorials showing the best practice in use out there:

1= . Cookie based login / authentication
The best method for coo= kie based username / password login (i.e. not realm based security). A lot = of us have implemented this, but it would be good to have a best practice g= uide.

2. Oauth Authentication
I s= till struggle when trying to use Oauth to access various API's. =C2=A0 = I usually manage to hack my way through each challenge, but again a best pr= actice would be great.

3. API Wrappers
WebDNA API wrappers for the most common / popular APIs, i.e. Twitter,= Facebook, MailChimp, Flickr, etc

4. Shell To= ols
An overview of how to use some of the most useful [shel= l] tools out there (I use imagemagick, wkhtmltopdf, ghostscript, and unocon= v)


Finally, and this m= ay over-complicate WebDNA, but I would love some way of easily defining dat= a types for WebDNA fields - similar to SQL data types. =C2=A0 I spend a lot= of time writing code that validates and checks data, if there was a way of= hard baking this that would be great.


<= div>Anyhow there's my thoughts.

Take care
- Tom










=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D
Digital Revolutionaries
1st Floor, Castleriver = House
14-15 Parliament Street
Temple Bar,Dublin 2
Ireland
-----= -----------------------------------------
[t]: + 353 1 4403907
[e]: &= lt;mailto:tom@r= evolutionaries.ie>
[w]: <http://www.revolutionaries.ie/>
=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

On 16 January 2015 at 14:00, <christophe.billiottet@webdna.us> wrote:
If we work on the [switch] cell to introduce the full set of= comparisons available with [showif], will you all still need the [elseif] = ?
I ask because if seems to me this is something missing with [switch] that s= hould have been there in the first place, but the [elseif] concept could sh= ow a little bit heavy and less elegant=E2=80=A6

- chris


> On 15 Jan 2015, at 20:58, iPhonzie@G <iphonzie@gmail.com> wrote:
>
> The do/while and repeat/until scenarios can be easily enough managed w= ith [loop], so that doesn=E2=80=99t bother me enough to need the additional= tags, but I would love to see [break] available in EVERY looping context -= founditems, listwords, formvariables, etc.
>
>
> [elseif] would be a great addition for situations where you have a num= ber of mutually exclusive conditions that are to complex for [switch]. I ha= ve lots of code that looks like this:
>
> [if (condition1)]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0[then]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0do stuff 1
>=C2=A0 =C2=A0 =C2=A0 =C2=A0[/then]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0[else]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0[if (condition2)= ]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0[then]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0do stuff 2
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0[/then]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0[else]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0[if (condition3)]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0[then]=
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0do stuff 3
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0[/then= ]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0[else]=
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0do default stuff
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0[/else= ]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0[/if]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0[/else]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0[/if]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0[/else]
> [/if]
>
> This would be much nicer if I could write:
>
> [if (condition1)]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0[then]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0do stuff 1
>=C2=A0 =C2=A0 =C2=A0 =C2=A0[/then]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0[elseif (condition2)]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0do stuff 2
>=C2=A0 =C2=A0 =C2=A0 =C2=A0[/elseif]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0[elseif (condition3)]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0do stuff 3
>=C2=A0 =C2=A0 =C2=A0 =C2=A0[/elseif]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0[else]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0do default stuff=
>=C2=A0 =C2=A0 =C2=A0 =C2=A0[/else]
> [/if]
>
>
> This could similarly be addressed with an alternative form of switch/c= ase. One possibility would be if no parameters are in the [switch] tag, the= n [if]-style comparisons could be put into each [case] tag:
>
> [switch]
> [case (condition1)]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0do stuff 1
> [/case]
> [case (condition2)]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0do stuff 2
> [/case]
> [case (condition3)]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0do stuff 3
> [/case]
> [default]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0do default stuff
> [/default]
> [/switch]
>
>
> =E2=80=94 Brian Fries
>
> On January 15, 2015 at 9:34:47 AM, Psi Prime Inc, Matthew A Perosi (matt@psiprime.com) wrote:
>
>> There have been plenty of time when I needed a [do]/[while] or a >> [repeat]/[until] statement.
>>
>> The [removehtml] needs to be improved to recognize the new format = for
>> HTML. Instead of removing HTML tags formatted like this:
>> <anything_between_here>
>> it needs to also recognize this new format like this:
>> <anything_between_here_followed_by_space_slash />
>>
>> Secure cookies are a good idea and I could use those too.
>>
>> -Matt
>>
>>
>> On 1/15/2015 11:23 AM, christophe.billiottet@webdna.us wrote:
>> > Some possible ideas; please explain specifically what you wan= t with "[elseif] to [if] context" and the [switch]
>> >
>> > The "commerce tags" are not supported anymore. Also= , PostGres is not on the roadmap at this time.
>> >
>> > You have had an opportunity earlier.
>> >
>> > - chris
>> >
>> >
>> >
>> >
>> >> On 15 Jan 2015, at 18:56, Donovan Brooke <dbrooke@euca.us> wrote:
>> >>
>> >> If resources are going to be put into development rather = than marketing, why not make some *standardized* improvements that will att= ract new users.
>> >> I=E2=80=99m talking about things that programmers look fo= r in a language.
>> >>
>> >> Off the top of my head:
>> >> [elseif] to [if] context.
>> >>
>> >> Database support, starting with PostGres
>> >> ie. [SQLConnect dbtype=3DPostGres]
>> >>
>> >> [sendmail] (local) override (instead of global server set= ting) of things like smtp port/auth, TLS settings, etc.. We already have th= e roadmap to make that local.
>> >>
>> >> [switch..] context with more comparison options.
>> >>
>> >> Add Md5 (and other newer encryption, digest, etc.) to enc= rypt..
>> >> for md5, just copy APOP. APOP is not very descriptive. >> >> [encrypt method=3Dmd5][/encrypt]
>> >>
>> >> secure param for setcookie
>> >>
>> >> Some other improvements off the top of my head:
>> >>
>> >> For the commerce tags (which, yes, they are still very us= eful):=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6..
>> >> [listHeaders][/listHeaders]
>> >> ie.:
>> >> [orderfile cart=3D[cart]]
>> >> [listHeaders name=3DAccountnum]
>> >> [name]=3D[value]<br>
>> >> [/listheaders]
>> >> [/orderfile]
>> >>
>> >> would produce:
>> >> accountnum=3D<thevalue>
>> >>
>> >> =3D=3D
>> >> Ability to set a flag to use a WebDNA Database with [orde= rfile] instead of the
>> >> order files that are created.
>> >>
>> >> =3D=3D
>> >> Ability to specify a unique ID within [addlineitems..], i= nstead of sku
>> >> [addlineitems uniqueID=3Dp_id&p_id=3DX&cart=3D[ca= rt]][/addlineitems]
>> >> =E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2= =80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80= =A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6= =E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6...
>> >>
>> >>
>> >> "Best Match" used in WebDNA Search system is mu= nged when using the Summ=3DT param. <=E2=80=94 I don=E2=80=99t think tha= t ever got fixed.
>> >>
>> >> Improvements to [removehtml]:
>> >> specify only parts of the html syntax... such as:
>> >> [removehtml comments]
>> >>
>> >> New SiteBuilder?
>> >>
>> >> code for Payment and Shipping Gateway API=E2=80=99s.
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> ---------------------------------------------------------=
>> >> This message is sent to you because you are subscribed to=
>> >> the mailing list <ta= lk@webdna.us>.
>> >> To unsubscribe, E-mail to: <talk-leave@webdna.us>
>> >> archives: http://mail.webdna.us/list/talk@webdna.us
>> >> Bug Reporting: suppo= rt@webdna.us
>> > ---------------------------------------------------------
>> > This message is sent to you because you are subscribed to
>> > the mailing list <talk@w= ebdna.us>.
>> > To unsubscribe, E-mail to: <talk-leave@webdna.us>
>> > archives: http://mail.webdna.us/list/talk@webdna.us
>> > Bug Reporting: support@w= ebdna.us
>> >
>> >
>> >
>> > --
>> > Matthew A Perosi
>> > Corporate Consultant
>> > Mobile Marketing Expert
>> > Senior Web Developer
>> > SEO Analyst & Educator
>> > matt@psiprime.com >> >
>> > Psi Prime, Inc.
>> > 323 Union Blvd.
>> > Totowa, NJ 07512
>> >
>> > Direct: 888.872.0274
>> > Fax: 888.488.5924
>> >
>> > http://ww= w.perosi.com
>> ---------------------------------------------------------
>> 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.us
>> Bug Reporting: support@webdna= .us
> --------------------------------------------------------- This message= is sent to you because you are subscribed to the mailing list . To unsubsc= ribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug R= eporting: support@webdna.us

---------------------------------------------------------
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

--089e0160b88e30ba51050cc93229-- Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] improvements (Stuart Tremain 2015)
  2. Re: [WebDNA] improvements (=?utf-8?Q?iPhonzie=40G?= 2015)
  3. Re: [WebDNA] improvements (Tom Duke 2015)
  4. Re: [WebDNA] improvements (christophe.billiottet@webdna.us 2015)
  5. Re: [WebDNA] improvements (Jym Duane 2015)
  6. Re: [WebDNA] improvements (christophe.billiottet@webdna.us 2015)
  7. Re: [WebDNA] improvements (=?utf-8?Q?iPhonzie=40G?= 2015)
  8. Re: [WebDNA] improvements (Brian Burton 2015)
  9. Re: [WebDNA] improvements (Dan Strong 2015)
  10. Re: [WebDNA] improvements (Stephen Reiss 2015)
  11. Re: [WebDNA] improvements (=?utf-8?Q?iPhonzie=40G?= 2015)
  12. Re: [WebDNA] improvements (Kenneth Grome 2015)
  13. Re: [WebDNA] improvements (Dan Strong 2015)
  14. Re: [WebDNA] improvements (Donovan Brooke 2015)
  15. Re: [WebDNA] improvements (Matthew Perosi 2015)
  16. Re: [WebDNA] improvements (Kenneth Grome 2015)
  17. Re: [WebDNA] improvements (=?utf-8?Q?iPhonzie=40G?= 2015)
  18. Re: [WebDNA] improvements ("Psi Prime Inc, Matthew A Perosi " 2015)
  19. Re: [WebDNA] improvements (christophe.billiottet@webdna.us 2015)
  20. [WebDNA] improvements (Donovan Brooke 2015)
--089e0160b88e30ba51050cc93229 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi all, I'm enjoying reading all the views here about WebDNA improvements, and I'm both grateful and impressed by Christophe's commitment to keeping the language alive. A few things I would like / agree with: *1. [setcookie]* Ensure that it supports all possible options i.e 'secure' and 'HttpOnly', though admittedly these can be set now using workarounds involving [setmimeheaders]. *2. [grep]* A new [regex] that supports standard grep is a great idea. *3. [setmimeheader]* (This may be fixed in latest versions) Ensure that all possible mime header options are supported. *4. [sendmail]* Add the ability to set the Return-Path *5. HTML Parser* The ability to properly parse HTML would be incredibly useful. Maybe a [tag] that uses one of the better HTML parsers out there. *6. Cryptography* Access to a wider set of cryptography tools so we can use current best practice for secure salted password hashing ( https://crackstation.net/hashing-security.htm). At the moment we have security through obscurity as the cryptography used by [encrypt] has never been properly explained. There are a number of other things that should be easier in WebDNA, these probably don't need new tags but just some tutorials showing the best practice in use out there: *1. Cookie based login / authentication* The best method for cookie based username / password login (i.e. not realm based security). A lot of us have implemented this, but it would be good to have a best practice guide. *2. Oauth Authentication* I still struggle when trying to use Oauth to access various API's. I usually manage to hack my way through each challenge, but again a best practice would be great. *3. API Wrappers* WebDNA API wrappers for the most common / popular APIs, i.e. Twitter, Facebook, MailChimp, Flickr, etc *4. Shell Tools* An overview of how to use some of the most useful [shell] tools out there (I use imagemagick, wkhtmltopdf, ghostscript, and unoconv) Finally, and this may over-complicate WebDNA, but I would love some way of easily defining data types for WebDNA fields - similar to SQL data types. I spend a lot of time writing code that validates and checks data, if there was a way of hard baking this that would be great. Anyhow there's my thoughts. Take care - Tom =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Digital Revolutionaries 1st Floor, Castleriver House 14-15 Parliament Street Temple Bar,Dublin 2 Ireland ---------------------------------------------- [t]: + 353 1 4403907 [e]: [w]: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D On 16 January 2015 at 14:00, wrote: > If we work on the [switch] cell to introduce the full set of comparisons > available with [showif], will you all still need the [elseif] ? > I ask because if seems to me this is something missing with [switch] that > should have been there in the first place, but the [elseif] concept could > show a little bit heavy and less elegant=E2=80=A6 > > - chris > > > > On 15 Jan 2015, at 20:58, iPhonzie@G wrote: > > > > The do/while and repeat/until scenarios can be easily enough managed > with [loop], so that doesn=E2=80=99t bother me enough to need the additio= nal tags, > but I would love to see [break] available in EVERY looping context - > founditems, listwords, formvariables, etc. > > > > > > [elseif] would be a great addition for situations where you have a > number of mutually exclusive conditions that are to complex for [switch].= I > have lots of code that looks like this: > > > > [if (condition1)] > > [then] > > do stuff 1 > > [/then] > > [else] > > [if (condition2)] > > [then] > > do stuff 2 > > [/then] > > [else] > > [if (condition3)] > > [then] > > do stuff 3 > > [/then] > > [else] > > do default stuff > > [/else] > > [/if] > > [/else] > > [/if] > > [/else] > > [/if] > > > > This would be much nicer if I could write: > > > > [if (condition1)] > > [then] > > do stuff 1 > > [/then] > > [elseif (condition2)] > > do stuff 2 > > [/elseif] > > [elseif (condition3)] > > do stuff 3 > > [/elseif] > > [else] > > do default stuff > > [/else] > > [/if] > > > > > > This could similarly be addressed with an alternative form of > switch/case. One possibility would be if no parameters are in the [switch= ] > tag, then [if]-style comparisons could be put into each [case] tag: > > > > [switch] > > [case (condition1)] > > do stuff 1 > > [/case] > > [case (condition2)] > > do stuff 2 > > [/case] > > [case (condition3)] > > do stuff 3 > > [/case] > > [default] > > do default stuff > > [/default] > > [/switch] > > > > > > =E2=80=94 Brian Fries > > > > On January 15, 2015 at 9:34:47 AM, Psi Prime Inc, Matthew A Perosi ( > matt@psiprime.com) wrote: > > > >> There have been plenty of time when I needed a [do]/[while] or a > >> [repeat]/[until] statement. > >> > >> The [removehtml] needs to be improved to recognize the new format for > >> HTML. Instead of removing HTML tags formatted like this: > >> > >> it needs to also recognize this new format like this: > >> > >> > >> Secure cookies are a good idea and I could use those too. > >> > >> -Matt > >> > >> > >> On 1/15/2015 11:23 AM, christophe.billiottet@webdna.us wrote: > >> > Some possible ideas; please explain specifically what you want with > "[elseif] to [if] context" and the [switch] > >> > > >> > The "commerce tags" are not supported anymore. Also, PostGres is not > on the roadmap at this time. > >> > > >> > You have had an opportunity earlier. > >> > > >> > - chris > >> > > >> > > >> > > >> > > >> >> On 15 Jan 2015, at 18:56, Donovan Brooke wrote: > >> >> > >> >> If resources are going to be put into development rather than > marketing, why not make some *standardized* improvements that will attrac= t > new users. > >> >> I=E2=80=99m talking about things that programmers look for in a lan= guage. > >> >> > >> >> Off the top of my head: > >> >> [elseif] to [if] context. > >> >> > >> >> Database support, starting with PostGres > >> >> ie. [SQLConnect dbtype=3DPostGres] > >> >> > >> >> [sendmail] (local) override (instead of global server setting) of > things like smtp port/auth, TLS settings, etc.. We already have the roadm= ap > to make that local. > >> >> > >> >> [switch..] context with more comparison options. > >> >> > >> >> Add Md5 (and other newer encryption, digest, etc.) to encrypt.. > >> >> for md5, just copy APOP. APOP is not very descriptive. > >> >> [encrypt method=3Dmd5][/encrypt] > >> >> > >> >> secure param for setcookie > >> >> > >> >> Some other improvements off the top of my head: > >> >> > >> >> For the commerce tags (which, yes, they are still very > useful):=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6.. > >> >> [listHeaders][/listHeaders] > >> >> ie.: > >> >> [orderfile cart=3D[cart]] > >> >> [listHeaders name=3DAccountnum] > >> >> [name]=3D[value]
> >> >> [/listheaders] > >> >> [/orderfile] > >> >> > >> >> would produce: > >> >> accountnum=3D > >> >> > >> >> =3D=3D > >> >> Ability to set a flag to use a WebDNA Database with [orderfile] > instead of the > >> >> order files that are created. > >> >> > >> >> =3D=3D > >> >> Ability to specify a unique ID within [addlineitems..], instead of > sku > >> >> [addlineitems uniqueID=3Dp_id&p_id=3DX&cart=3D[cart]][/addlineitems= ] > >> >> =E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2= =80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80= =A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6= =E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6... > >> >> > >> >> > >> >> "Best Match" used in WebDNA Search system is munged when using the > Summ=3DT param. <=E2=80=94 I don=E2=80=99t think that ever got fixed. > >> >> > >> >> Improvements to [removehtml]: > >> >> specify only parts of the html syntax... such as: > >> >> [removehtml comments] > >> >> > >> >> New SiteBuilder? > >> >> > >> >> code for Payment and Shipping Gateway API=E2=80=99s. > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> --------------------------------------------------------- > >> >> 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 > >> > > >> > > >> > > >> > -- > >> > Matthew A Perosi > >> > Corporate Consultant > >> > Mobile Marketing Expert > >> > Senior Web Developer > >> > SEO Analyst & Educator > >> > matt@psiprime.com > >> > > >> > Psi Prime, Inc. > >> > 323 Union Blvd. > >> > Totowa, NJ 07512 > >> > > >> > Direct: 888.872.0274 > >> > Fax: 888.488.5924 > >> > > >> > http://www.perosi.com > >> --------------------------------------------------------- > >> 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.u= s > > --------------------------------------------------------- > 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 > --089e0160b88e30ba51050cc93229 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi all,

I'm enjoying reading all th= e views here about WebDNA improvements, and I'm both grateful and impre= ssed by Christophe's commitment to keeping the language alive.

A few things I would like / agree with:

1= . [setcookie]
Ensure that it supports all possible options i.= e 'secure' and 'HttpOnly', though admittedly these can be s= et now using workarounds involving [setmimeheaders].

2. [grep]
A new [regex] that supports standard grep is = a great idea.

<= div>(This may be fixed in latest versions) Ensure that all possible mime he= ader options are supported.

4. [sendmail]=
Add the ability to set the Return-Path

= 5. HTML Parser
The ability to properly parse HTML would be= incredibly useful.=C2=A0 Maybe a [tag] that uses one of the better HTML pa= rsers out there.

6. Cryptography
= Access to a wider set of cryptography tools so we can use current best prac= tice for secure salted password hashing (https://crackstation.net/hashing-security.htm).= =C2=A0 At the moment we have security through obscurity as the cryptography= used by [encrypt] has never been properly explained.


There are a number of other things that sho= uld be easier in WebDNA, these probably don't need new tags but just so= me tutorials showing the best practice in use out there:

1= . Cookie based login / authentication
The best method for coo= kie based username / password login (i.e. not realm based security). A lot = of us have implemented this, but it would be good to have a best practice g= uide.

2. Oauth Authentication
I s= till struggle when trying to use Oauth to access various API's. =C2=A0 = I usually manage to hack my way through each challenge, but again a best pr= actice would be great.

3. API Wrappers
WebDNA API wrappers for the most common / popular APIs, i.e. Twitter,= Facebook, MailChimp, Flickr, etc

4. Shell To= ols
An overview of how to use some of the most useful [shel= l] tools out there (I use imagemagick, wkhtmltopdf, ghostscript, and unocon= v)


Finally, and this m= ay over-complicate WebDNA, but I would love some way of easily defining dat= a types for WebDNA fields - similar to SQL data types. =C2=A0 I spend a lot= of time writing code that validates and checks data, if there was a way of= hard baking this that would be great.


<= div>Anyhow there's my thoughts.

Take care
- Tom










=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D
Digital Revolutionaries
1st Floor, Castleriver = House
14-15 Parliament Street
Temple Bar,Dublin 2
Ireland
-----= -----------------------------------------
[t]: + 353 1 4403907
[e]: &= lt;mailto:tom@r= evolutionaries.ie>
[w]: <http://www.revolutionaries.ie/>
=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

On 16 January 2015 at 14:00, <christophe.billiottet@webdna.us> wrote:
If we work on the [switch] cell to introduce the full set of= comparisons available with [showif], will you all still need the [elseif] = ?
I ask because if seems to me this is something missing with [switch] that s= hould have been there in the first place, but the [elseif] concept could sh= ow a little bit heavy and less elegant=E2=80=A6

- chris


> On 15 Jan 2015, at 20:58, iPhonzie@G <iphonzie@gmail.com> wrote:
>
> The do/while and repeat/until scenarios can be easily enough managed w= ith [loop], so that doesn=E2=80=99t bother me enough to need the additional= tags, but I would love to see [break] available in EVERY looping context -= founditems, listwords, formvariables, etc.
>
>
> [elseif] would be a great addition for situations where you have a num= ber of mutually exclusive conditions that are to complex for [switch]. I ha= ve lots of code that looks like this:
>
> [if (condition1)]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0[then]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0do stuff 1
>=C2=A0 =C2=A0 =C2=A0 =C2=A0[/then]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0[else]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0[if (condition2)= ]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0[then]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0do stuff 2
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0[/then]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0[else]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0[if (condition3)]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0[then]=
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0do stuff 3
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0[/then= ]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0[else]=
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0do default stuff
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0[/else= ]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0[/if]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0[/else]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0[/if]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0[/else]
> [/if]
>
> This would be much nicer if I could write:
>
> [if (condition1)]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0[then]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0do stuff 1
>=C2=A0 =C2=A0 =C2=A0 =C2=A0[/then]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0[elseif (condition2)]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0do stuff 2
>=C2=A0 =C2=A0 =C2=A0 =C2=A0[/elseif]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0[elseif (condition3)]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0do stuff 3
>=C2=A0 =C2=A0 =C2=A0 =C2=A0[/elseif]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0[else]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0do default stuff=
>=C2=A0 =C2=A0 =C2=A0 =C2=A0[/else]
> [/if]
>
>
> This could similarly be addressed with an alternative form of switch/c= ase. One possibility would be if no parameters are in the [switch] tag, the= n [if]-style comparisons could be put into each [case] tag:
>
> [switch]
> [case (condition1)]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0do stuff 1
> [/case]
> [case (condition2)]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0do stuff 2
> [/case]
> [case (condition3)]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0do stuff 3
> [/case]
> [default]
>=C2=A0 =C2=A0 =C2=A0 =C2=A0do default stuff
> [/default]
> [/switch]
>
>
> =E2=80=94 Brian Fries
>
> On January 15, 2015 at 9:34:47 AM, Psi Prime Inc, Matthew A Perosi (matt@psiprime.com) wrote:
>
>> There have been plenty of time when I needed a [do]/[while] or a >> [repeat]/[until] statement.
>>
>> The [removehtml] needs to be improved to recognize the new format = for
>> HTML. Instead of removing HTML tags formatted like this:
>> <anything_between_here>
>> it needs to also recognize this new format like this:
>> <anything_between_here_followed_by_space_slash />
>>
>> Secure cookies are a good idea and I could use those too.
>>
>> -Matt
>>
>>
>> On 1/15/2015 11:23 AM, christophe.billiottet@webdna.us wrote:
>> > Some possible ideas; please explain specifically what you wan= t with "[elseif] to [if] context" and the [switch]
>> >
>> > The "commerce tags" are not supported anymore. Also= , PostGres is not on the roadmap at this time.
>> >
>> > You have had an opportunity earlier.
>> >
>> > - chris
>> >
>> >
>> >
>> >
>> >> On 15 Jan 2015, at 18:56, Donovan Brooke <dbrooke@euca.us> wrote:
>> >>
>> >> If resources are going to be put into development rather = than marketing, why not make some *standardized* improvements that will att= ract new users.
>> >> I=E2=80=99m talking about things that programmers look fo= r in a language.
>> >>
>> >> Off the top of my head:
>> >> [elseif] to [if] context.
>> >>
>> >> Database support, starting with PostGres
>> >> ie. [SQLConnect dbtype=3DPostGres]
>> >>
>> >> [sendmail] (local) override (instead of global server set= ting) of things like smtp port/auth, TLS settings, etc.. We already have th= e roadmap to make that local.
>> >>
>> >> [switch..] context with more comparison options.
>> >>
>> >> Add Md5 (and other newer encryption, digest, etc.) to enc= rypt..
>> >> for md5, just copy APOP. APOP is not very descriptive. >> >> [encrypt method=3Dmd5][/encrypt]
>> >>
>> >> secure param for setcookie
>> >>
>> >> Some other improvements off the top of my head:
>> >>
>> >> For the commerce tags (which, yes, they are still very us= eful):=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6..
>> >> [listHeaders][/listHeaders]
>> >> ie.:
>> >> [orderfile cart=3D[cart]]
>> >> [listHeaders name=3DAccountnum]
>> >> [name]=3D[value]<br>
>> >> [/listheaders]
>> >> [/orderfile]
>> >>
>> >> would produce:
>> >> accountnum=3D<thevalue>
>> >>
>> >> =3D=3D
>> >> Ability to set a flag to use a WebDNA Database with [orde= rfile] instead of the
>> >> order files that are created.
>> >>
>> >> =3D=3D
>> >> Ability to specify a unique ID within [addlineitems..], i= nstead of sku
>> >> [addlineitems uniqueID=3Dp_id&p_id=3DX&cart=3D[ca= rt]][/addlineitems]
>> >> =E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2= =80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80= =A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6= =E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6=E2=80=A6...
>> >>
>> >>
>> >> "Best Match" used in WebDNA Search system is mu= nged when using the Summ=3DT param. <=E2=80=94 I don=E2=80=99t think tha= t ever got fixed.
>> >>
>> >> Improvements to [removehtml]:
>> >> specify only parts of the html syntax... such as:
>> >> [removehtml comments]
>> >>
>> >> New SiteBuilder?
>> >>
>> >> code for Payment and Shipping Gateway API=E2=80=99s.
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> ---------------------------------------------------------=
>> >> This message is sent to you because you are subscribed to=
>> >> the mailing list <ta= lk@webdna.us>.
>> >> To unsubscribe, E-mail to: <talk-leave@webdna.us>
>> >> archives: http://mail.webdna.us/list/talk@webdna.us
>> >> Bug Reporting: suppo= rt@webdna.us
>> > ---------------------------------------------------------
>> > This message is sent to you because you are subscribed to
>> > the mailing list <talk@w= ebdna.us>.
>> > To unsubscribe, E-mail to: <talk-leave@webdna.us>
>> > archives: http://mail.webdna.us/list/talk@webdna.us
>> > Bug Reporting: support@w= ebdna.us
>> >
>> >
>> >
>> > --
>> > Matthew A Perosi
>> > Corporate Consultant
>> > Mobile Marketing Expert
>> > Senior Web Developer
>> > SEO Analyst & Educator
>> > matt@psiprime.com >> >
>> > Psi Prime, Inc.
>> > 323 Union Blvd.
>> > Totowa, NJ 07512
>> >
>> > Direct: 888.872.0274
>> > Fax: 888.488.5924
>> >
>> > http://ww= w.perosi.com
>> ---------------------------------------------------------
>> 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.us
>> Bug Reporting: support@webdna= .us
> --------------------------------------------------------- This message= is sent to you because you are subscribed to the mailing list . To unsubsc= ribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug R= eporting: support@webdna.us

---------------------------------------------------------
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

--089e0160b88e30ba51050cc93229-- Tom Duke

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:

WebCat 2.1.3 (and docs) (1998) Not really WebCat - need HTML Grider (1997) help (2001) PCS Frames (1997) Wierd problem with 3.08 WIN Version (2000) Re:PCS Customer submissions ? (1997) Separate SSL Server (1997) PCS Frames (1997) problems with 2 tags (1997) database size? (1997) all records returned. (1997) Protecting Images (2003) Keep away (1997) 2.01 upgrade problems (1997) Color (1997) Limit to variables passed on to next tpl? (1998) SiteGuard Admin Feature ? (1997) Credit Card Verification.... (1998) Add to a field (1998) 2.0 Info (1997)