mk.jr.fan

Thanks guys for the help! I now do understand since making games is my focus I should, as you say, make games. But I do like the thought of going deeper so I will probably make that a side project. Thank you again for your help!

I wouldn't recommend this. Just go with a library from the start. A library such as slick doesn't just turn graphics into an image that you can willy nilly paint on a JFrame....it has its own windowing system. There is little advantage, even an educational advantage, with trying to go "vanilla" java at the beginning...especially with Sick because it is designed to resemble the Java 2D graphics API and is even easier to use than regular Java. Even if you are just trying to make a basic working plan, Slick and similar libraries are designed for fast development(they write the code so you don't have to), which is what you want in a learning or prototyping environment. 

From what you said it sounds like, by using premade scripts it will help me learn how to code games in java.

The reason for me making this game is not the game in itself. The game is like the icing on the cake. The cake is that I become a better program so I don't always have to rely on libraries. Now the reason I mention the use of a library is that it seems that coding for graphics is different from coding game logic (I don't know for sure since I have never had a chance to look at it). I feel that it would be best to learn from the ground up, and instead of using premade methods that don't always do what is intended, I can instead make games with my knowledge instead of using someone else's hard work.

Now if you disagree that learning from "vanilla" java is not the best solution please tell me why.

To port to Android, you must use the Android SDK or LibGDX or similar library. LibGDX is specially made for porting to multiple platforms. Trying to port a PC version to the MAC is one thing...they are fairly similar systems...but moving a PC version to Android is completely different because you have to worry about touch screens and lots of other Android "stuff". If you want to port to Android, that is something you need to think about now because then you should use LibGDX. In my opinion, since this is your first project in Java(even though you have some prior experience with games) you probably shouldn't worry about being cross platform and just getting your game out there, in which case I would recommend Slick2D over anything else.

So I guess a library or sdk will do the graphics thing for me or at least make it easier? Also would you know if that could be implemented for android if a library is used or would that be library specific?

Slick2D makes the graphics easier and is less laggy than "vanilla" java graphics because Slick has hardware acceleration. Games made in slick are "state based"...your menu, game, game over screen, high score screen, etc. would be different states that have their own independent update and render loops. Slick has lots of cool lighting effects and fade transitions that can make your game look way more polished. (My one problem with Slick is that it has trouble playing MP3 files so you will have to use a separate library for you audio playback and processing)

Thank you for the response! I think what I am going to do is make the basic concept of the game first just strictly with java. Later on when the game is pretty much complete I will try using a library later on for the graphics.

When that's done I will then try slimming it down for Android(but lets see how far I go first).

It is quite complicated to make a multi platform title with a low level library. Say that you want to do it all yourself, grab LWJGL and code the OpenGL stuff by your own. You'd have to make several renderers for your target platforms (mobile, desktop, etc) which it gets complicated really fast.
 
If you're going for multi platform from the start, better grab a library that already can do that stuff for you (I've heard good things from what Olaf Van Schlacht suggested, libgdx, though I haven't used it).

Well I was thinking of coding just for pc and was wondering if I needed to keep anything else in mind if I were to later port to mac or android.

I would recommend focusing on game mechanics: health system, collision detection and moving objects around. Java has a built-in library to do this. I spend time coding Java for 3 months really helps build my algorithmic problem solving skills in Java.

 

Take a look at the Canvas, JPanel, Component and Graphics2D class in the Java API. You will need these classes to form the base of a 2D game.

Interesting, I like your idea of just using plain java. I think what I might do is like you said get the basic game mechanics down first and maybe later on use the libraries and other stuff later on for the graphics.