iOS todo list / considerations

[mattapperson]

THIS IS A WIP

1. Get TitaniumKit added as a second project in the workspace and building
2. From the app project pull in TitaniumKit into context

Then we need to consider how require works.

Right now we have JS files in bundles for dev and compiled into in-lined bytecode for prod. This is fine... except what we really want is that 3rd option as well to pull the files from a remote server via HTTP and/or sockets for active development.
Also we need to consider the 4th option below of native non-module code.
Lastly here, we need this to be NPM compatible with package.json

Build scripts

We then need the scripts (temp ones) to get the JS and other assets where they need to go (see TiForward/discuss#7)
This should also take into account NPM modules

Define a native workflow when NOT using modules

We need to demonstrate requiring into JS native code as a module without having to pre-compile a module. This code should exist in the apps project

Demonstrate the inclusion of a module

Sometimes there will be native modules still, precompiled and these should be linked at the TitaniumKit level to avoid messing with the apps project files.

Updating Titanium / HAL in an existing project

My thought here is we can do this one of 2 ways:

1. A CLI command that replaces the TitaniumKit project bits and the HAL headers/lib when needed
2. We use cocoapods
   I personally favor the latter, I dont love cocoapods but it is a standard these days