SeattleJS Geodata Event Highlights and CoffeeScript Lecture
Table of Contents
- 1. SeattleJS
- 2. Geodata with Nate Vaughn
- 3. CoffeeScript with Geoffrey Grosenbach (of PeepCode)
- 3.1. Background
- 3.2. Use
- 3.3. Notes
- 3.4. Key Benefits
- 3.4.1. Fat arrow for binding this to a function
- 3.4.2. Ruby string interpolation
- 3.4.3. Need to have list comprehensions in Underscore vs. CoffeeScript
- 3.4.4. Proper management of this
- 3.4.5. Cleans the interface when creating applications
- 3.4.6. Firebug will have a CoffeeScript line support
- 3.4.7. Instance variable for a Class automatically become member
- 4. Tasks
- 5. Issues
1. SeattleJS
Design Commission is the likely ongoing space.
2. Geodata with Nate Vaughn
geo location api data aggregator.
- Based on Instagram
- Now Here This
- Uses iScroll plugin (v3; v4 has more features but integration cost) for mobile
- Provides a way to consolidate location based information from FS (but only venue photos or promotions), Instagram.
- Flickr geo data seemed unmatched to location
2.1. Updates
2.1.1. Share the links
2.1.2. Perform auth
2.1.4. Located based social graph
2.1.5. Pull to refresh
2.1.6. Triple tap
3. CoffeeScript with Geoffrey Grosenbach (of PeepCode)
@topfunky
3.1. Background
Lecture-based company.
3.2. Use
3.2.1. Process
Look at the way that CoffeeScript goes about reverse engineering a chunk of JavaScript:
- Remove punctuation
- s/this/@/
- Use :constructor
- s/function/->/
- Swap the order of formal parameters + function declaration
3.2.2. Consideration
- Libraries may need patches
- Imposes social overhead for any work with other people
3.2.3. Integration
Can be used with jQuery or Jasmine.
3.3. Notes
Used KeyNote as the presentation system.
See some additional CoffeeScript links at http://xfiles/display/ScrumCentral/CoffeeScript
4. Tasks
4.1. Test +cent + more does coercino
Unary + before a string attempts type coerction back to a float.
4.2. Document considerations
CoffeeScript doesn't provide a subset of functionality. Just abstracts some of the core coding typically required.
4.2.1. member variables
4.2.2. Class generation
4.2.4. Style consistency
4.2.5. Fat arrow
4.3. Pick classes based on organizational requirements
Use the examples provided by Troy.
5. Issues
5.0.1. Cannot trivially resolve back to source
This may be addressed in FireBug.
5.0.2. Organizational cost per resource is excessive
Requires a push for front-end control of the product development process.