On 05/29/2012 09:31 AM, Gervase Markham wrote:
On 29/05/12 14:55, Anant Narayanan wrote:
Because users are unable to see either the origin (domain name) or the
app's website at the time of install. The store is the last point at
which a user makes a install-or-no decision.
Why is that? Surely it makes sense to show the origin of the application
at the time of install?
As I said before, that's not true that the UA can't show the domain name
of the app at install time. Currently the doorhanger shows the app name
and the store domain, but we can change that.
"Error in installation: [object DOMError]" :-( As you know, I am using
Linux. Is this a bug I should file, or expected?
Unfortunately expected given the current state of the code.
Surely the domain is in the manifest? Otherwise, the UA doesn't know
what page to load when running the app.
This is very much relevant to installs_allowed_from, because developers
(of free and paid apps) may want to restrict their app from being listed
everywhere because they only trust certain stores to faithfully
represent their app.
Maybe they should revive compuserve ;)
That is the point at issue. But you are claiming that "the entire
installation architecture" needs to change if we decide not to let
developers do that. That would only make any sense if
installs_allowed_from were mandatory; but you've said it's optional. So
how can ignoring it in some cases suddenly break everything?
An additional point I'd like to make: currently, the install() call take
an optional parameter that is used to provide the payment receipts to
the UA. It's pretty clear that we can detect at install time if an app
is free or not using this parameter. And we could ignore
allow_installed_from for free apps.
Fabrice
--
Fabrice Desré
b2g team
Mozilla Corporation
_______________________________________________
dev-webapps mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-webapps
