What is codename one
2 likes1,239 views
Codename One was created in 2006 by Chen Fishein at Sun Microsystems to address device fragmentation. In 2010, Chen and Shai quit Sun Microsystems and formed Codename One to expand the scope of the project. By 2017, Codename One had grown to support over 10 releases, JavaScript, UWP, and desktop platforms with a developer community of over 40,000. Codename One provides a virtual machine, common API, IDE plugins, tools like a simulator and GUI builder, and cloud-based builds to create cross-platform mobile applications using a lightweight framework.
What is codename one
- 1. What is Codename One?
- 2. History 2006 2008 2010 2012 2014 2016 The Beginning Chen Fishein starts the LWUIT project at Sun Microsystems with goals of ending device fragmentation Open Source Sun Microsystems Open sources LWUIT at Java One A new Beginning Chen & Shai quit Sun Microsystems and form Codename One. The project has far greater scope and ambition than LWUIT 100M Installs Codename One grows & expands both in scope and use Maturity By January 2017 Codename One had 10 releases, added support for JavaScript, UWP & Desktop platforms. The bourgeoning developer community was 40k strong
- 3. What’s Codename One? ✦ Virtual machine for all devices ✦ API for all devices ✦ IDE Plugins to build mobile applications ✦ Set of tools, simulator, GUI builder, theme designer ✦ Cloud based build system to abstract device differences
- 4. What’s Codename One? ✦ Virtual machine for all devices ✦ API for all devices ✦ IDE Plugins to build mobile applications ✦ Set of tools, simulator, GUI builder, theme designer ✦ Cloud based build system to abstract device differences }
- 5. What’s Codename One? ✦ Virtual machine for all devices ✦ API for all devices ✦ IDE Plugins to build mobile applications ✦ Set of tools, simulator, GUI builder, theme designer ✦ Cloud based build system to abstract device differences } Fun Fact We came up with the name Codename One as a placeholder until we find an actual name Eventually we kept it because it makes these distinct tools act as “one”
- 6. Virtual machine for all devices ✦iOS doesn’t support Java & disallows JIT. Codename One’s open source ParparVM translates Java bytecode to C code so it can be compiled with xcode ✦Windows mobile works with a .net VM subset, Codename One ported iKVM (a Java .net runtime) so it will work with Universal Windows Platform ✦For web support Codename One uses TeaVM which translates Java bytecode to JavaScript
- 7. API for all devices ✦Common API abstracting mobile device functionality mainly UI ✦Clearly defined porting layer implemented for all supported platforms ✦Lightweight UI approach ✦Focus on simplicity, portability & common use cases ✦Statically linked
- 8. IDE Plugins ✦Codename One includes plugins for IntelliJ/IDEA, NetBeans & Eclipse ✦These plugins hide the complex details of installing/setting up Codename One ✦They are mostly a thin layer around the tools
- 9. Tools ✦Build tools - based on Ant, invoked by IDE for cloud builds and other capabilities ✦Device Simulator ✦Resource Editor/Designer - provides theming, localization, image management and old GUI builder ✦New GUI Builder - standalone GUI builder tool replacing the old one within the designer
- 10. Cloud Build ✦Macs, Windows & Linux machines in the cloud perform the actual native app build process ✦This is abstracted by the build tools to provide a unified experience ✦Removes the need to install custom software and configure it to very specific requirements ✦A major reason Codename One is so simple to use
- 11. Lightweight
- 12. Lightweight Frameworks Heavyweight Frameworks Codename One SWT Swing AWT Java FX Xamarin QT Appcelerator Lightweight vs. Heavyweight
- 13. Lightweight Frameworks Heavyweight Frameworks Codename One SWT Swing AWT Java FX Xamarin QT Appcelerator Lightweight vs. Heavyweight Lightweight Origin The term “lightweight” was popularized by the Swing framework to describe the difference between it and AWT. Heavyweight widgets in AWT were a performance problem as they required OS communication for every operation
- 14. Lightweight Frameworks Heavyweight Frameworks Draws widgets Native widget for every user widget Handles widget events & user input Thin API Layout, theming & all functionality is handled by framework Layout etc. are handled by OS Framework provides tools Mix of framework tools and OS tools Lightweight vs. Heavyweight
- 15. Lightweight Frameworks Heavyweight Frameworks Portable Matches OS Conventions Customizable Performant (debatable) Consistent (also in performance) Easier to build initially Easy to use Access to native OS features Lightweight vs. Heavyweight
- 16. Lightweight In Codename One ✦Allows native peer - e.g. Google Maps, Video etc. ✦Lightweight components can reside on top or below native peers ✦Enables the simulator and thus the cloud build! ✦Performant - uses gaming API’s (e.g. OpenGL) to get native performance. Performance is consistent across devices ✦Very customizable
- 17. I hope that this presentation: ✦Gave you a sense of Codename One’s origins ✦Gave you a glimpse of the breadth/scope of Codename One ✦Helped you understand the difference between Codename One and other tools you are familiar with ✦Clarified one of the most important aspects of Codename One: Lightweight architecture
- 18. Thank You