Quote:
Originally Posted by geekmaster
I read the event device packets directly from native mode. In a script, no less. That was definitely a hack. 
You can also detect touches with waitforkey, running in the background. |
I tried
Code:
waitforkey > /mnt/us/test.txt &
It detects the touch events, but it stores in txt always "330 1"...
Any clue? Is it possibile to store something like coordinates (just like what eips uses)?
Quote:
Originally Posted by eureka
Application Cache technology (sell also 1, 2) could be possibly interesting to you. As you know, WAF app could simply point to website address. Application Cache manifest points to resources (html, js, css, etc.) to download and use when site is inaccessible (i.e. when device is offline). It also will download updated resources in future application use (if user is online and if some resources were updated). I know, Kindle Store application uses this technology (did you ever see that "updating your Kindle Store experience" screen? At this time application updates it's Application Cache).
|
It seems interesting, I never heard of it before!!
I'll read it as it seems to be really usefull for another project I have...
