To understand libGDX, an open-source Desktop/Android/BlackBerry/iOS/HTML5 Java game development framework. As with all abstractions, the convenience of an abstraction depends upon the convenience of its examples. Furthermore, there is a proportional relationship between the flexibility of an abstraction and the number of examples needed to demonstrate said abstraction. When a sufficient number of examples properly demonstrate an abstraction's use cases, this eliminates the possible mismatch between what the abstraction provides and what one needs to accomplish. However, if examples are lacking then one finds themselves in the position of fiddling, blindly asking for help, or --most reliably-- working to understand that which the abstraction is abstracting. This last approach initially takes the most effort but, in any case requiring full use of the power of an abstraction, easily makes up for the time wasted later from endless fiddling and awaiting post responses on message-boards. The forthcoming posts will document this last approach as applied to libGDX.
Next.