Titanium Community Questions & Answer Archive

We felt that 6+ years of knowledge should not die so this is the Titanium Community Questions & Answer Archive

1.3 to

HAHA, Some how my title got cut off.. suppose to be "1.3 to 1.3.2"

I have a few issues and questions about this newly pushed out 1.3.2 sdk.

  1. Why did you release it as 1.3.2 if it will inevitably be 1.4? Just doesn't make sense, the whole reason for versions is to tell the difference between them and now thats worthless (If you would want to fix 1.3 bugs and release an actual 1.3.2 or 1.3.3 how do you do that now? You are an open source project so someone could want branch 1.3 and now its impossible to know the difference between 1.4 stuff and actual 1.3).. release the RC of 1.4 as "1.4 RC" not "1.3.2 (The 1.4 RC)".. silly.

  2. For some reason includes got messed up, now the relative location for iPhone and Android are different. For iPhone it always references from the 'Resources' folder, where in Android I have to backtrack and get into the 'Resources' folder.. in 1.3 this didn't happen.

  3. Did you change the way you reference images for Android? We were happily loading a bunch of PNGs in 1.3 with no problems and it was super fast. Now, in "1.3.2 (The 1.4 RC)", we are getting errors while it tries to load the NinePatch (*.9.png) files, which creates an inevitable OutOfMemory exception?? Do we need to now convert all of our PNGs to .9.png? Will this create a problem with the iPhone reference to the images?

  4. Is there a change log for "1.3.2 (The 1.4 RC)"?

  5. When will the actual "1.4" release be? The blog claimed that it would be approximately 2 weeks ago, but you must have ran into a couple issues. I understand that you are busy coding along, but it would be nice to know when a realistic and static release date is or even just an update of what is going on. For people who are nearing the end of development and want to verify their app will work with "1.4" and/or don't want to release under "1.3 (The 1.4 RC)" (because that just seems like a no-no), it would be extremely nice to know what is going on.

Please do not take my post the wrong way, yes I am frustrated about a few things, but I am in no way trying to criticize you guys! Just joking around for the most part (the "RC" thing ;)).

If you would like any clarification or help in fixing these bugs, shoot me an email at armsteadj1@gmail.com.

Thanks!
James

— asked July 7th 2010 by James Armstead
  • 1.3
  • 1.3.2
  • 1.4
  • android
  • bugs
  • iphone
  • issues
  • mobile
  • questions
0 Comments

4 Answers

  • (#5) ditto. (Forum) Is this thing on? (tap)(tap). I noticed a high ranking member of the Titanium staff commented on a very recent post concerning the awesomeness of the premium membership (it probably rocks, i just can't afford the high fee). Wish he could give us an update on the status of the promised 1.4.

    sincerely yours,
    Ti.createFrustratedUser

    — answered July 7th 2010 by Derrick Wynes
    permalink
    2 Comments

    • Yea, I am sure Premium membership rocks. As soon as our app rolls out and we make enough money to pay for one I am sure we will. The accelerator developers deserve it =)..

      — commented July 7th 2010 by James Armstead

    • i honestly can't afford to pay for "premium access" for bug fixes. so, i have to wait weeks while i get refunds and customer complaints, that i can't do anything about. it's also a catch 22 - i could pay for premium access if i could sell my app, but i can't sell my app because it's buggy because of this giant titanium 4.0 readiness fail. depressing.

      — commented July 7th 2010 by paul seymour

  • Please provide an example of what's changed in #2 are you saying that on iPhone all path references are now absolute wrt to Resouorces and Android uses Relative paths.

    #3 We made changes to reduce the memory used for bitmaps which has solved the out of memory for others. Please provide an example of how it's failing. Also are you getting an actual error wrt to 9.png or simply file not found?

    — answered July 7th 2010 by Don Thorp
    permalink
    0 Comments

  • >Please provide an example of what's changed in #2 are you saying that on iPhone all path references are now absolute wrt to Resouorces and Android uses Relative paths.

    Yes, that is what it seems like to me. if I have the following structure:

     /Resources
     /logic
        test.js
     /logic2
        test2.js

    and test.js does a "Titanium.include('logic2/test2.js')" it will work on the iPhone but not in Android. If I do "Titanium.include('../logic2/test2.js')" then it works on the Android and not iPhone. If I go back to 1.3 then "Titanium.include('logic2/test2.js')" works for both.

    >#3 We made changes to reduce the memory used for bitmaps which has solved the out of memory for others. Please provide an example of how it's failing. Also are you getting an actual error wrt to 9.png or simply file not found?

    First thing to note is, We aren't using NinePatch PNGs. Just normal ones.
    Second, It just gives me this error for every single "PNG: path not found: file:///android_asset/Resources/images/**.9.png"
    It almost seems like Android is automatically looking for these files, I know they are awesome and everyone should use them, but shouldn't there also be a way to turn them off? I am assuming the iOS doesn't use them, thus really making them irrelevant if you want to use the same UI for both iPhone and Android.

    — answered July 7th 2010 by James Armstead
    permalink
    2 Comments

    • The Android method is the correct one in that we're suppose to support relative paths. If you want absolute paths. Try "/logic2/test2.js" on both platforms.

      iPhone knows nothing about nine patch images and if you only put them in your android folder, they'll only be bundled with android and not with iPhone. We are going to be making major changes in 1.5 with the handling of images on Android to allow multiple resolutions/densities and transparent nine patch support. Currently, the only way to figure out if there are nine patch files that should be used on Android are to check when an image is loaded as a background. Those messages are harmless, but I'll look at changing them to debug.

      — commented July 7th 2010 by Don Thorp

    • I actually tried using '/Resources/…' and it got converted into '/Resources/Resoucres/….' in Android??

      So the fact that my app runs perfectly fine in 1.3 but fails in 1.3.2 and the only difference from the Trace is the NinePatch errors doesn't throw a flag up that something is wrong and its not just the fact that its throwing an error?

      Maybe there is a memory leak when loading files? It has to be leaving something open and not getting cleaned up when it goes out to try and find a NinePatch file for every image we have?

      Wouldn't adding something like.. "Titanium.UI.CheckForNinePatch = false", work instead? I understand that there isn't a way of knowing if a PNG has NinePatch files, but I know that before the app starts up. Heck, why not add one into the options for each control? I would GLADY add 'ninePatchExist: false' into every place if my app worked.

      Any how, has anyone from appcelerator tried to add a TON of non-NinePatch PNGs to an app and seen if it worked in 1.3.2?

      — commented July 7th 2010 by James Armstead

  • Don, Would you happen to have an update on any of my questions from the comments?

    — answered July 8th 2010 by James Armstead
    permalink
    0 Comments
The ownership of individual contributions to this community generated content is retained by the authors of their contributions.
All trademarks remain the property of the respective owner.