Eric Feminella

AT&T Best Practices Guide for App Development

eric — Sun, 15 Jan 2012 11:00:20 +0000

When considering the various best practices surrounding the design of Mobile Web Experiences and Architectures, such works as the W3C’s Mobile Web Application Best Practices guide, or the excellent Mobile Web Best Practices site, and of course, the seminal text, Mobile First, are likely to come to mind. The concepts and strategies presented in these works are a staple in the design of many modern Mobile Web Experiences and are without question an invaluable resource. In addition to these and other similarly related works, another new and valuable resource has been made available from a very important player in the Mobile Space indeed – an actual Wireless Carrier, AT&T.

Recently, I was contacted by a representative of the AT&T Developer Program informing me of the research conducted by the AT&T Research Labs and, the subsequent resources made available by AT&T as a result of their findings. Since I was unaware of this work, I was very interesting in learning more and, after reading the introductory statements, I was quite eager to apply AT&T’s recommendations as well; to quote specifically:

We quickly saw that a few, simple design approaches could significantly improve application responsiveness.

Having read through the material in it’s entirety (provided below) I must say I am rather impressed. The information provided has very real and practical implications on the design of Mobile Web Applications. Specifically, I found the clear and concise explanation of the underlying implementation of the Radio Resource Control (RRC) protocol to be particularly relevant and useful. RRC is by far one of the most important design factors to consider in terms of battery life and Application responsiveness and, as the research suggests, this may not have been common knowledge.

By far, the most interesting and notable aspect of the AT&T Research Lab’s work in this area is the fact that all of the information provided is applicable in the context of all Wireless Carriers, not just AT&T. That is, the recommendations given, such as those regarding the RRC State Machine, for example, are all based on carrier-independent standards and protocols implemented by all Wireless Carriers. As such, understanding the implementation specifics and recommendations provided is certain to prove valuable for all users of your Application, regardless of their Carrier.

If you haven’t all ready, I highly recommend reading and applying the principles provided by AT&T’s research to your current and future Mobile Web Application Designs.

AT&T Research Labs: Mobile Application Resources

Build Efficient Apps
Profiling Resource Usage for Mobile Applications: A Cross-layer Approach

Configuring iOS HTTP Monitoring

eric — Sat, 17 Dec 2011 02:04:29 +0000

When developing Web Applications for the Mobile Web Experience it is often useful to have a clear view into all HTTP requests and responses sent between the client and server. This is quite simple to accomplish when developing Web Applications for the Desktop as, the browser is running locally so any standard HTTP Monitor will suffice. And, while it is a normal part of a typical development workflow to run an application locally the majority of the time, testing on each target device is obviously an essential part of the process as well.

Luckily, with Charles, on iOS this is quite simple to accomplish.

Configuration

To configure Charles to proxy all requests from an iOS device, simply follow these basic steps:

From your iOS Device, open Settings.
Go to Wi-Fi, select your Network and select the Blue “arrow” icon.
Scroll to HTTP Proxy and select the Manual Button.
In the Server field, enter the IP address of your development machine.
In the port field, enter port 8888 (the default port to which Charles binds).
Leave Authentication set to Off.

And that’s all there is to it. Now, open Mobile Safari and go to your Web Application’s URL (or any page on the web for that matter). On your development machine, in Charles you will receive a prompt with the IP Address of your Mobile Device, click “Allow” and you are all set. When you are done working, make sure to turn off HTTP Proxy on your device.

Additional Note

While this article may be focused on Mobile Web Applications, these same configurations apply to all HTTP traffic from any application on your device that requires resources over the web.

External Templates in jQote2

eric — Mon, 12 Dec 2011 12:00:56 +0000

The jQote2 API Reference provides plenty of useful examples which are sure to help users get up and running quickly. I found it a bit unclear, though, as to how templates could be loaded externally as, in the reference examples, templates are defined within the containing page. For the sake of simplicity this approach certainly makes sense in the context of examples. However, in practice, templates would ideally be loaded externally.

While jQote2 provides a perfect API for templating, it does not provide a method specifically for loading external templates; this is likely due to the fact that loading external templates could easily be accomplished natively in jQuery. However, since this is a rather common development use case, having such a facility available would be quite useful.

After reviewing the comments I came across a nice example from aefxx (the author of jQote2) which demonstrated a typical approach to loading external templates which was simular to what I had been implementing myself.

And so, I wrote a simple jQuery Plug-in which provides a tested, reusable solution to loading external templates. After having leveraged the Plugin on quite a few different projects, I decided to open source it as others may find it useful as well.

You can grab the source and view the example over on the jQote2 Template Loader Github page.

DHTMLX Touch 1.0 Released

eric — Wed, 23 Nov 2011 13:31:56 +0000

Last week, shortly after I blogged about the release of jQuery Mobile 1.0, I received an email informing me of the release of another Mobile Web Framework: DHTMLX Touch 1.0.

Being that I was unfamiliar with DHTMLX Touch (as I have been using jQuery Mobile almost exclusively), I was quite interested to learn more; and, having tried the Examples and reviewed the Documentation, I was rather impressed by DHTMLX Touch.

And so, if you haven’t already, check it out.

Function Overwriting in JavaScript

eric — Sat, 19 Nov 2011 19:45:40 +0000

Whether intentional, or simply a by-product of it’s design, Javascript, being a dynamic language, allows for a level of expressiveness which most any seasoned programmer would come to appreciate. Javascript naturally provides the ability to implement some rather intriguing and quite unique patterns; one of which is the ability to overwrite a function at runtime.

Function Overwriting

Function Overwriting (also known as “Self-Defining Functions” or “Lazy Defining Functions”) provides a pattern which, as stated above, allows for overwriting a function’s definition at runtime. This can be accomplished from outside of the function, but also from within the function’s implementation itself.

For example, on occasion a function may need to perform some initial piece of work, after which, all subsequent invocations would result in unnecessarily re-executing the initialization code. Typically, this issue is addressed by storing initialization flags or refactoring the initialization code to another function. While such a design solves this problem, it does result in unnecessary code which will need to be maintained. In JavaScript, perhaps a different approach is in order: we can simply redefine the function after the initialization work has been completed.

A possible candidate use-case for Function Overwriting is Feature Detection as, detecting for specific feature support in the Browser typically only needs to be tested once, at which point subsequent tests are unnecessary.

Below is a basic example of implementing Function Overwritting in the context of an abstraction of the HTML5 Geolocation API.

// Initial "getLocation" implementation. Since we only need to test
// for Geolocation support once, we perform the initial test and then
// overwrite the "getLocation" implementation based on the results of
// the test.
var getLocation = function ( success, fail, options )
{
var geolocation = navigator.geolocation;

if ( geolocation )
{
var _options = {
enableHighAccuracy : true,
timeout : 60000,
maximumAge : 0
};
// Geolocation is supported, so we overwrite the implementation
// to simply invoke "geolocation.getCurrentPosition" as there
// is no need to perform the test again.
getLocation = function (success, fail, options)
{
geolocation.getCurrentPosition ( success,
fail,
options || _options);
}
getLocation( success, fail, options );
}
else
{
// Geolocation is not supported, so we overwrite the
// implementation to simply return false (a real
// implementation might provide a polyfill here…).
getLocation = function ()
{
return false;
}
}
};

Considerations

Since functions are objects in Javascript, it is important to keep in mind that if you add a property or method to a function (either statically or via the function’s prototype), and then overwrite the function, you will have effectively removed those properties or methods as well. Also, if the function is referenced by another variable, or by a method of another object, the initially defined implementation will be preserved and the overwriting process will not occur. As such, be mindful when implementing this pattern. As a general rule of thumb, I typically only implement Function Overwriting when the function being redefined is in a private scope.

Concluding Thoughts

As you can see, Function Overwriting provides a convenient facility for optimizing code execution at runtime. There are many use-cases for dynamically overwriting functions and, where appropriate, they can certainly provide value in terms of performance and code maintainability.

Below you can find an example which demonstrates two basic Function Overwriting implementations. Simply load the page and add some breakpoints in Firebug to test the execution paths; both before and after overwriting each function occurs, or you can simply view the source.
Example

Refreshing listviews in jQuery Mobile

eric — Sat, 19 Nov 2011 03:42:01 +0000

When dynamically creating or updating a list in jQuery Mobile; either via AJAX or by other means, one must take care to explicitly invoke the target listview widget to “refresh” in order to instruct the framework to apply the augmented markup and styles to the corresponding elements of the underlying list.

For example, consider the following simplified example which creates an li element for each item in an Array:

var list = "",
items = [{name: "Item A", url: "/#item-a"},
{name: "Item B", url: "/#item-b"},
{name: "Item C", url: "/#item-c"}];

$.each( items, function( i, item ) {
list += ‘

item.url + ‘">’ + item.name +‘

’;
});
$("ul:jqmData(role=’listview’)").append( list );

While this will create the list items and add them to the target listview ul element, JQM will not auto enhance the newly added items unless instructed to do so. I imagine this is due to a necessary design decision as, constantly monitoring the DOM for changes would certainly incur a performance hit.

In order to correct this, we just need to invoke .listview("refresh"); after appending the new elements to the list. This will notify JQM to apply the expected enhancements. And so, the following example will result in the expected list enhancements being applied:

var list = "",
items = [{name: "Item A", url: "/#item-a"},
{name: "Item B", url: "/#item-b"},
{name: "Item C", url: "/#item-c"}];

$.each( items, function( i, item ) {
list += ‘

item.url + ‘">’ + item.name +‘

’;
});
$("ul:jqmData(role=’listview’)").append( list ).listview("refresh");

You can try an example which demonstrates both of the above implementations here.

jQuery Mobile 1.0 Released

eric — Thu, 17 Nov 2011 16:45:20 +0000

Today, the jQuery Mobile Team announced the official release of jQuery Mobile 1.0.

Having worked with jQuery Mobile since Alpha 1, in the time since, the framework has certainly evolved into a mature, premier platform on which Mobile Web Applications can be built.

On a personal note, as I am currently in the process of working towards the release of a multi form-factor Mobile Web Application built on jQuery Mobile, the 1.0 release couldn’t have come at a better time.

Be sure to check out the updated API Docs, especially the new Data Attributes section.

jQuery Mobile 1.0 represents a significant milestone in the Mobile Web Space. I am certainly excited to see what is on the roadmap next.

CSS3 Combinators

eric — Sun, 13 Nov 2011 11:51:52 +0000

In my previous article on CSS3 Selectors, I discussed the two Attribute Selector classifications; Attribute Presence and Value Selectors, and, Attribute Substring Matching Selectors.

In addition to the new Attribute Selectors, the CSS3 Selectors Module defines a new Combinator called the General sibling combinator, which is described below, succeeding a review of each CSS3 Combinator.

Combinators

Combinators provide a means for describing relationships between elements in order to “combine” them to form specific rules based on a simple syntax. There are four Combinators in CSS3, below is description and example of each:

Descendant combinator

The most familiar of all Combinators, the Descendant combinator allows for selecting any element f which is a descendant (child, grandchild, great-grandchild and so on) of an element e. The combinator syntax for a Descendant combinator is a single “white-space” character.

/* Matches all

elements which are descendants of an
element /
article h1{
/ declarations */
}

8.1. Descendant combinator

Child combinators

Child combinators allow for selecting any element f which is a direct child of an element e. The combinator syntax for a Child combinator is a single “greater-than” (>) sign.

/* Matches each

element that is a direct child of an

element */
article > section {
/* declarations */
}

8.2. Child combinator

Adjacent sibling combinator

The Adjacent sibling combinator is a Sibling combinator which allows for selecting an element f which is adjacent to an element e; that is, element f immediately follows element e in the document tree. The combinator syntax for an Adjacent sibling combinator is a single “plus” (+) sign.

/* Matches all elements which are the next sibling of a element */
strong + em {
/* declarations */
}

8.3.1. Adjacent sibling combinator

General sibling combinator

New in CSS3, the General sibling combinator is similar to the Adjacent sibling combinator in that it matches an element f which follows an element e in the document tree; however, whereas in the Adjacent sibling combinator element f must immediately follow element e, the General sibling combinator allows for selecting an element f which is preceded by an element e, but not necessarily immediately preceded by an element e. The combinator syntax for a General sibling combinator is a single “tilde” (~) sign.

/* Matches all elements which are preceded by a ~~element */~~
del ~ time {
/* declarations */
}

8.3.2. General sibling combinator

The following link provides a (rather crude in terms of design) example of each Combinator described above:
View Example

CSS3 Attribute Selectors

eric — Thu, 10 Nov 2011 15:59:33 +0000

The power of CSS Selectors can not be understated; for, without them, there would be no simple means by which developers could target specific elements for styling in a manner abstracted from, or external to, the actual markup to which the styles will bind.

In addition to some of the more common Simple Selectors, such as Type Selectors, Class Selectors and Id Selectors, we have have Attribute Selectors, which, as the name implies, allow us to match elements based on their attributes.

Attribute Presence and Value Selectors

CSS2 introduced four Attribute Selectors; referred to as Attribute Presence and Value Selectors, which allow for course grained matching of specific elements based on their attributes and / or attribute values. These include the following:

e[attr]

Where e is an element and [attr] is an attribute of element e. For example, p[title] would match all p tags with a title, regardless of the value of the title.

/* Matches all
tags with a title and changes their background color to red with white text */
p[title]{
background-color: red;
color: white;
}

e[attr=val]

Where e is an element and [attr=val] represent an attribute of element e which contains the exact value of val. For example, p[title="Example 1"] would match all p tags with a title which equals “Example 1″ exactly.

/* Matches all
tags with a title equal to "Example 1" and changes their background color to green and text color to white */
p[title="Example 1"]{
background-color: green;
color: white;
}

e[attr~=val]

Where e is an element and [attr~=val] is an attribute of element e which has a value containing a whitespace-separated list of words, one of which equals val exactly. For example, p[title~="Example-1a"] would match all p tags with a title containing the word “Example-1a” in a list of whitespace delimited words.

/* Matches all
tags with a title containing the exact word to "Example-1a" and changes their background color to black and text color to red */
p[title~="Example-1a"]{
background-color: black;
color: red;
}

e[attr|=val]

Where e is an element and [attr|=val] is an attribute of element e that has a value of val exactly, or begins with val immediately followed by a hyphen “-”. For example, p[title!="Example"] would match all p tags with a title containing the word “Example-”, followed by any other value, such as “Example-1″, “Example-A”, etc..

/* Matches all
tags with a title containing the word to "Example-" and changes their background color to blue and text color to white */
p[title|="Example"]{
background-color: blue;
color: white;
}

View Example

Substring Matching Attribute Selectors

In addition to the above Attribute Presence and Value Selectors, CSS3 expands on this by defining three additional Attribute Selectors; referred to as Substring Matching Attribute Selectors. These additions allow for fine grained matching of specific elements based on their attribute values.

In simplest terms, the new Attribute Selectors in CSS3 can be used to match an element with a given attribute whose value begins, ends or contains a certain value. The following is a basic description and example of each new Attribute Selector:

e[attr^=val]

Where e is an element and [attr^=val] is an attribute of element e which contains a value that begins with val.

/* Matches all linked resources sent over https */
a[href^="https"]{
color: red;
}

e[attr$=val]

Where e is an element and [attr$=val] represent an attribute of element e which contains a value that ends with val.

/* Matches all anchor tags to .html documents */
a[href$=".html"]{
color: green;
}

e[attr*=val]

Where e is an element and [attr*=val] is an attribute of element e which has a value that contains val.

/* Matches all anchor tags which contain a query string */
a[href*="?"]{
color: blue;
}

View Example

To summarize, there are a total of seven Attribute Selectors in CSS3, three of which are new. Whether used for general matches, such as global Attributes; e.g. *[hreflang|=en] or more specific matches, such as chaining; e.g, a[href^="https"][target="_blank"], Attribute Selectors provide a powerful mechanism for selecting both general and specific content within a page.

CSS3 selection pseudo-element (dropped)

eric — Wed, 02 Nov 2011 06:23:32 +0000

With both the CSS3 Selectors and CSS3 Namespaces Modules, respectively, having been released as official W3C recommendations (Selectors, Namespaces), I felt compelled to re-review each specification.

Interestingly, while reviewing the CSS3 Selectors Module (my personal favorite), I noticed that the selection pseudo-element selector which was originally drafted for CSS3 had been dropped from the proposal. In fact, it was dropped a rather long time ago.

In case you are not familiar with the selection pseudo-element, essentially it allows for defining the text color and background-color of selected text within a document.

For example, all elements on my site have a red background with white text when selected – such as this text here (select it) – based on the following two simple rules:
// IE, Chrome, Safari, Opera code::selection { background: #ca3131; color:#fff; } code::-moz-selection { background: #ca3131; color:#fff; } And so, while having been dropped, support is already rather good (FF3.6, SA3.1+, OP9.5+, CH2+, IE9) and as far as I am aware Browser vendors will continue to support ::selection.
HTML5 Structural Elements eric — Wed, 19 Oct 2011 22:37:11 +0000 The Semantic Web is not a separate Web but an extension of the current one, in which information is given well-defined meaning, better enabling computers and people to work in cooperation. - Tim Berners-Lee The HTML5 Specification introduces many new semantic elements intended to provide meaning to the structure of a document. These elements are quite important as they allow for marking up a document in meaningful ways which, prior to HTML5, would have otherwise required a rather ambiguous markup consisting primarily of divs and ids to provide semantic structure. Being purely markup based, it is understandable why these new semantic elements may not excite as much interest as many of the more attention grabbing HTML5 specifications, such as audio, video, Web Workers, WebSockets, Web Storage etc. However, it is important, perhaps even necessary, to emphasize the significance these new elements present in terms of helping to solidify the realization of what the web is intended to be: an open medium for disseminating homogeneous and heterogeneous information. With this in mind, combined with an informed understanding of the context in which each new semantic element can be applied, overtime the Web will (quite naturally) evolve in many new, exciting and perhaps previously unthought-of ways. Broadly, the new semantic elements introduced in HTML5 can be succinctly summarized as follows: The Element The element is rather self explanatory in that it allows for defining content which is to be denoted as a header of a page, or a header within a section of a page. Headers typically provide introductory and / or navigational content via hgroup and nav elements. What is important to keep in mind is that multiple elements can be defined per page. Some Blog Some Blog Description Last Modified: 2011-10-19</time>p> W3C Specification (section 4.4.8) The Element The element represents an important section of navigational links to specific pages or specific sections within the current page. As such, not all navigational links need be defined within a . Some Blog Some Blog Description Last Modified: 2011-10-19</time>p> Navigation "home.php">Home</a>li> "about.php">About</a>li> "contact.php">Contact</a>li> W3C Specification (section 4.4.3) The Element The element provides a means by which content can be represented independently from the document or application with which it is associated. General examples could include, as one may have guessed, an article from a newspaper, a blog post, a comment on a blog post, a self contained UI widget, and so forth. Some Post 2011-10-02</time>p> This is a simple example of the article element. … W3C Specification (section 4.4.4) The Element The element defines generic sections of a document, article or entire application. The section element is intended to provide semantics for a document and is not intended to be used as a container for styling purposes, in which case a element should be used. Some Post 2011-10-02</time>p> This is a simple example of the article element. … Comments Posted by: Eric Feminella 2011-10-1</time>p> Nice post, simple enough! Categories "/html5">HTML5</a>span> W3C Specification (section 4.4.2) The Element The element represents content which is relevant to, or supportive of it’s surrounding content, but is not required to convey the information set forth by the surrounding content. General examples could include a pull quote, a blog roll, a sidebar etc. Some Post 2011-10-02</time>p> This is a simple example of the article element. … Comments Posted by: Eric Feminella 2011-10-1</time>p> Nice post, simple enough! Categories "/html5">HTML5</a>span> "tags"> "semantics/">semantics</a>li> "elements/">elements</a>li> … W3C Specification (section 4.4.5) The Element As with the element, the element is rather self explanatory in that it allows for defining content which is to be denoted as a footer of a page, or a footer within a section element for it’s nearest ancestor. A page can contain multiple elements, each unique to a particular section. Some Post 2011-10-02</time>p> This is a simple example of the article element. … Comments Posted by: Eric Feminella 2011-10-1</time>p> Nice post, simple enough! Categories "/html5">HTML5</a>span> "tags"> "semantics/">semantics</a>li> "elements/">elements</a>li> … class="g-plusone" data-annotation="inline"> W3C Specification (section 4.4.9) Putting it all Together The following example is comprised of each semantic element described above to form a complete, valid HTML5 document: "utf-8" /> HTML5 Semantic Structure Example Some Blog Some Blog Description Last Modified: 2011-10-02</time>p> Navigation "home.php">Home</a>li> "about.php">About</a>li> "contact.php">Contact</a>li> Some Post 2011-10-02</time>p> This is a simple example of the article element. … Comments Posted by: Eric Feminella 2011-10-13</time>p> Nice post, simple enough! Categories "/html5">HTML5</a>span> "tags"> "semantics/">semantics</a>li> "elements/">elements</a>li> … class="g-plusone" data-annotation="inline"> Circumventing Conditional Comparisons eric — Fri, 14 Oct 2011 23:36:37 +0000 Often during the course of my day I come across code which evaluates the same conditional comparisons in multiple contexts. Understandably, this is rather typical of most software systems, and while it may only introduce a negligible amount of technical dept (in the form of redundancy) for smaller systems, that dept can grow considerably in more complex, large scale applications. From a design perspective, this issue is applicable to nearly every language. For example, consider a simple Compass class which defines just one public property, “direction” and, four constants representing each cardinal direction: North, East, South and West, respectively. In JavaScript, this could be defined simply as follows: var Compass = function(direction){ this.direction = direction; } Compass.NORTH = "North"; Compass.EAST = "East"; Compass.SOUTH = "South"; Compass.WEST = "West"; Technically, there is nothing problematic with the above class signature; the defined constants certainly provide a much better design than conditional comparisons against literal strings throughout implementation code. That being said, this design does lead to redundancy as every instance of Compass which needs to evaluate the state of direction requires conditional comparisons. For example, to test for Compass.North, typically, client code must be implemented as follows: if (compass.direction === Compass.NORTH) { //… } Likewise, simular comparisons would need to be implemented for each cardinal direction. And, while this may seem trivial for a class as simple as the Compass example, it does become a maintenance issue for more complex implementations. With this in mind, we can simplify client code by defining each state as a specific method of Compass. In doing so, we afford our code the benefit of exercising (unit testing) Compass exclusively. This alone improves maintainability while also simplifying client code which depends on Compass. As such, Compass could be refactored to: var Compass = function(direction){ this.direction = direction; } Compass.prototype = { isNorth: function() { return this.direction === Compass.NORTH; }, isWest: function() { return this.direction === Compass.WEST; }, isSouth: function() { return this.direction === Compass.SOUTH; }, isEast: function() { return this.direction === Compass.EAST; } } Based on the above implementation of Compass, the previous conditional comparison can be refactored as follows: if (compass.isNorth()) { //… } Comparator API To simplify implementing conditional comparisons, I have provided a simple Comparator API that defines a single static method: Comparator.each, which allows for augmenting existing objects with comparison methods. Comparator.each can be invoked with three arguments as follows: type The Class to which the comparison methods are to be added. property The property against which the comparisons are to be made. If the property has not been defined it, too, will be added. values An Array of constants where each value will be used to create a new comparison method (prefixed with “is”). If the constants specified are Strings, typically an Array containing each constant should suffice. For example, passing [Foo.BAR] where BAR equals “Bar” would result in an isBar() method being created. To specify custom comparison method names, an Object of name/value pairs can be used where each name defines the name of the method added and the value is the constant evaluated by the method. This is useful for constants which are not strings. For example, {isIOS421: DeviceVersion.IOS_4_2_1} where IOS_4_2_1 equals 4.2.1 would result in an isIOS421() method being created. Taking the Compass example, the previous comparison methods could be augmented without the need to explicitly define them via Comparator.each: var Compass = function(){ this.direction = direction; } Compass.NORTH = "North"; Compass.EAST = "East"; Compass.SOUTH = "South"; Compass.WEST = "West"; Comparator.each( Compass, "direction", [Compass.NORTH, Compass.WEST, Compass.SOUTH, Compass.EAST] ); The above results in the comparison methods isNorth, isEast, isSouth and isWest being added to the Compass type. Comparator: source | min | test (run)

type
The Class to which the comparison methods are to be added.
property
The property against which the comparisons are to be made. If the property has not been defined it, too, will be added.
values
An `Array` of constants where each value will be used to create a new comparison method (prefixed with “is”). If the constants specified are Strings, typically an `Array` containing each constant should suffice. For example, passing `[Foo.BAR]` where `BAR` equals “Bar” would result in an `isBar()` method being created. To specify custom comparison method names, an `Object` of name/value pairs can be used where each name defines the name of the method added and the value is the constant evaluated by the method. This is useful for constants which are not strings. For example, `{isIOS421: DeviceVersion.IOS_4_2_1}` where `IOS_4_2_1` equals 4.2.1 would result in an `isIOS421()` method being created.

Eric Feminella

AT&T Best Practices Guide for App Development

AT&T Research Labs: Mobile Application Resources

Configuring iOS HTTP Monitoring

Configuration

Additional Note

External Templates in jQote2

DHTMLX Touch 1.0 Released

Function Overwriting in JavaScript

Function Overwriting

Considerations

Concluding Thoughts

Refreshing listviews in jQuery Mobile

jQuery Mobile 1.0 Released

CSS3 Combinators

Combinators

elements which are descendants of an element */ article h1{ /* declarations */ }

CSS3 Attribute Selectors

Attribute Presence and Value Selectors

Substring Matching Attribute Selectors

CSS3 selection pseudo-element (dropped)

HTML5 Structural Elements

Comments

Categories

Putting it all Together

Comments

Circumventing Conditional Comparisons

Comparator API

elements which are descendants of an
element /
article h1{
/ declarations */
}