I have had the worst two days. Here I have my app, Notiffi, pretty much ready to go. I have it set up in iTunes connect, ready to go. I am ready for the last step in the process, archiving. I hit Archive and BOOM. Nothing. Build works. Debug works. Archive does not work, and it still doesn’t as I’m writing this. Also, suddenly I start getting linker errors like this when I was building it and so I couldn’t even check to see if the app worked any more.
Just a quick one today. I have read on several web pages that if you want to speed up the rendering of your site that you need to add -webkit-transform: translate3d(0,0,0) to the page elements to have the browser use the GPU to render the page instead of the CPU. I tried this trick several times and it never seemed to work. But I think that today I figured out why not. I would apply this trick to a container element that houses the things that were animating. This may not
Found an interesting behavior today. I have an LI element that has a click handler on it, but that LI element has an A element which has a link. So it looked kind of like this: 1 2 3 4 5 <ul> <li onclick="doSomething(); "> <A href="http://somewhere" target="_blank">Go</a> </li> </ul> But when I clicked on the link the event would fire (expectedly) but it wouldn’t open the link in the mobile browser window. Pulled my hair out for a while and then I wanted to see if the A element
I’ve been doing a lot of work in Phonegap lately and I really like it. However, one of the things I don’t like is that click events are really, really slow. There’s a reason for this. How does the browser know if it’s a click or the beginning of a move? The answer to this is to bind your click events to the “touchend” event. So, in JQuery you would previously do something like this. 1 target.bind(’click’, callback); But that introduces the lag. So I wrote a little function where
Keeping this for myself. I bet that I will find it useful someday. Simon Mac Donald: PhoneGap Android Application Preferences Plugin.