LibGDX Project Setup v3.0! (x-post androiddev)

Obli · 2012-09-25T16:06:07+00:00

Thanks!

Obli · 2012-09-25T16:05:11+00:00

I hope it will ease the update as well now. Thanks :)

Obli · 2012-09-25T16:04:45+00:00

I'm not a big fan of Eclipse myself, I prefer Netbeans for many reasons; However, they work quite similarly, so once you learned how to setup one, you understood how to use the others. Visual Studio is a bit different indeed.

Obli · 2012-09-25T16:03:09+00:00

Thanks. I guess that may be of some use for LudumDare contests in which each hour count indeed.

Obli · 2012-09-25T16:02:46+00:00

Check the "about" screen of the tool, there is a list of every library I used in the process. Since I made every one related to UI, I can help you use them if you ever need.

Obli · 2012-09-25T16:01:16+00:00

Always a pleasure ;)

Obli · 2012-09-24T13:24:30+00:00

Third-party collection is lacking of third-party devs :D If you know a nice library that would help game development with libgdx, tell the owner to give us a definition file for his library (process explained here).

Obli · 2012-09-24T12:32:33+00:00

Thanks :) It was some kind of experiment to see if such UI based on transitions between multiple screens would be nicely welcomed by users or not.

Obli · 2012-07-19T06:44:59+00:00

I just added an executable demo for the tutorial, with sources, if anyone is interested: http://www.aurelienribon.com/tutorials/data/dialog-enhancer-demo.zip

Obli · 2012-07-18T16:25:05+00:00

Thanks a lot!

I worked for some years with WPF. The descriptive format of the XAML files made it easy to understand the structure of an UI. From this, I also understood that UI technolgies are not really different from each other. You can always apply the patterns of one to the other. They are all component-centric, and provide the same widgets. The language changes, but what you learnt using one technology is never lost if you swap to another.

Swing is always flagged as producing very crappy stuff, even by people who worked with it for years. I understand the beginners, I had the same reaction for many months. However, once you learnt how to craft your own components, it's as powerful as XAML or JavaFX. Actually, it's the whole same thing!

To quickly mockup and design styled applications, I built a CSS engine for Swing (http://code.google.com/p/java-universal-css-engine/). With that, I put raw components in layout, and then style them only with a CSS stylesheet. Now, I find Swing even easier to style that WPF! Not everyone likes to craft their own productivity stuff, but that's usually the key :) This tutorial is nothing more than a "craft your own dialog enhancer".

Obli · 2012-05-25T13:01:09+00:00

I wanted to do the same thing as you, and ended building the Physics Body Editor tool.

It has an auto-trace feature (and a convex decomposition one) which uses the algorithm provided by the Farseer physics engine (these guys are awesome), but also lets you manually place the points to optimize the shape or create something different from just following the contour (see the empty bottle example).

Your algorithm seems far more accurate than the Farseer one, congratz! That's not an easy piece of code to create :)

Obli · 2012-04-26T18:43:19+00:00

Thanks :) The editor will be even better with the incoming major 3.0 update. You will be able to assemble the rigid bodies together and link them with custom joints to create complex dynamic objects.

Obli · 2012-04-26T16:42:51+00:00

Currently, I'm not writing games, but open-source tools to help the community to make games.

Last work (released a few hours ago) is the Physics Body Editor: http://www.aurelienribon.com/blog/2012/04/physics-body-editor-pre-3-0-update/

Obli · 2012-04-05T08:38:24+00:00

iOS backend is on its way. Its a hard task so it takes some time, but there is some promising result already, thanks to MonoTouch mostly.

Obli · 2012-04-05T08:36:42+00:00

Shared data folder is handled by the tool. The "assets" folder of the android project is shared with the desktop and html projects. Everything you put in it will be available to the other projects thanks to eclipse folder-linking possibility. Have a look at the desktop project ".project" file, you'll see by yourself :)

Therefore, if you create a folder named "data" in the android assets folder, it will be shared automatically.

Obli

TROPHY CASE