Exporting problems! Please help!

[gasquakee]

Hey guys,

So my experience with jSFML has been absolutely superb but I'm having some problems whilst making a jar. I can make my jar and and run it but none of my assets go through; Instead, they are replaced with White rectangles. Does anyone know what's going on? I'd really appreciate it! Thank you.

[Nexus]

The paths to the assets are probably wrong. Make sure they're still valid in the JAR.

[pdinklag]

Indeed, as Nexus said, the file structure of your exported version seems to be different from your IDE.
How do you load resources, via classpath or from the file structure? Maybe post a little code sample, giving us some insight on the way you load your textures, for instance.

[gasquakee]

I load resources like this:
try {
   spritesheet.loadFromFile(Paths.get("res/spritesheet.png"));
} catch (Exception e) {
   e.printStackTrace();
}

and I add a class folder in eclipse called "res"

This seems right to me? Could it be how I export it? I export a runnable jar file and I extract libraries into a generated jar according to Eclipse.

side note: is jSFML still being worked on?

[pdinklag]

spritesheet.loadFromFile(Paths.get("res/spritesheet.png"));

This means that you are reading the texture from the filesystem, not the classpath.
In your released version, you would need a directory called "res" with the file in it, it won't work in the jar.

You need to load it from the classpath / jar, using the loadFromStream method using the path to the resource (look that up, easy to find information ).

side note: is jSFML still being worked on?

Ouch.

At the moment, no. Most SFML 2.2 changes had been incorporated, but I never made an official build because I had no environment set up. I completely lost track of what's going on when 2.3 was released, because I have no use for SFML myself at the moment.

I also said goodbye to Java after quitting a job in summer, so the situation is not exactly great for JSFML.
If somebody's willing to take over, that'd probably be best for the project. For now, I can only help with what's there.

[gasquakee]

Thank you!

Also, though, sad. How would you say the current version of jSFML is though? I've used it for a little over a month now and I like it quite nice. When do you think it will be too old?

[gasquakee]

Hmm, I've replaced what you've told me to and I can run it through CMD as a jar but I cant run it via double click?

[pdinklag]

Thank you!

Also, though, sad. How would you say the current version of jSFML is though? I've used it for a little over a month now and I like it quite nice. When do you think it will be too old?

The problem is that bugfixes from the updated SFML do not go in there, so whatever problems SFML 2.1 had are in the current JSFML. It works pretty decent as far as I can tell, though.

Of course, SFML 2.2 and 2.3 brought an improved API, too, which is not in JSFML.

Hmm, I've replaced what you've told me to and I can run it through CMD as a jar but I cant run it via double click?

That's system specific, you'll need to associate JAR files to Java. If the setup doesn't do it automatically (I think only the JRE setup does, not the JDK one), then you have to do it manually.

That goes for customers, too.

You could alternatively create a batch file for launching it, or use launch4j to create an executable launcher.

[gasquakee]

Yeah, I was thinking about batch I just didn't know how many OS' supported it. I'll look into launch4j.