I was thinking we would supply all of the jars (created when one runs Dist-All) in addition to this download. However, there has been several complaints in the past about the seperation of the jar files.
For people just wanting to get up and running with jME a single file seems like a nice solution, no dealing with the SVN or creating new libraries; just download it and it has everything you need to get up and running. In order to create a new jME project with that all one needs to do is point their IDE to the single jME jar file (which is why I included the source directly into it) and set their native path…
(also, its almost 1/10 the size of downloading from the SVN…)
My thoughts exactly, I guess I did forget to mention this download was in addition to the 'dist' jars that ppl should use when it time for distribution in their project.
Think of this more as a solution to 'get people up and coding' with the least amount of effort/time needed.
To create a new project; one simple needs to included this library in their IDE, code, clean and build, then copy the (included) lib folder under the created project dist/lib folders. So the actual command to run any project (outside of the IDE) would be:
The source is in the jar file, so to the end user it is just magically there (if they program in an IDE); or if they wanted to they could decompress the jar file and take the source out. In an IDE it should function a lot like the JavaDoc except they can view a read-only copy of the source it would have been generated from (which I really, really like libraries that do).
How would you feel about reversing that and having the JavaDoc as a separate download?
I think there is a minor problem with the way I have packaged up the download. Any SWT tests (unless the user is on OSX) will fail, this due to only the one swt.jar copied into the lib folder.
I do really think having a complete download (that's ready to test, program with) is very nice to have (some ppl can't use SVN…), and apparently I am not the only one since there is over 1000 downloads and it hasn't even be up for a week.
As I see it we have 6 options (with the current setup):
Create OS specific downloads for Windows, Linux and OSX
Leave it the way it is, and if someone needs different swt.jar(s) have them DL from SVN web-page
Remove the OSX carbon swt.jar and replace with windows (this still requires previous option)
Wait until next time to package then do previous option
Remove the swt.jar from the complete download all-together and have ppl use SVN to test/program with it.
Previous option, but instead create specific SWT download w/ all swt.jar files
(I wish I had seen this issue before deploying...)
(if we could specify different jar files for different OSs in the manifest then this wouldn't be a problem anymore, does anyone know if that's possible?)
Just letting everybody know that I started working on jME3.. Two things:
1) You will probably need a DirectX10 compatible card (GeForce 8000, Radeon HD)
2) It will be made mostly from scratch with some general parts like math & frustum culling taken from jME2.
That's all I have to say for now.
I thought the point of clearing jme2 was to get consensus on what jme3 would be, etc?