For downloading bundles I'm using LoadFromCacheOrDownload. It's works fine, but when I'm trying load bundle from cache, it start downloads bundle with same version again.
I'm look at Unity cache folder and found cached bundle(by resources name), but it still want to downlaod bundle.
Related
Is there a version package manager like npm, maven, nuget, pip? I just want my asset store assets to be saved in one way and when I open the project from a different computer everything will be downloaded with ease. Unity has a "package manager" but as far as I can understand it just helps you get the packages into the "Assets" folder. So, I don't see there is no package.json all anything like that what has been downloaded and triggered to download if not found.
I am sure there is a way to do it but I don't know how.
Unity's package manager uses /Packages/manifest.json to store it's dependencies as a JSON array. You can just copy-paste the file from project to project to have all those dependencies available from the start. Alternatively, you can just copy the individual entries for certain key packages, and use the defaults for the rest.
Just be sure that the packages are compatible with each Unity version you're going to be using.
I'm getting the error sqlite3.dll already exists under the filter when loading a newly built solution in Unity using ILL2CPP. This prevents my main project and the Unity Data project from loading. If I go into the project files and delete the reference as well as delete the dll from the directory both projects load correctly and my app deploys to the Hololens Emulator fine.
I do see a reference to the dll in C:\Program Files\Unity\Editor\Data\Mono\lib\mono\unity
I'm not using Mono to build as mentioned, I'm using IL2CPP. Why is this reference getting copied, what is it for and why is the error happening?
This is solved, I had sqlite3.dll in multiple directories in my assets folder. Deleting one of the dlls solved the issue.
I have my bundle jar file along with other code(component JSPs) in a package(under apps/mytest/install).
When I upload and build the bundle from my local to stage environment, I don't see the "apps/mytest/install" folder itself in crx/de and the bundle doesn't get installed in the stage environment.
I can see a post here URLrelated to this but cannot find "org.eclipse.equinox.region" bundle in any of our environments. Anyone has any other solution to resolve this issue?
I am working with GWT and I have some issues with the images. I need images outside my WAR file and, In order to make them visible in the application, I must put them inside the "target" folder ( I am using maven as well). The problem is that the target folder by definition is deleted every time recompile the project. This issue happens only in hosted mode, because when I deploy the application on Tomcat I can just change the server.xml adding the following statement
and it should read correctly images outside my WAR file(not tried yet due to another problem I have)
Can anybody give me some suggestions?
What is the directory structure of your maven project? Why is there a requirement for you to put the images in the target folder? Typically in a Maven project the items you put in the src/main/resources/static such as images end up in the built artifact.
I have searched a lot and tried several ways to do this, but am stumped. I am writing a desktop app (though I suppose it could also run in a browser) that allows an Android programmer to edit all of their dimens.xml files at once. I have created my own images to use in ImageViews as buttons. I am using different methods to access these images:
Some are referenced in the FXML file, like <Image url="#Icons/ic_launcher.png" />. The path is "src/Icons/". The path of the FXML file is "src/application/xxx,fxml".
Some are referenced in the css file, like "-fx-image:url("QuestionMark.png");". The css file and png file are in the same directory "src/MessageBox/"
Some are changed dynamically at runtime:
ImageView mButtonIcon = new ImageView("/insert_item_above.png");
The path of the image: src/
The path of the class: src/ContextMenuButton/
The above only works in Netbeans 7.4. None work when I run the app in Eclipse.
If I go to the dist/ directory and run it from any of the 3 methods, I see my images.
If I move the dist/ folder somewhere else, the only way I can get it to work is if I copy the src/ folder to the same directory and delete everything but the png and css files. So, I end up with:
+ F:/AndroidDimens
+ dist
xxx.jar
+ src
insert_item_above.png
+ Icons
ic_launcher.png
+ MessageBox
QuestionMark.png
So, the jar file has modified all of the paths to be relative to the src/ folder. My goal is to make the paths relative to where the jar file is. I tried to place the images where I would not need project related paths. But it must have made the paths something like "../src/MessageBox/QuestionMark.png" in the jar (relative to the project's dist/ folder).
Is there any way to fix this? Ideally, I would like all images to be in one directory. Then I could zip that directory, and someone else could just unzip it and run the app.
Thanks!
EDIT
Thanks to #jewelsea (in chat), I found that the problem was due to having an older version of JDK 7u13 installed with the latest one needed for JavaFX 2.2. Deleting the old version, and updating global variables that referenced it, solved the problem. No changes were needed to the default project settings.
Packaging Advice
Package all of your application's runtime class files and resources (fxml, css, png, etc) in the application jar file using the JavaFX packaging tools.
Using the JavaFX packaging tools is what NetBeans 7.4 does automatically during it's build process for JavaFX application projects.
Eclipse and other build environments will not use the JavaFX packaging tools automatically. I believe, if you use Eclipse with the recommended e(fx)clipse extension toolset for JavaFX development, then that toolset will, through its UI, provide you with the ability to use the JavaFX packaging tools to package your application.
There are 3rd party packaging alternatives for JavaFX such as the JavaFX Maven Plugin or the JavaFX Gradle Plugin which will also package your application correctly.
Whatever packaging tool you choose, test the packaging process by unzipping the files from your resultant jar and checking that all of the resource files (fxml, css, png, properties etc) are where you expect them to be in the jar's internal directory structure. This unzipping process is just a developer sanity check, you don't need to ask your end users do perform such an extraction.
Your end users can run your application as either an installed native application (JavaFX term self-contained application) or as a click to execute jar file (JavaFX term standalone program) and all of your application's resources will automatically be available from the packaged application, with no additional work required by the user.
Resource Access Advice
I advise not referring to a src path in your code (as you won't have a src path inside your distribution jar), css or fxml files, but instead refer to those paths relative to the root of the distribution jar or your JavaFX application class. For example, to load a scene style sheet in a JavaFX Application subclass, use a form as recommended by the JavaFX deployment guide - 3.3.4 Loading Resources:
scene.getStylesheets().
add(this.getClass().getResource("my.css").toExternalForm());