THIS! THIS! thanks for saying that for me! :point:
Table is just a confusing name – it should really have just been called Container or something like that.
It is not a fix because JOGL supports applets. If you decide to drop JOGL, let us know so that I provide another backend based on JOGL 2.0 (which would be hosted and maintained by the JogAmp foundation if you refuse to do it).
I’d love to have the time get a Jogamp backend going, sadly i have other priorities. If you fork libgdx and want to work on a Jogamp backend i’d be happy!
I can do it before the end of this year but please can you tell me whether you would like to host it? I have several ports to do…
the level of pro-ness in this thread is rising… :persecutioncomplex:
What do you mean Jimmt? pro-ness? professional?
yup.
Group is the generic container. Table is a Group that lays stuff out in rows and columns.
Table is quite right name.
ok… i just decided to use libgdx 
Most of this thread was hijacked 
please close the thread, otherwise its going to become a full scale war 
libgdx ftw!
Not been around here long, have you? ;D
nop, lost my intrnet connection. Damn my ISP
Take me to Cuba!!!
LibGDX is indeed good, this was a question me and my partner in crime asked 8 months ago, make an engine, or go with libGDX.
We went the route of making an engine. After 24,000 lines of code later we are somewhat ready to makes games. It took us monday to friday, programming 9 - 5:30 for past 8 months to get to this point. We have an editor, our own scripting language (incomplete) and an Engine that can port to pc (incomplete) via LWJGL and Android (complete). And unfortunately after all this hard work, we don’t even come close to the features that libGDX provides.
Making an engine is not easy, it will require dedication, skill and utmost motivation. I recommend is go with libGDX or equivalent and don’t waste time, start making games.
If you’re still keen on making an engine i can recommend a few good reads.
Beginning Android Games - We started with this early on, an excellent book, based on early libGDX design.
Game Engine Architecture - Again, excellent read, it will pummel your mind on various ways to approach engine design.
Ericson Real-Time Collision Detection - If you’re making an engine, you will need good collision detection that’s both accurate and fast, this book is a very good read. Its examples are written in C though.
Programming Game AI by example - Very beginner friendly book, also a very good read for AI.
Game Physics Engine Development - If you plan to have physics and are not very good at math (like me) this book is also a very good read. The engine it develops is not optimal but it does give very good examples.
I hope I didn’t scare anyone off. Making an Engine can teach alot. This past 8 months i’ve learned more developing this software than I did in 4 years of University doing Computer Science.
It’s a fabulous way of learning. Sometimes learning is the only way to really do it right. Shame it costs 8 months but as you say… you learned more in that 8 months than you did in 4 years of Comp Sci. This is why engineering employers pay people with experience and no degrees far more than they pay people with degrees and no experience.
Cas
Not where i live, i hate my job prospects…
Wanting a job is a trick played on your mind by The Man. I’ve spent the last 20 years figuring out how to not have a job!
Cas
I describe my game project as my tunnel outta here. Writing game engines does not shift dirt.