next »

[autophile]

Hi all,

Today I downloaded 0.9.0-beta2 as recommended on the downloads page. Then I took a look at Xith in a Nutshell 2nd ed. to get started. But nothing matches up! In xith3d.jar, there's no Xith3DEnvironment, no RenderLoop... what gives? Is there any other way to learn Xith3D?

Thanks,

--Rob

[Marvin Fröhlich]

I Rob, welcome to Xith3D .

Actually 0.9.0-beta2 is the one, who's out of date compared with XIN. But don't worry. There's a matching version of XIN coming with the release (folder doc). But I would advise you to use the latest cooker, which matches the XIN (2nd ed) being online or even better: work with the current SVN trunk.

Marvin

PS: Xith3DEnvironment and RenderLoop exist in both versions. It's ExtXith3DEnvironment and ExtRenderLoop, which are missing in newer versions. But you can simply use Xith3DEnvironment instead of ExtXith3DEnvironment and RenderLoop or InputAdapterRenderLoop instead of ExtRenderLoop.

[autophile]

Okay... I downloaded 0.9.1-beta1-preview1, the Cooker edition. I still don't see it in xith3d.jar. There's no org.xith3d.render.base package...

Any ideas?

--Rob

[Marvin Fröhlich]

Okay... I downloaded 0.9.1-beta1-preview1, the Cooker edition. I still don't see it in xith3d.jar. There's no org.xith3d.render.base package...

It's in xith-tk.jar. (Though not very long anymore. I will move it to the core in the next days).

Marvin

[autophile]

Ahhh, ok, there it is. Maybe the Nutshell book could point that out:

1. Include xith3d-tk.jar.
2. include org.xith3d.render.base.*; in the source file
3. Use 0.9.1-beta1-preview1 (XIN 2ed says anything above 0.8.0 is fine).

I'm good at documentation, and I'd be willing to fix up XIN, but I'm not sure what my commitment would be to Xith. Basically, I came here because I'd like to make some simple games for learning the Japanese language.

Yours,

--Rob

[Marvin Fröhlich]

Maybe the Nutshell book could point that out:

1. Include xith3d-tk.jar.

Well, any lib coming with the release must be in the classpath. So there's no need to specially point this out. But at least it cannot harm.

2. include org.xith3d.render.base.*; in the source file

No. All the coding examples in XIN are snippets from the real examples, that come with the release. The cooker "release" doesn't contain it, but you can find them in SVN in the org.xith3d.xin package (xith-tk). All the necessary imports are used there.

3. Use 0.9.1-beta1-preview1 (XIN 2ed says anything above 0.8.0 is fine).

Yupp. This should be changed.

I'm good at documentation, and I'd be willing to fix up XIN, but I'm not sure what my commitment would be to Xith. Basically, I came here because I'd like to make some simple games for learning the Japanese language.

Your help is welcome. Please change points 1 and 3 (not 2). I need your sourceforge username to grant you SVN dev-access to xith-tk.

Marvin

[autophile]

About point 2 -- some people (like me! don't like to just load up a source file for an example and then run it. I like to type the examples in. So I don't refer to the sample files included in the release. Also, I doubt a n00b like me would even bother grabbing the files from SVN if they aren't included in the Cooker release. Then again, what's a n00b doing playing with a pre-beta?

In any case, I'm not sure what harm adding:

import org.xith3d.render.base.*;
import org.xith3d.render.loop.*;
import org.xith3d.render.*;

to the examples in the book would do.

My SF login is groovyjava.

--Rob

[Marvin Fröhlich]

About point 2 -- some people (like me! don't like to just load up a source file for an example and then run it. I like to type the examples in. So I don't refer to the sample files included in the release.

Well, there could be a note in XIN, that says: "If your crappy IDE doesn't complete the imports for you, then you can find them in the example .java files"

In any case, I'm not sure what harm adding:

import org.xith3d.render.base.*;
import org.xith3d.render.loop.*;
import org.xith3d.render.*;

to the examples in the book would do.

I don't want to fill up the book (and esspecially the examples) with unnecessary info. Only the necessary info should be in XIN, to reduce confusion potential as much as possible.

And I don't like the .* imports .

My SF login is groovyjava.

I've granted you dev-access to xith-tk.

Marvin

EDIT: Forgot to mention, that the example .java files are also available as a separate download next to the XIN download link on xith.org. This is exactly, what is normally shuipped with the book ni a release.

[autophile]

Eclipse isn't exactly crappy

You really would only have to include the imports once, just to establish the initial code. After that, if all your examples are modifications of previous examples, you don't have to include the imports, or even the class declaration. Just the changes.

Of course, now that I've got the initial problems solved, I ran into the openmali issue. Yes, I'm on OSX

Anyway, if you're absolutely dead-set against including the imports in the book, that's fine.

--Rob

[Marvin Fröhlich]

Eclipse isn't exactly crappy

I know . And it nicely fills in all teh necessary imports, if you press CTRL+SPACE when the cursor is after an "unimported" class name.

Of course, now that I've got the initial problems solved, I ran into the openmali issue. Yes, I'm on OSX

And I hope, you were able to solve it.

Anyway, if you're absolutely dead-set against including the imports in the book, that's fine.

Well, I think, it is ok to put them into "Chapter 0 - A Quick Rush". But they would only server as hints, where the imports normally come from. It is absolute overkill to add ALL the imoprts there.

Please remember to use Font "Monospace" size 9 for the examples.

Marvin

['n ddrylliog]

I know . And it nicely fills in all teh necessary imports, if you press CTRL+SPACE when the cursor is after an "unimported" class name.

Or alternatively Ctrl+Shift+O fix all missing imports.

Of course, now that I've got the initial problems solved, I ran into the openmali issue. Yes, I'm on OSX

Man, soon everyone will hate OpenMali. At least they should know that it makes Xith3D run faster compared to the original vecmath.