[android-developers] Re: creating a shared jar library

2009-08-27 Thread Mac
I've sufficiently understood about the reason not to support third party libraries. Goolgle apis as regular sharing libraries can add on %ANDROID_HOME%/ add-on and then Android Applications can use that libraries. Like this, could I add my sharing library on %ANDROID_HOME%/add-on directory? If

[android-developers] Re: creating a shared jar library

2009-08-26 Thread Mac
Hello, Dianne Hackborn. I've read all of these mails and I understood most of them. But, I don't know one important point of these mails. I wonder what the difference of regular shared libraries and third party shared libraries. Could you tell me the difference for me? On 8월5일, 오후11시18분,

[android-developers] Re: creating a shared jar library

2009-08-26 Thread Dianne Hackborn
I meant regular as what we generally call a shared library in any OS. A third party shared library is specifically talking about the (theoretical not currently possible) case of putting a shared library as an .apk up on market that could be installed by the system and used by other applications.

[android-developers] Re: creating a shared jar library

2009-08-26 Thread Mac
Thanks, Dianne Hackborn. Could I think the reason that can't support sharing third party libraries is that all applications are on each Dalvik VM? And there's any way to share a regular library(.jar) without putting the library on application framework layer? On 8월27일, 오후12시17분, Dianne

[android-developers] Re: creating a shared jar library

2009-08-26 Thread Dianne Hackborn
If you are creating your own device, you can have your own shared libraries that are separate from the framework. We don't support third party shared libraries mostly because we really don't want to get into dll hell and library versioning and such at this point. 2009/8/26 Mac xosk...@gmail.com

[android-developers] Re: creating a shared jar library

2009-08-05 Thread GiladH
Dianne/anyone, i would like to elaborate on the shared jar's memory model. my understanding is that: a. the code (read only) segment of the shared jar resides in common memory = code will be loaded once regardless of the number of apps using the shared jar b. the data (read/write)

[android-developers] Re: creating a shared jar library

2009-08-05 Thread Dianne Hackborn
Yes, it is just a regular shared library. On Wed, Aug 5, 2009 at 7:03 AM, GiladH gila...@gmail.com wrote: Dianne/anyone, i would like to elaborate on the shared jar's memory model. my understanding is that: a. the code (read only) segment of the shared jar resides in common memory =

[android-developers] Re: creating a shared jar library

2009-07-30 Thread Dianne Hackborn
Sorry, Android currently doesn't support third party shared libraries. On Thu, Jul 30, 2009 at 4:13 AM, GiladH gila...@gmail.com wrote: hey, i have several apps (each in its own apk, process etc) running at the same time on user's device. these apps are all linked to a single common jar

[android-developers] Re: creating a shared jar library

2009-07-30 Thread GiladH
tnx Dianne. after my post i have learned about the ability to 'inject' my shared library into open source Andro, as described in: http://android.git.kernel.org/?p=platform/development.git;a=blob;f=samples/PlatformLibrary/README.txt;h=5ce9d2f7756a0708e9fc0aed7845f3d69d4a6ae0;hb=cupcake i take it

[android-developers] Re: creating a shared jar library

2009-07-30 Thread Dianne Hackborn
That only applies if you are making your own device. On Thu, Jul 30, 2009 at 8:20 AM, GiladH gila...@gmail.com wrote: tnx Dianne. after my post i have learned about the ability to 'inject' my shared library into open source Andro, as described in: