You might know from the site comments or the SourceForge bug tracker, that the current ui library has some issues with Nokia S40 3rd edition phones since this models use 3 commands instead of the normal 2.
We were planning some major changes in the user interface library, and we are now finishing the first part of it that addresses this issue.
The new ui library will use the concepts of Desktop, Window and Decorator, managing the screen in full screen mode and handling all the painting.
The Desktop is like the LCDUI Display class, it handles the painting of the window title and the commands.
All the classes that were previously Canvas subclasses such as the dialogs, menus and data lists are now Windows that get painted in the Desktop.
The desktop is divided in four regions: title, content, first command and second command. The commands are optional, you can have none, one, two or more.
Each region has an assigned Decorator, which is responsible of drawing the background and managing the overall aspect of the region.
The library will provide a default decorator that simply paints the background with a solid color, and also an experimental one that will draw an image as the background using any mode ( mosaic or stretch).
Thanks to the way the views are defined (with XML), you don’t need to change anything in your application (if you use the default decorator) just compile it against the new ui library.
We will publish soon a beta version of the library and post it here for download.
This is a minor, though important, change.
It is now fixed and tested on Windows XP Pro. We did not remember that there still people (developers) using Windows
We have not changed the release on sourceforge, it remains 3.0, but we have removed the binary and source files named 3.0 and uploaded new ones with version number 3.0.01:
We have also added a new binary file called openbasemovil-3.0.01-buildtools.zip that contains only the jar files for the build tools, so to fix the bug in the binary distribution you can download only this one and override the libraries in the 3.0 files.
Sorry for the inconvenience, and thanks for your help.
PS: Try Ubuntu! you wont be disappointed.
Thanks to everyone, and thanks to the SourceForge staff.
It is ephemeral, but it’s great!
The project news for the OpenBaseMovil 3.0 final release is now in the SourceForge home page.
Just for the posterity a snapshot:
We were thinking about which application seamed the best choice for creating the Quick Start Guide and the sample application.
It should be not too big, but useful, and make use of a good deal of the platform.
It should also be helpful to compare the effort needed to create an application from scratch and using our framework.
So we finally choose PasswordKeeper, a KeePass like application that has J2ME version at source forge (KeePass for J2ME).
Here are a few quick facts about the size of the project, that I think that speak aloud:
UPDATE: the table above represents some statistics about the SOURCE code of both applications, not the final .jar size of the application itself. We are trying to picture the development effort.
|PasswordKeeper||KeePass for J2ME|
|Number of files||20 (5 java, 1 XML for the views, the rest resources)||71|
|Size in Kb (approx)||94 (includes images)||237|
|Lines of code||2326 (807)||6835|
The number of 807 between parenthesis is the approximate number of lines of code that are actually part of the application and not of the template, so the ones that you really create.
Have some comments?
Finally, we are releasing OpenBaseMovil 3.0.
This version fixes some bugs found in RC3 and adds a lot of interesting things:
- app-template is an application template from which you can create the skeleton for your application, simply running ant in the folder will ask you a few questions and create your new project.
- PasswordKeeper, this is a sample application built with the app-template. You can download a working version for you phone at the download page and also the source code to learn how to create applications.
- Best of all, the Quick Start Guide which is also available for download. This guide explains how to use the app-template and follows the process of PasswordKeeper.
With this release we hope that you have every thing you need to create your own applications, and don’t forget that the BaseMovil developer program is open (in a yet restricted beta) allowing you to to get access to the sync engine, application and database hosting, and more… for FREE for developers.
Just a quick note, I wrote PasswordKeeper in about 8 hours while I created the Quick Start Guide and refined the app-template, so we could say that it took me about 4 hours to write the entire application. It may contain bugs, it’s a 0.1 version, but I think that the result is a good one for just 4 hours.
We would love to hear from you, your applications, your thoughts, feature requests… feel free to use the comments and the project page at Source Forge.
We have released another version of the library, the RC3.
It fixes a bug in the new table creation methods and one in the build system.
We’ve also made some improvements and moved some classes from the util library to the core and bluetooth libraries.
We have done this release so fast because the bug resolved in the Table class is important enough, though it could be easily “workarounded” we felt that it should be fixed at once. It was only one missing line of code!
We are working with the application template and the demo application. They are going to bring some minor changes to the database engine. We will release them (the template and the sample) soon, along with the final version 3.0.
We’ve been working hard to publish this 3.0 RC2 release, because this is the first complete release of the OpenBaseMovil platform.
This means that you can now create applications with all the supplied files that you can download at Source Forge.
We have finally included the ui library, along with the net and util libraries and much, much more. This includes some bonuses such as a barcode scanner interface to Microvision Flic barcode scanner and also a NMEA compatible driver for bluetooth GPS antennas. You just start them and register your class to listen for their events, and then you just have to process the events with the data (barcodes and gps locations respectively).
So what’s next? We’ll be releasing soon also a template application and a demo application built with it, along with a series of posts here with a tutorial on how to build applications very quickly. So stay tuned, and subscribe to the feed!
You have been very helpful and very inspiring through your commens and emails, and I encourage you to keep that way.
Please, leave your thoughts and digg it if you like it!
We have finally released the first “almost complete” version of OpenBaseMovil.
You can download it at Source Forge.
This version includes the awaited OpenBaseMovil-db J2ME Relational Database Engine, along with all the dependencies and almost all the build tools.
We have included some changes in the database structure and api compared to the current commercial version, since the standalone open source version needs methods to create the database manually while the commercial version gets the structure over the air with the sync engine. But you can consider it a very stable release.
In the next one, RC2 which should also come this week or earlier next week, we will include the remaining libraries and tools. The most important one missing now is the ui library.
With RC2 we will also publish some samples and templates.
And finally, after your valuable comments we will release the final 3.0 version which should be almost the same as RC2.
Thanks to all of you that have showed such a great interest in OpenBaseMovil, through this blog’s comments and through email. We are almost there… just a few days for RC2 and you will have all you need to create powerful, enterprise-class J2ME applications.
We’re working to release as soon as possible the J2ME database engine, OpenBaseMovil-db, along with the required dependencies.
In the mean time, we have written a short developer guide that will let you take a deeper look at the database.
It also contains the specification of the proposed SQL engine that will sit on top of the current API-based one, as requested by some of you by email. This SQL engine is to be written, but for most applications I believe it is not really necessary.
We are very happy of the echo and the comments that we are receiving from the community, we hope that you find our framework really useful.
Stay tunned, the database engine will be released soon, and a little afterwards the first complete release with the ui engine.
Here is the OpenBaseMovil-db Developer Guide in PDF format.
Update: The document has been updated with some minor changes in the SQL format and some examples.
We’ve just started to use the project wiki (provided by SourceForge). We plan to put there useful information about the platform, but mainly as a vehicle for collaborative definition of objectives and specifications.
The first thing we are defining and discussing is the specification for the OpenMidsets platform. The idea behind it is to create a first well defined draft that will guide the development of the host application itself, but more over the foundations for the programming model for the hosted applications.
We are defining the life cycle of an OpenMidset, the intercommunication protocol to allow applications to collaborate between them and to access system resources in a uniform way that can be really portable to platforms other than J2ME (like Android).
It has very little information yet, bet we expect to put more over the next weeks and we’d like you to share your ideas with us to make it a better platform for powerful mobile applications.