Hello there,
I've been evaluating Titanium/Allow for more than a week now and would like to present the results to my customer. The prototype app I have works fine on iOS simulator, Android (emulator & device) and in a browser when I run the Mobile Web app through Titanium Studio.
1. MobileWeb packaging mess
To prepare the app for deployment on a web server I use (in Titanium Studio) Package > Mobile Web > "Copy Mobile Web app to a directory in the local file system" which seems to be quite the same as taking the content of build/mobileweb.
I end up with the following mess: 
As you can see the alloy and images folders and other files are duplicated both at the root of the export and in the mobileweb subfolder. That's an unnecessary duplication of content but I don't know which version of the files to keep, why wouldn't the package tool clean it up properly?
(Note: there is no common "images" folder at the root of my "app" folder in Alloy. There is one in mobileweb/iphone and the images themselves are also in android/images/res-hdpi for now)
2. Image paths when uploading the mobile web app
Happy to have a folder to upload (even if polluted) I uploaded the full content to a webserver but not at the root of it. I upload it in a location like http://www.mysite.com/subfolder/web where web is the full content of what Titanium Studio exported.
When I access the app through a browser, none of my images work.
Inspecting the paths I see that they refer to http://www.mysite.com/images/myimage.png which obviously doesn't work because that's not where I uploaded my mobile web app.
In the app, either through Alloy XML files or through Alloy JS Controllers, I have images defined as
<ImageView class="icon" image="/images/icon_001.png" /> image.setImage('/images/icon_001.png');All the images set like that work perfectly fine in iOS, Android or in the test mobile web server (which is at the "root" of itself), but not when deployed.
Only the background images set like this:
image.setBackgroundImage('/images/icon_001.png');Work fine and point to
http://www.mysite.com/subfolder/web/images/myimage.png
That problem seems so trivial to me that I can't believe I'm not doing anything wrong. However the fact that it works for background images and not standard images tend to show that there is indeed a problem.
As anyone experienced it recently ?
I'm using Titanium Studio, build: 3.2.1.201402041146 Titanium Mobile 3.2.2.GA
Overall I must admit the amount of time I'm spending investigating such trivial issues doesn't give me a good impression of Titanium/Alloy.
