Re: [WebDNA] First-timer feedback

This WebDNA talk-list message is from

2014

It keeps the original formatting. numero = 111511
interpreted = N
texte = This is a multi-part message in MIME format.--------------040108030408070109070208Content-Type: text/plain; charset=UTF-8; format=flowedContent-Transfer-Encoding: 8bitA few notes in-line below:On 8/4/2014 10:16 AM, Dan Strong wrote:>> I've begun teaching some php/CF/other-languages-savvy developers > WebDNA and had them do a test project. I thought you'd find their > feedback interesting.>> Obviously some things they just need to be shown how to do in WebDNA, > but overall this is some good feedback.>> 1. No session support: We must use cookies and built-in db instead.>> 2. No JSON object (encode/decode) support>> 3. Some limitations in File Handling: No absolutely path support, only > relative paths are supported.>> 4. Db Connections are limited.>> 5. Language syntax is limited, so it is hard to implement some algorithms.>> 6. Not easy to debug, lacks editor/debug support>> 7. Built-in db has poor performance (poor query language : NO group, > sum... etc).>> 8. Array object is much more limited than Array objects in Python and PHP>> 9. Seems that it does not support object model, and its concepts are > not similar to other common scripting languages.>It's a mark-up language like HTML. Object-Oriented is not always better. There are ways around this by dynamically naming variables (i.e. Variable variables in PHP - $$txtVar;).> 10. Does not support WHILE loop>[break] works inside any [loop] to accomplish the same thing as a "do... while" or "do... until". If I'm not mistaken, it works inside [founditems], also. (Can't test because I'm fighting with Windows 7 right now to set up a dev instance.)>> 11. No reading of text files (or not yet found the way)>I swear I did this on a project 10+ years ago in v6.x, but I don't remember exactly how I did it. It might have been [text show=f]txtVariable=[include file=file.ext&raw=T][/text] I used it to pull the text information out of jpgs.>> 12. No support for CURL, so working with web services can be a problem.>> 13. There is some special handles with “\ln” character while WebDNA > works with HTML….>> ------------------------------------> Sent from phone>> -Dan Strong> http://DanStrong.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 --------------040108030408070109070208Content-Type: text/html; charset=UTF-8Content-Transfer-Encoding: 8bit A few notes in-line below:

On 8/4/2014 10:16 AM, Dan Strong wrote:

I've begun teaching some php/CF/other-languages-savvy developers WebDNA and had them do a test project. I thought you'd find their feedback interesting.

Obviously some things they just need to be shown how to do in WebDNA, but overall this is some good feedback.

1. No session support: We must use cookies and built-in db instead.

2. No JSON object (encode/decode) support

3. Some limitations in File Handling: No absolutely path support, only relative paths are supported.

4. Db Connections are limited.

5. Language syntax is limited, so it is hard to implement some algorithms.

6. Not easy to debug, lacks editor/debug support

7. Built-in db has poor performance (poor query language : NO group, sum... etc).

8. Array object is much more limited than Array objects in Python and PHP

9. Seems that it does not support object model, and its concepts are not similar to other common scripting languages.

It's a mark-up language like HTML. Object-Oriented is not always better. There are ways around this by dynamically naming variables (i.e. Variable variables in PHP - $$txtVar;).

10. Does not support WHILE loop

[break] works inside any [loop] to accomplish the same thing as a "do... while" or "do... until". If I'm not mistaken, it works inside [founditems], also. (Can't test because I'm fighting with Windows 7 right now to set up a dev instance.)

11. No reading of text files (or not yet found the way)

I swear I did this on a project 10+ years ago in v6.x, but I don't remember exactly how I did it. It might have been [text show=f]txtVariable=[include file=file.ext&raw=T][/text] I used it to pull the text information out of jpgs.

12. No support for CURL, so working with web services can be a problem.

13. There is some special handles with “\ln” character while WebDNA works with HTML….<captured to avoid this issues next times>

------------------------------------
Sent from phone

-Dan Strong
http://DanStrong.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
--------------040108030408070109070208-- Associated Messages, from the most recent to the oldest:

Re: [WebDNA] First-timer feedback (Dan Strong 2014)
Re: [WebDNA] First-timer feedback (Stuart Tremain 2014)
Re: [WebDNA] First-timer feedback (Dan Strong 2014)
Re: [WebDNA] First-timer feedback (Donovan Brooke 2014)
Re: [WebDNA] First-timer feedback (Matthew Bohne 2014)
[WebDNA] First-timer feedback (Dan Strong 2014)

This is a multi-part message in MIME format.--------------040108030408070109070208Content-Type: text/plain; charset=UTF-8; format=flowedContent-Transfer-Encoding: 8bitA few notes in-line below:On 8/4/2014 10:16 AM, Dan Strong wrote:>> I've begun teaching some php/CF/other-languages-savvy developers > WebDNA and had them do a test project. I thought you'd find their > feedback interesting.>> Obviously some things they just need to be shown how to do in WebDNA, > but overall this is some good feedback.>> 1. No session support: We must use cookies and built-in db instead.>> 2. No JSON object (encode/decode) support>> 3. Some limitations in File Handling: No absolutely path support, only > relative paths are supported.>> 4. Db Connections are limited.>> 5. Language syntax is limited, so it is hard to implement some algorithms.>> 6. Not easy to debug, lacks editor/debug support>> 7. Built-in db has poor performance (poor query language : NO group, > sum... etc).>> 8. Array object is much more limited than Array objects in Python and PHP>> 9. Seems that it does not support object model, and its concepts are > not similar to other common scripting languages.>It's a mark-up language like HTML. Object-Oriented is not always better. There are ways around this by dynamically naming variables (i.e. Variable variables in PHP - $$txtVar;).> 10. Does not support WHILE loop>[break] works inside any [loop] to accomplish the same thing as a "do... while" or "do... until". If I'm not mistaken, it works inside [founditems], also. (Can't test because I'm fighting with Windows 7 right now to set up a dev instance.)>> 11. No reading of text files (or not yet found the way)>I swear I did this on a project 10+ years ago in v6.x, but I don't remember exactly how I did it. It might have been [text show=f]txtVariable=[include file=file.ext&raw=T][/text] I used it to pull the text information out of jpgs.>> 12. No support for CURL, so working with web services can be a problem.>> 13. There is some special handles with “\ln” character while WebDNA > works with HTML….>> ------------------------------------> Sent from phone>> -Dan Strong> http://DanStrong.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 --------------040108030408070109070208Content-Type: text/html; charset=UTF-8Content-Transfer-Encoding: 8bit A few notes in-line below:

On 8/4/2014 10:16 AM, Dan Strong wrote: