I am new to PhoneGap and PhoneGap Build and jQuery Mobile.
During my 1st build in PhoneGap I received this error...
invalid characters [._-] in filenames and/or directories
Invalid widget archive - resource name is not valid(jquerymobile/ images/ajax-loader.png)
...which means....
The BlackBerry Widget Packager, a RIM tool that takes your application assets and packages them into a BlackBerry-compatible binary, has very stringent rules on what characters your filenames and directories can be composed of. Make sure all of your filenames and directories contain only alphanumeric characters. Until RIM can fix this issue, unfortunately there is nothing we can do about this.
Invalid Directory Names Another twist in the BlackBerry Widget Packager saga, there are two names that are reserved for directory names: bin and src. If your application package contains directories with either of these names, the Widget Packager will fail. Make sure you rename those directories!
...so THAT means that one would have to rename virutally ALL the jQuery Mobile imges and files and those in jQuery itself and even the PhoneGap JS file too...
...is all that renaming going to cause an "internal" or "hidden" issues, relative to the workings of jQuery Mobile and jQuery and PhoneGap, such as, for example, the fact that the images are used internally by jQuery Mobile and, as such, the name change will need to propogate into the JS code itself because those image filenames are probably references internally in the jQuery Mobile JS itself... so has anyone done this???
iOS5 transitions & fixed toolbars: Refined, but off by default (for now)
The new iOS5 page transitions and true fixed headers have been improved significantly since Beta 3 but after much debate, we’ve decided to have this feature off by default for now because we want to wait for the final version of iOS5 to arrive so we can test this thoroughly. Note that we’re now using a 3D transform CSS rule reduce page rendering artifacts which could cause memory use issues on very complex pages so you may need to override this selectively. To mitigate some usability issues with overflow containers and fixed headers, we’re also disabling zoom by injecting a meta viewport tag only for iOS5 if this feature is enabled. We’re hoping this won’t be necessary long-term but this is the short-term fix.
...what exactly does that mean...
(1). Does it mean "fixed headers and page transitions will be implemented in jQuery Mobile but will only work for iOS5"?
(2). Does it mean "fixed headers and page transitions will be implemented in jQuery Mobile and will work for iOS5 and Android"?
(3). Something else?
You see, the qualifier "iOS5" in the heading is a bit misleading.
...but at the same time (AFAIK) there is no such implementation in jQuery Mobile other than the "magically disappering and reappearing" pseudo-fixed-headers and pseudo-fixed-footers?
That is...
...if it works at the link above then why can't jQuery Mobile do whatever they are doing there to make them work?