- From: Brian LeRoux <b@brian.io>
- Date: Fri, 25 Nov 2011 07:33:21 -0800
- To: Filip Maj <fil@adobe.com>
- Cc: "public-native-web-apps@w3.org" <public-native-web-apps@w3.org>
Ok! There was a TONNE of good discussion there. I captured some prior art on the wiki. [1] Lets use it to: * collect missing uses * look into pinging / alerting the Fixing Application Cache Community Group and HTML WG * forward thinking stuff: packaging w/ metadata like screenshots, inter-widget communication, webintents, etc Btw, I like the idea of embracing format agnostic config. Seems pragmatic and could open some interesting opportunities. [1] http://www.w3.org/community/native-web-apps/wiki/Main_Page On Thu, Nov 24, 2011 at 6:15 PM, Filip Maj <fil@adobe.com> wrote: > >>> >>> > 4. Apps being able to XHR to their own content has come up a lot (so >>> > jQuery mobile and other libs can be used more easily). Also, a lot of >>> > widget-like apps still use file://, which is bad because it breaks >>> > anything depending on an origin (e.g., localStorage). >>> > >>> > Just wondering, what are you guys using in PhoneGap as your local >>>content >>> > URI scheme on the various platforms? >>> >>> >>> >>> Relative URLs. So if you have an app running off index.html in your >>>widget >>> root, you can XHR to "partials/template_one.html" and get the right >>>local >>> content. >> >>Right, but those must "dereference" to something (i.e., in JS, what do >>you get back from "window.location.href" on each platform?). Is it >>file://? or content://? > > Sorry I think I misunderstood you. It is the file:/// URI > > >
Received on Friday, 25 November 2011 15:33:49 UTC