Add WKPFTable ant task to generate the binary link table and component map from an xml specification (to be generated by the master)
Work in progress on letting wkpf read the tables from flash instead of ram.
Include wkpftable task in build process and include binary file in application archive.
Don't need to worry about links and component map in garbage collector anymore since it's stored in flash now.
Removed some obsolete functions
Include binary link table in build process. The link table will be created in the app's build directory if the wkpftable property is specified, and it will be included in the app archive.
Changed some debug output from hex to decimal.
Merge branch 'merge-latest-nanokong-master' into binary-link-table-merge-new-master
Updated master to generate XML for link table and component map instead of Java
Demo broke on the node because I received an unexpected FUNC_ID_MEMORY_GET_ID from zwave which messed up the local node id. Ignore those cmdx when we're not expecting them.
The real problem seems to be deeper though, and caused by turning on too many debug statements.
Merge branch 'master' into merge-tmp

Conflicts:
	wukong/master/templates/fbp.html
	wukong/master/wkpf/xml2java/generator.py
Add wuclass id to component map
Create local wuobjects for native wuclasses based on the component map instead of from Java.
Add data for initvalues table to WKDeploy.xml
Added binary initvalues table and split up the binary tables into separate files instead of a single wkpftables file.
First version of binary initvalues table works. Still has a small problem where the master generates an initvalue for a readonly property.
Fix to initvalues: don't generate values for readonly properties.
Fixed mapper.py and binary tables code to work with virtual wuclasses.
Refactoring generated Java code.
Fixed duplicated calls to WKPF.registerWuClass that were generated when a node contains multiple instances of a virtual WuClass.