Please see the in-line comments. Thanks!
----- Original Message -----
> From: "Chuck Lee" <[email protected]>
> To: "Jonas Sicking" <[email protected]>
> Cc: "dev-webapi" <[email protected]>, "William Chen"
> <[email protected]>, "Anne van Kesteren"
> <[email protected]>, "Doug Turner" <[email protected]>, "Mounir
> Lamouri" <[email protected]>, "EDUARDO
> FULLEA CARRERA" <[email protected]>, [email protected]
> Sent: Tuesday, May 7, 2013 4:50:48 PM
> Subject: Re: Improving system messages to support webpages and more
>
>
> If we are going to extend the manifest for system message, it is
> possible to add another syntax defining a subtype(or filter,
> whatever)
> of system message?
Good point. I agree with you but for a different reason. Please see the
following example for registering activities in the manifest of Camera App and
the previous discussion thread at [1]:
"activities": {
"record": {
"filters": {
"type": ["photos", "videos"]
},
"disposition": "window"
},
"pick": {
"filters": {
"type": ["image/*", "image/jpeg"]
},
"returnValue": true,
"disposition": "inline",
"href": "/index.html#pick"
}
},
The issue is the system message mechanism cannot distinguish system messages
with different activity types because they actually share the same "activity"
system message type, which means we have to queue the pending system messages
by the same "activity" type even if they should belong to different queues (one
for something like "activity-record" and the other for "activity-pick").
If we can support sub-types then we can also solve this issue for activities.
[1]
https://groups.google.com/forum/?fromgroups=#!topic/mozilla.dev.webapi/wBVJdotpx0c
Gene
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
