Along the lines of Thinker's remarks about controlling when to update, some
updates may be large (a new set of maps for an offline navigation app is a good
example) and I might not want to update them when on a paid or slow pipe
(cellular). Also, I sometimes don't update if comments indicate an
On Apr 21, 2012, at 10:35 PM, Thinker K.F. Li wrote:
> Hi,
>
> Although we donwload pages automatically if the cache manifest changes,
> but the new cache will only be used for next time of launching.
>
> I concern more about faults of networks. Internet is not always stable
> and secured. For
Updated proposal. Please reply-to dev-weba...@lists.mozilla.org
Name of API: Open Web App API
Reference: https://developer.mozilla.org/en/OpenWebApps/The_JavaScript_API
Brief purpose of API: The Open Web Apps JavaScript API is a programmatic
interface for installing Web apps and for managing a
On 04/16/2012 10:22 AM, Jim Straus wrote:
How about un-install an app, update an app (assuming that the app has a cached
component and we can distinguish when cached components change, and also that
we desire that the user can control when an app is updated).
I also think that the risks for som
Hi,
As far as I know, you can do an uninstall now. Regarding the update
functionality I guess it will work a bit different, each time you visit a
new web app, if the cache manifest changes, or even if you don't have an
offline version and you are always using the online one, the system will
automa
How about un-install an app, update an app (assuming that the app has a cached
component and we can distinguish when cached components change, and also that
we desire that the user can control when an app is updated).
I also think that the risks for some of the APIs vary. For example, getSelf()
Please reply-to dev-weba...@lists.mozilla.org
Name of API: Open Web App API
Reference: https://developer.mozilla.org/en/OpenWebApps/The_JavaScript_API
Brief purpose of API: The Open Web Apps JavaScript API is a programmatic
interface for installing Web apps and for managing a client-side collect