Thanks Dianne!
However, we have take a try to modify the platform.
I will let you know if we have any good news.
James
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
Thanks, Dianne.
I think, there is no other approach for
going down this road but packing our resources into framework-res.apk
by PRODUCT_PACKAGE_OVERLAYS, isn't there?
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
We just like our resource to be public to all apks like framework's
resource.
Develop can reference it in layout.xml or in code directly.
I saw some discussions about loading resource from another apk. I
think that way is no elegant enough.
Thanks, Dianne.
--
unsubscribe: android-porting+unsubs
Dianne, I post one message (http://groups.google.com/group/android-
platform/browse_thread/thread/d7016b891fbabcea) on android-platform
and share one method about how to build our own resource apk.
Please take a look if you have time. Thank you.
James
--
unsubscribe: android-porting+unsubscr...@
My suggestion: please don't. This way lies lots of difficult to maintain
patches, a good chance of subtle bugs that cause problems for applications,
and other bad things. Please try to investigate any other approach for
going down this road.
On Sun, Nov 29, 2009 at 5:35 PM, James Wang wrote:
>
You can certainly take that approach. I don't know enough about what you
are doing to suggest others -- for example you could put it in a separate
.apk that you explicitly load and retrieve things from, rather than trying
to merge all the resources together.
On Tue, Dec 1, 2009 at 5:42 PM, James
On Thu, Dec 3, 2009 at 12:35 AM, James Wang wrote:
> We just like our resource to be public to all apks like framework's
> resource.
> Develop can reference it in layout.xml or in code directly.
>
Absolutely not, just like you can't make arbitrary APIs public to developers
on your builds. The An
