6th annual Code Camp
8, 9 October 2011
Foothill College

This un-conference just keeps getting better and better. More people know each other, more students have clued into it, more people attend and more people give talks! This time there were even companies recruiting, for example, SurveyMonkey.

1. "Mobile Web Design Moves" by Luke Wroblewski
Designing a mobile app or website is very different from the desktop. The screen size is obviously smaller, so you have to make sure you choose just the most important functionality. You need to think about what features people need when they are on the move. People will type, as the massive popularity of texting and tweeting proves.
-Put one nav button top left, which jumps to the bottom of the screen where alll the navigation is.
-Don't replicate browser controls (like the back button) in your HTML app.
-Drop downs take so many taps. so avoid them.
-Input: specify type attributes in HTML, use input masks.
-Drag to refresh or reveal.
-Make interactions happen with the content, e.g. content is clickable.

2. "ECMAScript: What next?" by Douglas Crockford
The new features of the JavaScript language he is describing here may be implemented by browsers in 2013.
-Modules - gives us security; make JS one of the most secure programming languages in the world,
-Proxies,
-struct types intended for 3D graphics realtime,
-Parallel arrays for compute-intensive apps,
-Other features that will make JavaScript better for server side programs.
-See Wiki.ecmascript.org for more info or to make a feature request.

3. "Programming Android Tablets" by Oswald Compesatoand Markova Gargenta
Markova Gargenta -would be a great adjunct
Marko@marakana.com
He wrote the O'Reilly book
No more passwrds, must use OAuth
Android Java=
Java SE - UI , reflection, et al
+ Android API

4. "iPhone Development Kickstart" by Lance Bullock
-App Delegate exposes the app lifecycle
-You have Views and 'view controllers'
A 'view controller' is just another word for the controller in an M/V/C architecture
-Nib file is where you build your UI
-All positioning is absolute
-Cocoa touch frameworks and patterns
foundation, Uikit, mapkit
-Don't perform long running tasks on main UI thread

Objective C
-They are teaching Objective C at Canada college
-Has no constructors
-You have to release memory
-Uses alloc

5. "JavaScript Code Organization and Encapsulation" by Shawn Can Ittersum
This talk was standing room only. It assumed one already knew JavaScript and OOP and wanted to use JavaScript as a real application programming language.
-In JavaScript, all functions are closures because they all have scope.
-When you use "new" JS automatically creates an instance for you and you can refer to it as "this"
-Duck.prototype = { } Is the parent object, so all other Ducks will inherit from that object, which allows all other Ducks to use the same copy of a method in the prototype.
-Base.js allows for more intuitive inheritance and class defs.
-underscore as prefix is a signal that a variabe is private, but it isn't enforced by the language.
-Put all globals in Shared namespace.
-Keep all CSS styles in separate file.
-Avoid creating many DOM elements using JavaScript