Prime31 UIToolkit Multi Resolution GUI Solution Ready for Use...and it's free

[3Duaun]

simply awesome, very generous of you. I love my Prime31 plugins!

[prime31]

@TaintedLemon, that should work just fine. You can use the getButtonForScreenPosition() method and if it returns something other than null ignore the touch and don't shoot off your ray.

[prime31]

Added a little note about the awesome animation system baked into UIToolkit to the main post...

[itech]

Thanks !

[Barbur]

I am starting to be a Prime31 fan! Thanks a lote Mike!

[smkamran]

Amazing product. I would love to use it in my projects.

[RolfBertram.com]

Not sure if this info makes sense here regarding implementing it in this GUI system, but I found a tutorial on how to apply a text to a texture of any 3D shape, in this example a mug. I wonder if this makes sense to use for showing score on a game object, since there is mention of some slowness of this method in the tutorial. If someone knows more about the possible slowness issue, and the usefulness of this method for frequently updated text, like a score, on a 3D surface, please comment.

http://blog.almostlogical.com/2010/0...ender-texture/

[mudloop]

Looks awesome.

Small question, in this code example:

var playButton = UIButton.create( "playUp.png", "playDown.png", 0, 0 );
playButton.highlightedTouchOffsets = new UIEdgeOffsets( 30 );

Could the images also be referenced with an index, to avoid string creation (GC) and string lookups?

[prime31]

@smag, you could assign the uvRect directly. Most controls have "raw" constructors that don't take in any strings. we purposely went with the string route though in order to keep the code readable, work across SD/HD and most importantly so the texture atlases can be totally rebuilt/modified at any time and still work with the same code. Those pesky tradeoffs...

[Mousey]

This looks great - many thanks Prime31!

Not to go too off topic (maybe someone can point me to a seperate thread), but what's the problem with string creation / lookups, as mentioned by Smag?

[mudloop]

@smag, you could assign the uvRect directly. Most controls have "raw" constructors that don't take in any strings. we purposely went with the string route though in order to keep the code readable, work across SD/HD and most importantly so the texture atlases can be totally rebuilt/modified at any time and still work with the same code. Those pesky tradeoffs...

I see the benefits of that, but if each image would get a number in the atlas, you could keep those benefits (except readability, but that can be solved by the user if they use enums). However, this would only work well if the TexturePacker keeps the order of the images in it's exported files consitant.

This looks great - many thanks Prime31!

Not to go too off topic (maybe someone can point me to a seperate thread), but what's the problem with string creation / lookups, as mentioned by Smag?

Well, strings will increase the garbage that the garbage collector has to collect. So the more strings you use, the quicker the GC has to kick in, which can cause small hitches.

In this case however, most of these things will be setup at the start of your scene so it shouldn't be that big a deal.

[Mousey]

Thanks Smag.

[prime31]

I see the benefits of that, but if each image would get a number in the atlas, you could keep those benefits (except readability, but that can be solved by the user if they use enums). However, this would only work well if the TexturePacker keeps the order of the images in it's exported files consitant.

TexturePacker will reconfigure the order depending on the new sprites added to best fit the setup. Believe me, I tried every way possible to go without string creation and the cost of making a few strings at startup outweighed every other option. They all required some post or pre processing which just isn't worth the extra work. Letting the GC do it's job and collect some strings at startup and keeping a nice, simple workflow far outweighed the alternatives.

[Gigiwoo2]

@Gigiwoo,

* ...absolutely not going to be in the Asset Store. We want this to be a community project, not something the we alone support. It was made to be easily extensible and we would love to see what creative controls can come from other folks using the library.

Fantastic! Brilliant idea!

I've co-run an open source project for many years now (www.delta3d.org), so I've been where you're about to go. It is a really enjoyable process - one that can lead to many opportunities, is personally satisfying, and is at the same time very challenging. One of the neatest thing about a project like that is when you start getting user submissions and even better, major adopters/users/partners.

I haven't used GIT yet, but I guess now is as good a time as any to learn it .

Gigiwoo

[prime31]

@Gigiwoo, sounds like you have some work to do. Here is your todo list:

1. grab yourself a copy of Gitbox (free) or Tower (paid but really nice)
2. make the container objects you were asking about previously
3. send over a pull request

[jjobby]

I'm currently experimenting about GUI solution for mobile development. You've come at the right time.

Thank you very very much for this awesome release!!!

[Eskema]

This prime guy is the number one, once again a really complete solution and this time for free

[afalk]

Looks like an outstanding start Prime! Downloaded the files this morning and looking forward to experimenting with your system and to the Container addition you're working on!

Thanks again!

AF

[mindlube]

Add the exported bitmap font png to your texture atlas in Texture Packer and you are good to go, just be sure the image name is the same as the .fnt filename.

This is a nice feature - to be able to embed font bitmaps in a texture atlas! very cool

[leonardoaraujo]

Very nice work! One question guys does this GUI system works on Android (I did not tested on Iphone yet)