I'm proud to anounce that MoSync 2.3 Beta has finally been released after some intense couple of months, with not much rest might I add . If you're like me, you don't have time for going through web pages and press releases to filter out what's actually in a new product release. So to make your life easier, this blog post will sum it up in an easly digestible format.
Devices:
We are contiously growing our profile database and as of version 2.3, there are 770 devices and counting, below is a list of some of them.
- 20 new Android devices
- 11 new Windows mobile devices
- 11 new Symbian S60 devices
- 6 new J2ME devices
- Moblin devices
New Platforms:
- Android
- Moblin
- Symbian S60 5:th Edition
IDE:
- Debugger!
- This is probably the most exciting feature in this release, you can now actually debug your programs through our IDE.
- Build configurations
- Debug and release configuration, or your own custom one(s).
- Heap settings in the IDE
- One missconception that might have occured the previous versions of MoSync might have been that you could only use 64 KB of memory, that wasn't actually true, it was just the default settinng. The amount of memory you could use could be configured through command line switches. We recognised that this was not an ideal solution, so with 2.3 this can be configured in the project build setting in the IDE.
- Selecting device directly in the BT dialog
- It's now even simpler to send your app to a device, when you select a device in the bluetooth search dialog, a dialog will ask you which device it is directly, which is one step less the previously.
- Sending to android devices through USB cable
- Android 1.5 does not have bluetooth OBEX support, so we added this feature for easy deployment on such devices.
API/Libraries:
- Improved touch support
- MAP library
- And lots of bug fixes and improved stability
Documentation:
Our documentation has been greatly improved, on the mosync website as well as in the editor. Thanks to our technical writer consultant Chris Hughes. Some of areas in which it has been improved are these
- IDE - Converting .fnt files to .mof files
- Building MoSync from the Windows command line
- Building MoSync from source on Linux
- Building Moblin runtimes on Linux
- Building MoSync from source on Windows
- Library - MAFS
- Library - MAUtil - Set, Map, and HashMap
- Library - MAUtil - PlaceholderPool
- Library - MAUtil - DataHandler
- Library - MAUtil - Graphics
- Library - MAUtil - Framebuffer
- Library - Framebuffer API
So there you go, if you haven't tried MoSync yet, now is probably a good time to try the only cross platform solution for developing mobile applications.





