Confirmed users
429
edits
Gaia/Build/RefactoringToNodejs: Difference between revisions
Jump to navigation
Jump to search
Gaia/Build/RefactoringToNodejs (view source)
Revision as of 08:05, 23 January 2015
, 23 January 2015no edit summary
Ricky Chien (talk | contribs) No edit summary |
Ricky Chien (talk | contribs) No edit summary |
||
| Line 6: | Line 6: | ||
* Web developers are familiar with JavaScript, also NodeJs is the most popular and acceptable for those who are familiar with client side JavaScript. It could attract more contributors to involve and improve Firefox OS. | * Web developers are familiar with JavaScript, also NodeJs is the most popular and acceptable for those who are familiar with client side JavaScript. It could attract more contributors to involve and improve Firefox OS. | ||
* NPM is a well-known build-in package manager of node, such tool is commonly used for web developers for years. It will make your life easier that developers can install third-party libraries and | * NPM is a well-known build-in package manager of node, such tool is commonly used for web developers for years. It will make your life easier that developers can install third-party libraries and prevent us to reinvent the wheel if there is no such library provided by XULRunner. | ||
* | * It will be more easier if we build up a pure JS system. To implement Makefile and shell script, NPM provides a bunch of packages that let us build our pure JS system more quickly, flexible and maintainable. | ||
= Plan = | |||
Refactoring plan will split into 3 stages. | |||
== Stage 1 == | |||
== Stage 2 == | |||
== Stage 3 == | |||
== Q & A == | |||