Shamil Salakhetdinov
shamil at smsconsulting.spb.ru
Wed Apr 13 14:35:07 CDT 2011
Hi Doug, Not at all - in fact that was Ken who posted that link here: <<< Also, I use Crockford's Javascript Lint, http://www.jslint.com/, which promises to 'hurt your feelings'. But, it has never hurt mine, mainly because it has rescued my crappy, non-working Javacript code too many times. >>> Thank you. -- Shamil -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Doug Murphy Sent: 13 ?????? 2011 ?. 22:37 To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Libraries and Frameworks [Was: AccessD Digest, Vol 98,Issue 7] Shamil, Thank you for the reference to the javascript checker. I just ran some of my code through this. The result wasn't pretty, but it was informative. I'll keep this link. Doug -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Shamil Salakhetdinov Sent: Wednesday, April 13, 2011 6:25 AM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Libraries and Frameworks [Was: AccessD Digest, Vol 98, Issue 7] Hi Ken -- <<< If you haven't run into it yet, I would recommend Douglas Crockford's book "Javascript: the Good Parts", which very efficiently shows what to do and what to avoid. Also, I use Crockford's Javascript Lint, http://www.jslint.com/, which promises to 'hurt your feelings'. But, it has never hurt mine, mainly because it has rescued my crappy, non-working Javacript code too many times. >>> Thank you I jave got bookmarked both book and the site... <<< Right now, I do the most brutally simple testing possible -- if I have a library module 'MFoo', I have a test module called 'testMFoo', with 'test' functions that exercise like-named MFoo functions. I just run the code by hand. I don't have perfect test coverage, either. I'm not sure how or if I will automate it, but I suppose I could loop through all of the 'test*' modules, run each of the 'test*' functions, and log the results. >>> Yes, that's one of the options how to run your test code.... Thank you. -- Shamil -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Kenneth Ismert Sent: 13 ?????? 2011 ?. 0:12 To: accessd at databaseadvisors.com Subject: Re: [AccessD] Libraries and Frameworks [Was: AccessD Digest, Vol 98,Issue 7] All, <<< skip>>> Javascript is Prototype-based, which is a simpler (but still enormously useful) object paradigm. If you haven't run into it yet, I would recommend Douglas Crockford's book "Javascript: the Good Parts", which very efficiently shows what to do and what to avoid. Also, I use Crockford's Javascript Lint, http://www.jslint.com/, which promises to 'hurt your feelings'. But, it has never hurt mine, mainly because it has rescued my crappy, non-working Javacript code too many times. <<< skip >>> -Ken --