Latest messages

I take back the transitions comment, now that I've seen it in the javadocs ;)

kind of lonely here... but anyways... I actually found you guys a few months ago.  I'm really interested in the project, I worked on Synclast, which was very similar on the canvas based UI toolkit level, and I wrote the XML->UI layer with databinding and animation support and stuff like that that.  Anyways... the company didn't allow that stuff to get opensourced, and I don't work there anymore.  Which brings me here!  So ya, like minds for sure, and now I'm having to choose between kuix and lwuit for the project I'm about to start.  The CLDC1.1 requirement might kill the lwuit option.  But some of the simple animation stuff would be great in kuix.  I don't need 3d cube transitions (haha) but a sliding screen, or sliding component sort of thing would be a great visual indicator to the user, as far as action goes. 

I do have a question though, looking through the tutorial a few times, I'm curious about css image resolution.  Is there a way to say:  url(blah.png) and have 'blah.png' get loaded from a new datasource? Similar to how you handle the DataProvider solution, but perhaps with Image, or even Object resolution services rather than just String.  That would allow me as a developer to download new XML interface dependencies OTA, and have a much more dynamic application.  Of course some way to cache those would be even better, but that can always be handled in the implemented ImageDataProvider (or whatever) implementation of the application developer.

beyond that, the application I'm working for is for a large company with lots of carrier deals here in the US, and there's no way they'll allow their application to be opensourced.  What kind of private licensing to you guys offer for this case, which obviously doesn't go with the GPL, 'use our source / show your source' mentality?

thanks!

-pandora

To be able to implement in Kuix the best things to be in phase with developers needs, we would like to question you.

- What do you think about Kuix ?

- Do you think it's easy to use or a nightmare ?

- What do you think about the XML/CSS approach at runtime ?

- What do you need to have and Kuix doesn't have ?

- Do you prefer to use an other UI Frameword ?

I just wanted to post a big THANK YOU for a change, instead of my normal ranting and raving about bugs and features. I must say that Kuix seems to be the best thing since sliced bread that I have come across. Makes mobile UI development  a breeze, even though the document is a bit lacking at the moment. And even that promises to change as soon you get the source code out in the open. I for one am eagerly waiting for getting my hands dirty with the code!

But anyways.. Just wanted to give credit where credit is due, so again, thank you for the excellent UI framework guys !!

Kalmeo welcomes all Kuix developpers!

We hope that Kuix will help you to create efficiently new mobile applications. However, if you have some improvements ideas, feel free to post in this forum. We will take them into consideration for further releases.