Notes

subtitle module -> more publicity

XDK2 suggestions:
- more feedback on our design would be of massive help
- separate CSS from JavaScript code
- the folder structure now looks counter-intuitive right now. In UI folder, I was expecting UI widgets, but I find MVC in there...
- the console.setLogger() looks weird, it takes a logger module name string. Looks like a code smell to me. We should be able to modify it, to taking in a logger module instead.
- virtual key files: a shared vKey.js and also device specific keys in device/samsung/vKey.js, so that App developer will know exactly when they are working with a device specific key
- I feel that App developer have to config device packages is unnecessarily complicated, if that means we have to put the device detection outside of device packages, then it is a necessary evil. (http://en.wikipedia.org/wiki/Convention_over_configuration)
- the media player config also seems a bit complicated, though I'm not sure how to fix that
- history back action sounds like an App level default action, so consider putting key "back" handling into AppRoot
- The "view.hookTemplateRenderer" call in ax/ui/mvc/Controller does not look right to me. I think Controller creation/replacement should be centralized in controller manager. If using "new" to create controller, the controller tree structure may be broken.

Last inputs:
- define clear scope of XDK (such as 1.excluding the build process, leaving it to Stockholm team, 2. server proxy scripts)
- educate App developers how to use r.js optimization tool, let them optimize the App themselves, this would look more professional if XDK is to be used to by external parties.
- be careful when aiming for flexibility, it increases complexity. http://www.artima.com/intv/flexplex2.html


Other areas:
- Warn the developers about design pattern misuse: http://www.codinghorror.com/blog/2005/09/head-first-design-patterns.html (this post is kinda dramatic... but he made a good point)
- People don't like to be managed, they like to think they are working for their advantage. So maybe spent some time "畫大餅" is worth it. Not in the sense of giving empty promises, but in the sense of convincing how their goals are aligned with the projects they are currently working on.
- Provide plenty training for team members, this is also a good way of communicating why working here is for their advantage. (To me, there being a lot of "sweat-shop" style companies does not mean we must also go "sweat-shop" style, there are still options available.)