- From: Marcos Caceres <notifications@github.com>
- Date: Mon, 09 Mar 2015 05:31:38 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Message-ID: <w3c/manifest/issues/9/77844800@github.com>
Ok, there are two solutions here I can think of... 1. we support patch images, as per Android: from playing around, it appears that patch images are just PNGs with a 1px transparent border around the image. In that border, black pixel lines indicate what the stretchable areas are (you can have patterns like: __ _ __ ____ __). Android uses a `.9.png` file extension as the way to tell the OS that this is a 9-patch. So, in the manifest, we would also provide a member to say that it's a nine-patch image: ```JSON { splash: [{"src": "foo.png", "BikeShedMyName": "patch"}] } ``` When patch markers are missing, we just use, say, 30 by 30px (or some sensible default). BikeShedMyName could be "align" or "display" or something. 2. we support CSS border-image syntax. This seems overly complicated tho, because values relate to the rest of a stylesheet, so it's probably not even possible to support 2. So, my vote is just do 1: it's simple and straight forward :) On March 9, 2015 at 7:05:11 AM, Anssi Kostiainen (notifications@github.com) wrote: > @mounirlamouri For the background image, we're using the 9-patch image method. Android > uses something similar for stretchable bitmaps, see http://developer.android.com/guide/topics/graphics/2d-graphics.html#nine-patch > > --- > Reply to this email directly or view it on GitHub: > https://github.com/w3c/manifest/issues/9#issuecomment-77834657 --- Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/issues/9#issuecomment-77844800
Received on Monday, 9 March 2015 12:32:27 UTC