Starting this weekend builds sent using the old plugin or an old project will fail. You will need to update the plugin to 4.3 (or 4.0.3 in NetBeans) or newer. This is an important phase in removing App Engine from our build stack and moving to a new system.Read More
I used to do a lot of enterprise consulting in the day and used to lecture a lot on J2EE (as it was known back then). A lot of that knowledge isn't as applicable even in the server side today, but the algorithms are surprisingly even applicable in mobile.
One of the algorithms I would explain a lot when teaching J2EE was the 2PC AKA Two Phase Commit.
The most common question we get about Codename One is: "Is Codename One Free". The direct answer is "Yes" but we don't want to mislead. You can work with the open source code, which is just as free as any other project. But it's not for the faint of heart...
The build servers have quotas so we won't go out of business. This is perceived by developers as "not free" but since no one else offers build servers I have an issue with that perception. To battle that perception we're increasing the build quotas.
I've been working on the new "Create an Uber Clone in 7 Days" book for ages. After so much work this is finally almost done!
We have a release date: August 16th (yes 2018!). You can already pre-order the kindle edition but you'd get it for free if you buy the print edition which for some inexplicable reason can't be pre-ordered.
Over the weekend we migrated a huge amount of code to the new build servers. In this post I'll try to cover three separate things. I'll explain the architecture/history and process of the migration. What worked, what didn't work and lessons learned. And finally how this will impact Codename One users moving forward.Read More
This is important! We will replace the entire build infrastructure of Codename One over this weekend. That means that you might see disruptions in service through the weekend but please report them to us as we might not be aware!
We are finally removing the last remaining pieces of the horrible mess that is Google App Engine from our backend code. This is a huge job and is sure to cause some disruption.
A few years ago a consultant convinced us to integrate Intercom into our website. In retrospect this was a mistake which I'll discuss in more depth below. We are migrating away from Intercom right now... That means that if you have an email address or ongoing chat history with us in Intercom it might get lost!
Worse. If you unsubscribe this might also get lost due to the migration process (sorry about that!). We're moving to a new far better system (crisp).
Last week I pushed out an enhancement to
ToastBar that changed the static
showMessage methods. I made them return the
Status object instead of
void which would allow more control of the toast message after it's shown. Unfortunately, I totally forgot that I can't do that without breaking some binary compatibility.