how to reference an asset in a library project_问答_开发者

In a class belonging to a Library proje开发者_C百科ct I call:

webview.loadUrl("file:///android_asset/info.html", null);

Unfortunately, this only works if I duplicate the file info.html into the Application's project asset folder as well.

Is there a way to tell an Android library code: "look for this file in the library's assets folder, not in the application's assets folder" ?

This answer is out of date, the gradle build system and AAR files support assets.

From the Android Docs:

Library projects cannot include raw assets

The tools do not support the use of raw asset files (saved in the assets/ directory) in a library project. Any asset resources used by an application must be stored in the assets/ directory of the application project itself. However, resource files saved in the res/ directory are supported.

If you want to include files from a Library project, you'll need to put it in the resources instead of the assets. If you're trying to load HTML files from your library project into a WebView, this means that you'll have to go a more roundabout method than the usual asset URL. Instead you'll have to read the resource data and use something like loadData.

This is now possible using the Gradle build system.

Testing with Android Studio 0.5.0 and v0.9 of the Android Gradle plugin, I've found that files such as

MyLibProject/src/main/assets/test.html

are correctly packaged in the final application and can be accessed at runtime via the expected URL:

file:///android_asset/test.html

You can achieve this by creating a symbolic link in the project's asset folder that points to the directory in the library project.

Then you can access as below:

webview.loadUrl("file:///android_asset/folder_in_a_libary_project/info.html", null);

Okay. Ive been stressing out and losing sleep about this for a while. Im the type of person that loves API creation, and HATES complicated integration.

There arent many solutions around on the internet, so im quite proud of what Ive discovered with a bit of Eclipse Hackery.

It turns out that when you put a file in the Android Lib's /assets folder. The target apk will capture this and place it on the root of the APK archive. Thus, making general access fail. This can be resolved by simply creating a Raw Java Library, and placing all assets in there, ie (JAVALIB)/assets/fileX.txt.

You can in turn then include this as a Java Build Path Folder Source in Project > Properties > Java Build Path > Source > Link Source.

Link Source
Click on Variables. and Add New Variable, ie VAR_NAME_X. location : ../../(relative_path_to_assets_project)
Click Ok

Now, when you build and run your app, the assets folder in the APK will contain your (GLOBAL Library) files as you intended.

No need to reconfigure android internals or nothing. Its all capable within a few clicks of Eclipse.

I confirm that Daniel Grant's approach works for at least the following situation: target project does NOT have an asset folder (or the folder is empty, so you can safely delete it). I did not setup any variable. Simply setup a LinkSource as follows (just an example) Linked folder location: /home/matthew/workspace_moonblink/assetsForAdvocacy/assets Folder name : assets

The "assetsForAdvocacy" is a Java project, (created with New- Project - Java Project) with empty src folder, and a new folder named "assets", which now provides the entire assets folder for the target project.

This is a fairly straightforward way within Eclipse to provide assets re-use across many different projects IF they do not already have assets, good enough to get going with. I would probably want to enhance it to become a content provider in the long run, but that is a lot more development.

My project accesses the assets with the following code: String advocacyFolderInAssets = "no_smoking/"; //a folder underneath assets/ String fn =advocacyFolderInAssets+imageFilename; Bitmap pristineBitmapForAdvocacy = getBitmapFromAsset(context, fn);

I use Motodev Studio 3.1.0 on Ubuntu. It would not let me 'merge' a new assets folder in the new assets-only project onto an existing assets folder in the target project.

If you want to use a setup where multiple derivate products are created from one library you might consider using svn:externals or similar solution in your SCM system. This will also do the trick that static assets like online help may be versioned seperately from the android source code.

I found this older question, it might help you, too.

This is the official way Google uses to archive this (from the above post): Link