Well, no offense Amos, but If a game is a bit large, it will take a long time to download the entire file to your computer; even just your small COLLADA loader demo took about 5 minutes because of the xith3D and xith-tk jars involved...BTW, to get your programs to run (on Windows XP SP2) was to open my Task Manager and manually kill the "javaw.exe" program. Then the "java.exe" program opened up by itself.
But I take no offense here, as I am perfectly aware of what you're telling me and I above exposed the solutions to that. Though I'll make it clearer !now!.
Why was the COLLADA demo file large ?
- Xith3D + Xith-tk jars (a few Mbs)
- COLLADA schema jar (6Mbs), not needed anymore with Jibx (runtime takes something like 250Kb), plus generated COLLADA code, not needed anymore, also (don't now the size, though).
- The Demo code (a few Kbs)
- The Data (around a Mb).
What's the use of a setup with such big files ?
- Offline distribution : e.g. CDs, DVDs. In that case you really don't mind about an additional 10Mb. Really.
What's the solution for online distribution ?
- Dependency/repository system : Install Xith3D once, update if needed, and if user permits it.
This way :
- No duplication on user HDD : Xith3D run-time installed once
- Smallest download size : the app just has to say : "I depend on Xith3D version at least 3.0" (
) and it's fine.
Does that satisfy you, kukanani, or do you still have questions ?
About the javaw.exe / java.exe, I'm also very well aware of that, from our internal testings here in MagicSpark.org team and I knew the workaround, also. The solution I will apport to this will be to let the javaw.exe process die by itself.
Why wasn't it killed before ?
- It was there to clean up the temp files when the application quits/crashes
- It's the only way to display the System.out stream IN THE SYSTEM CONSOLE (e.g. if the jar was run manually in a linux console, "java -jar oneclickedjar.jar") : another solution will be provided, e.g.
* Either show the console if it crashes
* Or show the console by a special key shortcut (e.g. Ctrl + Alt + Shift + §
)
* Or suggest the user to send a bug report whenever the application crashes (reports sent automatically to Microsoft Corp.
no just kidding, the report address will be specified by the package creator).
Of courses these options will be decided by the package creator at build time. So things that may look annoying such as the bug-report tool can be disabled as the developer want (control, I want to give control to devs.. and to myself).
I welcome any questions and have answers ready. But it's hard to answer AND work on COLLADA at the same time
Projects
