[ALOY-135] Improve widget asset and lib path handling

problem

Right now managing paths that relate to encapsulated assets and libs in a widget is a bit unwieldily. For example, let's say you have a widget structure that looks like this: * com.domain.widget ** assets *** android **** images ***** someimage.png *** iphone **** images ***** someimage.png ***** someimage@2x.png ** controllers *** widget.js ** lib *** somemodule.js ** views *** widget.xml ** widget.json Here's some sample code from widget.js that would make use of those (ugly) encapsulated paths

var mod = require('com.domain.widget/somemodule');
var iv = Ti.UI.createImageView({
    image: 'images/com.domain.widget/someimage.png',
});

So like I mentioned, doable but ugly. It would benefit developers to have a shorthand method for defining asset and lib paths.

Possible Solution

We could use something like *WPATH()* wrapped around all paths in a widget to take care of proper pathing.

var mod = require(WPATH('somemodule'));
var iv = Ti.UI.createImageView({
    image: WPATH('images/someimage.png'),
});