next »

[ChrisE]

So, I'm about to the point where I'd like to start having debug information overlayed onto my screen. This information is likely to be extended into a full-blown context-menu system eventually.

Anyways, the three options seem to be using the HUD, using the UIWindow to stuff Swing components into poor old Xith, or using AWT heavyweight components directly onto my Canvas3DPanel.

Which of these is going to be easiest? I'd personally prefer to use AWT or Swing, but searching around on the forums here has lead me to believe that Swing integration is a major performance hit.

Any advice?

[Marvin Fröhlich]

Only one advice: Use the HUD. It is fastest and very easy to use.

Marvin

[ChrisE]

I'm using the HUD, but was wondering...

What's the function of the UIWindow class? The impression I get from the docs is that it lets me embed Swing stuff in Xith, and also lets me interoperate with other Swing components that might be external.

As I've got Xith running in a pane among other things in my application, it would be cool if I could use the documented drag-and-drop functionality to deal with the rest of my app. Thoughts?

[Marvin Fröhlich]

Yes, The Swing integration is working. But I would only advice you to use it, if you really need the interoperability with other Swing components. Normally you will want your application/game to atually look like a game, which will not be possible with Swing in an easy way.

Swing integration is comparably slow. The HUD is easy to use and fast. And it interates with your game nicely.

Well, it's your choice.

Marvin

[ahealingman]

I believe I read somewhere a month or so ago the major performance issues with swing were resolved. Not suggesting it should be used but just that performance shouldn't be as much of a consideration as it was before

[Marvin Fröhlich]

Hmm.. I don't remember that. But the Swing integration cannot be as fast as the HUD, since it includes a lot of full pixel buffer copies. The HUD does that very efficiently.

In the end it's just a matter of what you need. If you definitely need to Swing interaction, go with it. But if you'r making a game, you won't need that and you should get as much performance out of the engine as you can. Than the HUD is, what you need.

Marvin

[ChrisE]

Regrettably, my project isn't much of a game--perhaps I'll add something as an Easter Egg. I'll try and get cleared to post some shots. Thanks!