MyApp provides JavaScript best practices including: 1) Using namespaces to avoid naming collisions and define packages like MyApp.string.utils for reusable functions. 2) Branching code during initialization or lazily on first use to handle browser differences efficiently. 3) Passing configuration as an object instead of many parameters to simplify function calls. 4) Defining private methods and properties using closures to encapsulate code. 5) Employing self-executing functions for one-time initialization tasks. 6) Allowing method chaining for readability when calling several related methods.

2. JavaScript and UI Architecture
Best Practices
Siarhei Barysiuk
s.barysiuk@sam-solutions.net

3. Our roadmap

4. Introduction: What will we cover today?
• Coding patterns
JavaScript-specific best practices
• Design patterns
Language independent patterns, UI architecture

5. Coding patterns

6. Namespaces

7. Tip of the day
“Global variables should be avoided in order to
lower the possibility of variable naming
collisions. “

8. Namespaces: Defining namespace
//defining top-level package
var MyApp = MyApp || {};
//defining package
//defining package
MyApp.dom = {
MyApp.string = MyApp.string || {};
addEventListener: function(element,
//defining package
callback) {
MyApp.string.utils = {
//code goes here
trim: function(str) {
},
//code goes here
removeEventListener: function(element,
},
callback) {
reverse: function(str) {
//code goes here
//code goes here
}
}
};
};

9. Namespaces: Usage in code
MyApp.string.utils.reverse(...);
MyApp.string.utils.trim(...);
MyApp.dom.addEventListener(...);
MyApp.dom.removeEventListener(...);

10. Namespaces: namespace() function
//defining top-level package
var MyApp = MyApp || {};
//defines package structure
MyApp.namespace = function(name) {
if(name) {
//some checks if name is valid
var names = name.split(quot;.quot;);
var current = MyApp;
for(var i in names) {
if(!current[names[i]]) {
current[names[i]] = {};
}
current = current[names[i]];
}
return true;
}
return false;
};

11. Namespaces: Defining namespace
//defining top-level package
var MyApp = MyApp || {};
//defining package //defining package
MyApp.string = MyApp.string || {}; MyApp.namespace(quot;string.utilsquot;);
//defining package //defining package
MyApp.string.utils = { MyApp.string.utils.trim = function(str) {
trim: function(str) { //code goes here
//code goes here console.log(quot;trimquot;);
}, };
reverse: function(str) {
//code goes here MyApp.string.utils.reverse = function(str) {
} //code goes here
}; console.log(quot;reversequot;);
};

12. Questions?

13. Init-time branching

14. Tip of the day
“Branch some parts of the browser-specific code
during initialization, when the script loads, rather
than during runtime to avoid performance hit.”

15. Init-time branching: Defining browser-specific methods
MyApp.namespace(quot;domquot;);
MyApp.dom.addListener = null;
//all major browsers
if(typeof window.addEventListener === 'function') {
MyApp.dom.addListener = function(el, type, fn) {
el.addEventListener(type, fn, false);
};
}
//IE
else if(typeof document.attachEvent === 'function') {
MyApp.dom.addListener = function(el, type, fn) {
el.attachEvent('on' + type, fn);
};
}
//older browsers
else {
MyApp.dom.addListener = function(el, type, fn) {
el['on' + type] = fn;
};
}

16. Questions?

17. Lazy definition

18. Tip of the day
“The lazy definition pattern is very similar to the
previous init-time branching pattern.
The difference is that the branching happens only
when the function is called for the first time.”

19. Lazy definition: Defining browser-specific methods
var MyApp = MyApp || {};
Override function first time
MyApp.dom = {
addListener: function(el, type, fn){
if (typeof el.addEventListener === 'function') {
MyApp.dom.addListener = function(el, type, fn) {
el.addEventListener(type, fn, false);
};
} else if (typeof el.attachEvent === 'function'){
MyApp.dom.addListener = function(el, type, fn) {
el.attachEvent('on' + type, fn);
};
} else {
MyApp.dom.addListener = function(el, type, fn) {
el['on' + type] = fn;
};
}
MyApp.dom.addListener(el, type, fn);
}
};

20. Questions?

21. Configuration object

22. Tip of the day
“Instead of having many parameters, you can use
one parameter and make it an object.
The properties of the object are the actual
parameters.”

23. Configuration object: Ordinary constructor
var MyApp = MyApp || {};
MyApp.namespace(quot;domquot;);
MyApp.dom.Button = function(text, type) {
//some code here
}
MyApp.dom.Button = function(text, type, color, border, font) {
//some code here
}

24. Configuration object: Usage of configuration object
var MyApp = MyApp || {};
MyApp.namespace(quot;domquot;);
MyApp.dom.Button = function(text, settings) {
var type = settings.type || 'submit';
var font =settings.font ||'Verdana';
//..other props
//some code here
}

25. Questions?

26. Private properties and methods

27. Tip of the day
“Use local variables and methods inside a
constructor to achieve the “private” level of
protection.
Use naming conventions _doInternalOperation to
show that the function is private/protected.”

28. Private methods and properties: Private method
var MyApp = MyApp || {};
MyApp.namespace(quot;domquot;);
MyApp.dom.Button = function(text, settings) {
//..process properties
function setStyle(element, settings) {
//setting style to element
};
var button = //...
//..
setStyle(button,settings);
this.clone = function() {
var clonedButton = //...
//...
setStyle(clonedButton, settings);
}
//some code here
}

29. Questions?

30. Self-executing functions

31. Tip of the day
“Self-executing functions are especially suitable for
one-off initialization tasks performed when the
script loads.”

32. Self-executing functions: Usage
(function() {
//code goes here
})();
(function(){
// ...
var jQuery = window.jQuery = window.$ = function( selector, context ) {
// ...
return new jQuery.fn.init( selector, context );
};
// ...
jQuery.fn = jQuery.prototype = {
init: function() {
//...
}
};
})();

33. Questions?

34. Chaining

35. Tip of the day
“Pretty convenient way to call several related
methods on one line as if the methods are the links
in a chain.”

36. Chaining: Usage
var obj = new MyApp.dom.Element('span'); var obj = new MyApp.dom.Element('span');
obj.setText('hello'); obj.setText('hello')
obj.setStyle('color', 'red'); .setStyle('color', 'red')
obj.setStyle('font', 'Verdana'); .setStyle('font', 'Verdana');
document.body.appendChild(obj); document.body.appendChild(obj);
document.body.appendChild(
new MyApp.dom.Element('span')
.setText('hello')
.setStyle('color', 'red')
.setStyle('font', 'Verdana')
);

37. Questions?

38. Design patterns

39. Unobtrusive JavaScript

40. Unobtrusive JavaScript: Separate JavaScript functionality
<a onclick=quot;doSomething()quot; href=quot;#quot;>Click!</a>
<a href=quot;backuplink.htmlquot; class=quot;doSomethingquot;>Click!</a>
$('a.doSomething').click(function(){
// Do something here!
alert('You did something, woo hoo!');
});

41. Unobtrusive JavaScript: Never depend on JavaScript
<script type=quot;text/javascriptquot;>
var now = new Date();
if(now.getHours() < 12)
document.write('Good Morning!');
else
document.write('Good Afternoon!');
</script>
<p title=quot;Good Day Messagequot;>Good Morning!</p>
var now = new Date();
if(now.getHours() >= 12)
{
var goodDay = $('p[title=quot;Good Day Messagequot;]');
goodDay.text('Good Afternoon!');
}

42. Unobtrusive JavaScript: Never depend on JavaScript
<a href=quot;javascript:window.open('page.html')quot;>my page</a>
<a href=quot;#quot; onclick=quot;window.open('page.html')quot;>my page</a>
<a href=quot;page.htmlquot; onclick=quot;window.open(this.href)quot;>my page</a>
<a href=quot;page.htmlquot; class=quot;popupquot;>my page</a>
//some java script to open element with class quot;.popupquot; in a new window

43. Questions?