We are preparing for the 3.5 code freeze which should go into effect on July 26th. We are still not sure about the full set of features that will make it into 3.5 as the release is pretty close by now. However, we already have some cool tentative plans for 3.6 and beyond that we are already sketching out.Read More
I blogged about peer components all the way back in 2014 trying to explain basic facts about their limitations/behaviors. A lot of those limitations are inherent but over the past year or so we've been thinking more and more about the z-order limitation.Read More
A common issue we get from developers relates to minor differences between devices which are often very hard to quantify. They are also very hard to explain to the developers in some occasions. One of the biggest points of difficulty is density which is a very hard concept to grasp and it's often hard to know which image will be used from the set of multi images or how many pixels will be used for 1 millimeter.Read More
We just updated the QT and Xamarin comparisons to Codename One that we did a while back. Those comparisons now include a property cross comparison section. Property Cross is really valuable for comparing the differences between various cross platform development solutions and Codename One has the smallest implementation (in terms of lines of code) by far!Read More
June just ended and we are starting the final stretch to get 3.5 ready, there is a lot on our table right now so most of the work in the coming month will probably focus on stabilizing the GUI builder and fixing the remaining issues for 3.5.Read More
The charts demo is one of the most elaborate/messy demos we have as it was derived/ported from an aChartEngine demo. Since the Codename One charts are themselves a derivative of aChartEngine this makes a lot of sense but the demo is a bit big and hard to follow.Read More
ToastBar was one of those API's I didn't know I needed and yet I became addicted to it...
Ever since Steve came out with the
ToastBar I constantly catch myself typing
Display.show only to delete that to use the
ToastBar. It's both really easy to use and more consistent with modern mobile UI design.
Last time around we compared Codename One to Xamarin and this time around I'd like to compare Codename One to what is probably the market leader: PhoneGap/Cordova. If Xamain is big then Cordova is huge, it is so prevalent that it is often the default assumption when people mention cross platform today.Read More
InfiniteScrollAdapter revolutionized the way we think about Codename One. Up until their introduction we advocated lists for large sets of components and this is no longer the case.
InfiniteContainer has a controversial feature even within out team. It violates the EDT on purpose...
We covered the new
Accordion component last week and just started using it in a demo for which it was very suitable. As we were working with it we discovered that it was missing some core methods to remove an
Accordion entry or change it's title. But worse, was the fact that a delete button in the title wouldn't work!
The crux of the issue is in the fact that lead component doesn't support excluding a specific component within the hierarchy from it's behavior so we set about to fix that...