We’re thrilled to announce the immediate availability of Codename One 7.0 (AKA Video). This has been our most challenging release to date. We constantly shifted the release date due to constantly shifting requirements and pivotal changes.
Highlights of this Release
Here are the highlights of Codename One 7.0
This is probably one of the biggest challenges we took to date. We now have one of the best cross platform WebRTC implementations. This took a lot of work and proved to be a huge challenge in every single platform.
With the new build app we want to change the process of building/working with Codename One. Right now it’s “just” a more unified settings/build experience but we plan to make it central to Codename One development. This will reduce the importance of the IDE plugins and of the build app.
It’s now possible to use proper web APIs and debug web based code embedded in a Codename One application. This also finally removes the problematic JavaFX dependency we had for our simulator and desktop ports.
CodeRAD might end up being the biggest feature of this release. It’s a higher level approach for building Codename One apps that makes building elaborate apps much easier.
New Website and SSO
This isn’t quite a Codename One feature but it’s a huge change to the way we handle builds, signups etc.
Those were the highlights but there were also a few important smaller features. There are too many to list but here are some that you might find interesting:
→ Sign in with Apple Support – this also includes some improvements to the OAuth support
→ New KitchenSink Demo
→ Multiple fixes to ParparVM (used in the iOS port) mostly for Kotlin support and wider support of the Java API
→ Improved CSS Image Border support
→ Tooltips Support
→ Safe download even when minimized
→ Labels (and their subclasses) now support badging
→ Arrow dialogs now work in a cross platform way
Codename One 8 will continue in some of the same directions but will also pivot strongly towards more open architectures.
We intend to build more upon the basic framework of Codename One Build. We think it’s better to use a single app to manage the build, settings and everything related to Codename One as opposed to using multiple plugins.
This will let us simplify the plugins and make them easier to update/maintain.
We also plan to migrate to Maven. This is already in progress and will materialize within the next couple of months. This will simplify some aspects of our build process and update/dependency management.
We will use CSS as the default framework effectively deprecating the designer approach. While the designer has many advantages ultimately CSS is the de-facto standard and with live CSS editing it’s a pretty compelling case.
We would also like to strengthen our desktop offering. We believe Codename One on the desktop has a unique value proposition for Java developers that no other framework offers at this time. This is especially true with our CEF support.
Finally, we intend to make it easier to build Codename One from sources and work with the open source code that’s already available.
How Can You Help?
If you think we are doing a good job and appreciate our help, please help us by:
– Signup/Upgrade your account
If your company can afford it, please take the time and upgrade to enterprise, this will allow us to work on the things that are important for your company!
Thanks for reading this far and if you have any thoughts/suggestions of any kind please let us know!