Titanium JIRA Archive
Alloy (ALOY)

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

GitHub Issuen/a
TypeImprovement
PriorityMedium
StatusResolved
ResolutionFixed
Resolution Date2012-09-26T15:22:45.000+0000
Affected Version/sn/a
Fix Version/s2012 Sprint 20, Release 3.0.0
ComponentsRuntime, XML
Labelsn/a
ReporterTony Lukasavage
AssigneeUnknown
Created2012-07-26T11:36:02.000+0000
Updated2018-03-07T22:26:07.000+0000

Description

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'),
});

Comments

  1. Russell McMahon 2012-07-26

    Let's discuss this a bit more I think of WPATH as a constant but maybe a Alloy function call like getResource(...) and from the javascript argument somehow get the path. How does Android do it? I thought they grabbed resources using some kind of wrapper correct.
  2. Tony Lukasavage 2012-07-26

    What would be the advantages of the Alloy.getResource() method? I ask mainly because that would have to be performed at runtime, where WPATH (or any other name) could be done at compile time, potentially improving performance. I don't understand your questions as it relates to Android. Android doesn't have to worry about encapsulation. The reason the widgets assets and libraries are structured as such is to ensure that they don't conflict with any other installed widgets in your project.

JSON Source