It's a provoking topic this, so be aware of that
If you follow Slick community from some time like me, you can see a lot of movements. Many people asking how to develop a game, how to fix a collision problem, how to deploy a webstart (it's all the same old questions). Forum Search seems to be forgotten by newbie and wiki
a strange word.
As community member, I've developed in years some games with Slick (Jpacman
, Cute Tower Defense
, You Can't Win
, Escape from colors
and Catch the cat
) and as first objective is always the same: get things done.
To do this, I've developed a little library MarteEngine and someone find it useful: this is great, because so many newbie are solving the same old problems (not in order, of cours):
- code organization,
So after years it's clear that Slick is not a library for newbie: you have a lot of things to master and some big problems (code organization and collisions) are note solved by library itself, but you have to (you have to do, not you could do) solve before have a game.
Note: this is not a Marteengine advertising, I'm talking about Slick library itself.
I want to propose a community effort to solve this problems, adding to Slick a library (slick-common, I don't care too much about this problem) to solve this common problems, with some little class.
And again, adding a link here on the forum to wiki, because wiki is great!
Plus: using common slick and slick, build some little games (pong, platformer, top down zombie survival, anything you want), put code on github and have fun on forking/propose idea on games.
what do you think about this?