incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Reinstein <reinstein.m...@gmail.com>
Subject Re: [Android] Distributing Drawable Resources - What is acceptable?
Date Wed, 26 Sep 2012 08:14:54 GMT
> These aren't images that would be used in HTML. We're talking
> about images that are used in the Java UI portions of the code

Can we inline those assets similar to how base64 encoded data uris work in
html? I would imagine ios, android, blackberry, etc would allow for
declaring large byte arrays right in the code. Could those byte blobs then
be rendered into images in the various UIs?



On Wed, Sep 26, 2012 at 3:58 AM, Brian LeRoux <b@brian.io> wrote:

> Not an ideal situation but we do need to address static assets in our
> plugin packages too.
>
> I don't think we ever thought camera was going to be easy...if
> anything this brings up a great test bed for plugin packaging anyhow.
>
> On Wed, Sep 26, 2012 at 1:43 AM, Jesse MacFadyen
> <purplecabbage@gmail.com> wrote:
> > This is the same issue as the capture dialogs isn't it?
> > iOS and WP7 already package resources for making audio recordings.
> >
> >
> > Sent from my iPad
> >
> > On 2012-09-25, at 4:32 PM, Joe Bowser <bowserj@gmail.com> wrote:
> >
> >> These aren't images that would be used in HTML.  We're talking about
> >> images that are used in the Java UI portions of the code, such as this
> >> new camera that we're working on.  The problem is that we have to
> >> pre-populate each project with these images, which means more nasty
> >> create script issues, which I personally loathe.  However, Android
> >> doesn't allow you to just have images in the JAR.  I don't know why
> >> that is, but that would be a nice feature to have on Android.
> >>
> >> It'd be nice if there was a less brittle way of doing it, but I can't
> >> think of any at the moment..
> >>
> >> Joe
> >>
> >> On Tue, Sep 25, 2012 at 4:26 PM, Mike Reinstein
> >> <reinstein.mike@gmail.com> wrote:
> >>> Could we possibly use base64 encoding for images, and inline them? It
> would
> >>> take up 30% more space but it means you can inline them in the html
> rather
> >>> than having to package seperate resources?
> >>>
> >>> -Mike
> >>>
> >>> On Tue, Sep 25, 2012 at 7:19 PM, Joe Bowser <bowserj@gmail.com> wrote:
> >>>
> >>>> An icon is one thing, but we're going to have to start shipping UI
> >>>> elements, which makes things more brittle.  I'm wondering if anyone
> >>>> has any way of making this less brittle or if we're going to just have
> >>>> to drop the resources in the /res directory, use our typical mapping
> >>>> and hope for the best.
> >>>>
> >>>> Investigating zoom.  It look like we're going to need some mocks done
> >>>> up on this end, so I'll have to figure that out.
> >>>>
> >>>> Joe
> >>>>
> >>>> On Tue, Sep 25, 2012 at 4:15 PM, Filip Maj <fil@adobe.com> wrote:
> >>>>> Don't understand the issue Joe? We already ship a default icon
> drawable
> >>>>> resource - what's the issue with more?
> >>>>>
> >>>>> On 9/25/12 1:03 PM, "Mike Reinstein" <reinstein.mike@gmail.com>
> wrote:
> >>>>>
> >>>>>> If someday we were to package the camera plugin as we plan to
with
> 3rd
> >>>>>> party plugins, we could easily add assets. Several plugins already
> do
> >>>>>> this.
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> On Tue, Sep 25, 2012 at 3:38 PM, Joe Bowser <bowserj@gmail.com>
> wrote:
> >>>>>>
> >>>>>>> Hey
> >>>>>>>
> >>>>>>> So, while doing the UI for the Camera, I just realized that
we're
> >>>>>>> going to have to distribute images with Cordova.  I can
see this
> being
> >>>>>>> an issue with any plugin that does UI.  Does anyone have
any idea
> how
> >>>>>>> to solve this issue?
> >>>>>>>
> >>>>>>> Joe
> >>>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message