So for the first time in a few years I tried AWT

Performance Tuning
#81

I vote none of 'em.
I’d rather see LWJGL (or JOGL-JOAL-JINPUT if that’s your fav. lib) as the defacto library for games and speeding up AWT using the platforms best supported API, which is DX on windows.

#82

Hate to say it but i do agree with Cas on “the linux market”, which is to say I’ve had my doubts for a long time that there really is one.

For me it comes down to the simple fact that most linux devotees are deveoted to it because its free. Noones yet proved to my satisfaction that those folks will pay for anything, let alone games.

OTOH the Mac market, albeit small, is very real and companies have succeeded financially specializing in it. (eg Bungee before MSFT bought them out.)

#83

…and Mac AWT performance is lagging even behind Linux :frowning: (last I heard)

Hurrah for OpenGL :slight_smile:

Cas :slight_smile:

#84

Would (some of) you guys stop mixing up AWT and Java2D.

AWT = desktop interaction, focus management, clipboard, etc.
Java2D = imaging operations, rendering, printing, text, etc.

#85

There is a grey area between AWT and Java2D where the blitting happens…

Cas :slight_smile:

#86

[quote]There is a grey area between AWT and Java2D where the blitting happens…
[/quote]
Can you explain what is that grey area you are talking about?

#87

[quote]Hate to say it but i do agree with Cas on “the linux market”, which is to say I’ve had my doubts for a long time that there really is one.

For me it comes down to the simple fact that most linux devotees are deveoted to it because its free. Noones yet proved to my satisfaction that those folks will pay for anything, let alone games.
[/quote]
Well, there are many reasons why me and some of my friends are using Linux ,and none of them has anything to do with Linux beeing free (as in beer). Some of us buy packed boxes few times a year. I don’t think it is very productive to generalize rather big userbase (percentage of the market is maybe small, but numbers are getting big enough). As I’ve said before, linux consumer desktop market is in it’s infancy, but there are players out there that are making great progress both in usabillity and instaled base. They need good games, Java needs new platforms. Instead of being pesimistic about whole Linux story, why doesn’t someone from JGO try to talk with people that make a living selling (see, some people do pay for Linux, an some do pay monthly fee for having access to easily Click and Run;Webstart like apps) consumer Linux Desktop. Like Lindows/Lycoris. Try to get a promo or something. Try to use their channels.

#88

The grey area is the fact that Java2D and AWT are inseparable, which speaks volumes about its integration. Is blitting into a window an AWT function or a Java2D function? Is blitting into a surface AWT or Java2D? What’s the difference? etc.

wrt Linux - best move the discussion about Linux markets to General Business Discussions and start a thread there about it.

Cas :slight_smile:

#89

[quote]The grey area is the fact that Java2D and AWT are inseparable, which speaks volumes about its integration. Is blitting into a window an AWT function or a Java2D function? Is blitting into a surface AWT or Java2D? What’s the difference? etc.
[/quote]
I’m puzzled. do you ask these questions in order to add weight to your statement, or to get answers? I can’t find.
imho, blitting to a window is AWT and blitting to a surface is java2D. the role of awt should be to blit surfaces to the windows.
Are there hard links between java2D and AWT? I mean, is it impossible to use java2D without AWT, or the opposite? I haven’t found things that would tie one to the other.*

edit
‘the role of awt’ is of course not only to blit what java2D has done, but i was talking of the awt/j2D relation only., excluding its main purpose

#90

Any blitting (or rendering operation) is Java2D.
The creation of that window (as well as positioning, event handling, etc), however, is AWT operation.

Actually, Java2D and AWT are separable, and will likely even be in different libraries (.so, dll) in the future releases.

OK, I’m done with the hijacking the thread =) Feel free to start a new thread if you have any questions on this topic…

#91

blit is another word for moving pixel ( bits ) from one location in the video mem to another location, it doesnt matter which language which tools or what the heck else u use.

blitting is nothing special, every serious game developer knows it.

to blit or not to blit, thats the question 8)

#92

Hahahahah… AWT. This really cool windowing toolkit by sun that uses other windowing toolkits on other platforms. Morelike windowing windowing windowing tool kit of a windowing toolkit.

#93

[quote]blit is another word for moving pixel ( bits ) from one location in the video mem to another location, it doesnt matter which language which tools or what the heck else u use.

blitting is nothing special, every serious game developer knows it.

to blit or not to blit, thats the question 8)
[/quote]
Just nit picking here :slight_smile:
Blitting doesn’t need to be vram->vram, I think it’s a generic term for copying blocks of data in memory (‘blit’ is derived from BLT (BLock Transfer)), possibly with an operator in the process (such as XOR). Blitting can also be ram->vram or vram->ram.

Erik