On Tuesday June 9th, the Appcelerator team will be throwing a product launch party at Apple’s World Wide Developer Conference to toast the arrival of Titanium Beta. If you are going to be at the WWDC head over to Jillian’s in San Francisco between 6 and 9 p.m. where they will unveil Titanium Beta.
Please update your RSS and ATOM feeds to this site. I recently discovered a small error with my back-end code that was allowing erroneous links to appear for my RSS and ATOM feeds. These bad links will work until the end of the summer at which time I will remove them and only be updating the proper links.
In attempts to make my JavaScript applications better, I frequently use Douglas Crockford's JavaScript verifier application JSLint. If you have never used JSLint, I would advise reviewing the background on JSLint
In order to use it more easily and efficiently on local files, I took the JSLint JS file and ported it to an Adobe AIR application for the desktop. You can import the file from your desktop or paste the code in directly. In a future edition, I will add drag and drop ability to JS files. I used jQuery UI for the app UI and plan to eventually add skin choices to the options menu base on jQuery UI default skins. The app will auto update, so you will be able to see new features as soon as I add them if you accept the updates.
Many newcomers to web development may not be used to how web implementations of JavaScript execute. Namely, in what order it executes. This can be the source of many errors that are difficult to pinpoint if you aren't experienced with it. I think this also affects people who are very experienced with other programming languages and fosters a lot of undeserved hate towards ActionScript and JavaScript. (It's important to note that not all implementations of JavaScript are the same, and that some may in fact defer from what is said below. This article concerns browser and Flash based ECMAScript.)
The thing to understand about JavaScript is that it isn't compiled for the most part. (This is not exactly true for ActionScript because of the introduction of classes in ActionScript 2.0, however, the runtime script remains the same. You might argue that it compiles into a *.swf file, but in reality, that is the combination of everything that has to do with the Flash file. The ActionScript still remains live.) It's good that it isn't compiled though, because this allows for much more dynamic, expressive coding.
In JavaScript the typeof operator reports an array as 'object'. While this is technically correct (an array in JavaScript is really just a specialized object), it's a pain in the neck when you are type checking a variable.
There are a number of ways to identify an array in JavaScript. Checking for properties of an array isn't totally accurate because you can add any named member to an object to imitate an array. Checking for 'instanceof Array' works most of the time but could be tricky in some implementations of JavaScript.
When using multiple JavaScript libraries, it is inevitable that one JavaScript file will need to call functions named in other libraries. This is necessary but can cause issues if all of the libraries aren't present.
Error handling with JavaScript is somewhat lackluster. With this in mind, you should do your best to catch and handle errors and avoid sending them to the end-user. In order to prevent errors and allow for scalability, you should test for functions that aren't present in the script where you are calling them.
Page 1 of 4 pages 1 2 3 > Last »