----- Original Message ----- > Thanks for making that project page and starting this thread. I have two main > questions to start:
> 1) From a UX perspective, what kinds of things are we going to allow this > add-on to put in the snippet/promo banner? The banner itself is going to be > made in our native Java UI, so if we want to design a JS API that add-ons > can use, we'll have to be explicit about what things that API can do. I was > thinking that we would just let them provide an icon and some text, which > matches this mock-up that ibarlow created: http://cl.ly/image/3j0i1w2x1s1x . Or this one: http://cl.ly/image/1M3H0j2X3008 > 2) How do you actually see this integrating with the existing snippets > service? As I understand it, the snippets service that desktop uses serves > up web content, which is rendered directly in about:home (including running > JS). I suppose we could have the service serve us an add-on, or we could > support some simplified markup that we could convert into the appropriate > API calls, but I don't see us ever having the same kind of flexibility that > desktop has as long as we're creating this promo banner in native UI. Also, > the content from desktop snippets runs with content privileges, so if we do > start supporting running JS from this service, we should make sure to take > the same security precautions. I don't think we want this to integrate at all with the desktop snippet service. This is totally separate. The add-on will decide where the snippets are coming from and when to update them. The JS API only needs to be able to show the information and respond to closes and clicks. And yes, we will be more constrained by the type of "parts" in the banner: Icon, Title and Message? The message could allow some basic span formatting - whatever Java gives us for free.
_______________________________________________ mobile-firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/mobile-firefox-dev
