One of our enterprise customers needed help with file upload from the desktop. E.g. in his Codename One app running in the browser or desktop he wanted the ability to drag a file. Somewhat like we can drag a file into gmails compose window.Read More
We just flipped the switch on
InfiniteContainer which is now more synchronous and complies with the EDT policy by default. We are already back to committing changes and have been busy updating with all of the things that didn't make it into 3.5.
This is a feature Steve added way back in June but I didn't get around to documenting it. Build hints can sometimes get "unwieldy" e.g. in the case of
we sometimes have pretty verbose values.
When we initially designed the cn1lib file format we looked at jar files as a starting point. We wanted a way to distribute binary libraries that support the native code access, restrictions and ideally code completion.Read More
We are thrilled to announce the immediate availability of Codename One 3.5!
Version 3.5 is a huge release that includes the long awaited Windows Universal Platform (UWP) support and brings the new GUI builder out of beta.
When we announced Codename One 3.4 we also announced a major animation overhaul. This was an important milestone that we didn't fully actualize until this past week...Read More
We are deep within the 3.5 code freeze and this adds up to a remarkably busy week, we've got an even busier week with the release itself so I'll get right down to the questions...Read More
I wanted to write about the new kitchen sink demo which I'm trying to finish...
But I haven't finished it yet as it's such a major undertaking. As part of that work I wanted to show some code that downloads themes and didn't want to use the venerable infinite progress indicator which I generally dislike...
It's tough to pick up a new toolchain like Codename One. There's so much to learn...
A lot of our developers come from the Android world and even though Codename One is much simpler than Android porting the first app to Codename One is still painful.
Today we are going into code freeze for Codename One 3.5 which is due one week from now, because of the fast release cycle we don't need more than a week of code freeze to stabilize our current release.
The code freeze applies to the Codename One libraries and ports as those are the parts that are inherent to the release.