Deploying shared resources

by Jargon » Thu, 25 Mar 2010 00:56:10 GMT


Sponsored Links
 Hi,

We are investigating the possibilities to package & deploy platform UI
extensions which can contain both Java code and resources - which then
can be (re-)used by applications using <uses-library> tag in the
AndroidManifest.xml.

One solution which has been discussed was to use the aapt -x option
together with the new --custom-package option introduced in November
to generate unique resource identifiers for the shared resource
package.

Then, just as the <uses-library> information in the manifest file
would bootstrap the class loader with the listed  extension packages,
it would add these packages to the asset manager as well - allowing
the asset manager to locate and load the extension resources. (This
would require a platform extension.)

So, my question is really if this is a way forward - using the 8
package bits in the resource identifiers? This solution would probably
work initially for one vendor since the allocation of unique package
identifiers would be an internal issue, but if extension packages
where to be exchanged within the android community there would be a
high risk of packages using the same identifiers.

BR
Jrgen Ekstrm
Software Engineer
Sony Ericsson

--



Deploying shared resources

by Mark Murphy » Thu, 25 Mar 2010 01:03:31 GMT


 


You and me both, though I'm not trying to use <uses-library>.


That's interesting -- I had not noticed --custom-package before. I will
need to do some experiments to see if this helps with the solution I'm
working on.


I'm trying to avoid anything that requires modifying the SDK, and I
agree that overloading <uses-library> this way would require such
modifications AFAIK.


What are the "8 package bits"?


The issue of identifier collisions is a well-understood one for those
who have done development before with reusable components or modular
operating systems. Everything from Linux's apt and yum to Ruby gems
requires unique identifiers. So long as there are a handful of popular
repositories, "first one in wins" should suffice there.

Hence, I am not that worried about that aspect of the problem too much.
Whoever comes up with a component packaging system just needs to also
run a repository.

-- 
Mark Murphy (a Commons Guy)
 http://commonsware.com  |  http://twitter.com/commonsguy 

_The Busy Coder's Guide to *Advanced* Android Development_
Version 1.4 Available!

--


Sponsored Links


Deploying shared resources

by Jargon » Wed, 31 Mar 2010 15:28:31 GMT


 n Mar 24, 7:03pm, Mark Murphy <mmur...@commonsware.com> wrote:
Can you explain more of your strategy - and how to avoid platform
changes?
My initial plan is to do very small changes in the platform to enable
vendors
to build their own resource packages, just as framework-res.apk, since
most
of the stuff already seems to be there. Then looking into a more long-
term solution
which eliminates the "unique package identifier" issue which in
inevitable,
basically by replacing the top 8 package bits in the resource
identifier with a
namespace identifier, e.g. "com.vendor.foo". Such a solution would
enable
introduction of third party packages just by adding them into the file
system since
their resources would not clash with existing ones.

This fix enabled us to use the aapt tool as is, without any patching.
Still we
are considering another option --custom-package-id which would enable
finer
control of which package identifier is assigned to the generated
package.

We were considering introducing a <uses-resources> tag but this would
require a lot more changes. To me, it feels natural to think that a
library
could hold both code and resources.

Each resource identifier consists of 32 bits were 8 top bits defines
the
package in which the resource belongs to. Platform resources are 0x01
and 0x7F are application resources. The idea is to use the remaining
253 values for extension packages.

With the introduction of namespace, e.g. "com.vendor.foo" such a
repository would
not be needed since they would eliminate resource clashing.

--



Other Threads

1. Programming in Java

Programming in Java first provides a thorough understanding of the
basic concepts of object-oriented programming principles and then
moves onto explain the concepts in Java. Beginning with the history
and creation of Java to its properties and applications, it gradually
moves ahead to provide an exhaustive coverage of features such as
operators, classes, objects, inheritance, packages, and exception
handling. The book provides a comprehensive discussion of the latest
features of Java such as enumerations, generics, logging API, console
class, StringBuilder class, NetworkInterface class, and assertions.
The inclusion of these features combined with core concepts like
multithreading, applets, AWT, and swings provide a thorough
understanding of the important concepts. Lastly, the book gives an
insight into some advanced concepts such as servlets, RMI, and JDBC.
Numerous programming exercises are interspersed in the chapters for
better understanding of concepts. The book includes detailed exercises
at the end of each chapter as also some key review questions to help
readers revise the concepts learnt. ISBN - 9780198063582
you can buy this book and many more books from http://www.amazingindianbooks.com

-- 

2. Updating the Tab icons

Hello All ,

I have been trying to update the Tab icons  after the tabs are ll set
up but there has been no clean solution to it. Can  some one guide me
to a means of doing the same.

-- 

3. how to show a dialog alert dialog when receive a broadcast

4. Possible SoundPool bug in setLoop

5. Graphics performance

6. OpenGL ES Canvas

7. VideoView continues to play in 2.1