Hi, all
Yesterday I uploaded a beta version of one my projects, Twitter API ME v1.9. This version does not bring any new feature, but updates the project due to the changes in Twitter API v1.1.
The idea behind publishing an ealier build for the developers, is to give them a chance to test their apps as soon as possible. Any feedback is welcome! Here is the forum's link.
It is important to point out that Twitter API v1.0 will be shut down on March 5th... so TwAPIme v1.8 and older will stop working as well.
The download link is here.
See you in the next post...
Feb 26, 2013
Feb 25, 2013
Multiple HTTP Headers for S40: Fixed!
Hi, all
Long time since last time, hah? Sorry! Quite busy!
Back in 2011 we reported a problem on Nokia S40 platform. That time I would like to be able to access multiple HTTP headers of the same type, i.e. Set-Cookie. Unfortunately, I found it was not possible, because of a bug in the platform. It was a shame, since I had to implement a workaround for a feature that I was working on in one of my projects due to this issue.
But now, furtunately, I am here to share that this issue was fixed by Nokia in S40 SDK 2.0, present in the new multi-touch Asha devices.
Skalogir - Update 16th of August 2012
This issue is still present and affects both Symbian and Series 40 devices. After extensive hands on testing, I have updated the categories. The error is fixed on S60 5th Edition and Series 40 Developer Platform 2.0. Any previous platforms are affected by this.
Great, isn't it? I tried it out and it really works. Finally, I was able to implement my feature the way I wanted.
On the other hand, it is fixed only for SDK 2.0. So, if your app still targets older versions of S40, you will have to handle it.
One more time, thanks Nokia.
See you in the next post...
Long time since last time, hah? Sorry! Quite busy!
Back in 2011 we reported a problem on Nokia S40 platform. That time I would like to be able to access multiple HTTP headers of the same type, i.e. Set-Cookie. Unfortunately, I found it was not possible, because of a bug in the platform. It was a shame, since I had to implement a workaround for a feature that I was working on in one of my projects due to this issue.
But now, furtunately, I am here to share that this issue was fixed by Nokia in S40 SDK 2.0, present in the new multi-touch Asha devices.
Skalogir - Update 16th of August 2012
This issue is still present and affects both Symbian and Series 40 devices. After extensive hands on testing, I have updated the categories. The error is fixed on S60 5th Edition and Series 40 Developer Platform 2.0. Any previous platforms are affected by this.
Great, isn't it? I tried it out and it really works. Finally, I was able to implement my feature the way I wanted.
On the other hand, it is fixed only for SDK 2.0. So, if your app still targets older versions of S40, you will have to handle it.
One more time, thanks Nokia.
See you in the next post...
Jul 6, 2012
New version of Google Analytics ME v2.1
Hi, all
Today, I would like to announce that Google Analytics ME v2.1 has been released. This new version comes with important fixes. See them below:
- Fixed issue that was not identifing properly unique visitors.
- Improved session counter and visit duration calculation.
- Assign a custom user agent throught the JAD property "GAME-Custom-UserAgent".
It is important to point out that this new version will reset a cookie that is installed in your app by the API to track the user. This was necessary, since its structure had to be changed. So, don't worry when new unique users appear in your reports, when your users start updating their apps. From now on, they will be unique for sure.
Use the new JAD property "GAME-Custom-UserAgent" to customize the user agent that your app sends to Google Analytics. For instance, this can help you identify properly from which devices users are running your app.
I would like to thank Ramesh Sudini from SAAVN for your contribution in this release.
To download the API, click here! By the way, inside the package there is a sample app for reference.
Hopefully, everybody enjoy it!
See you in the next post...
Today, I would like to announce that Google Analytics ME v2.1 has been released. This new version comes with important fixes. See them below:
- Fixed issue that was not identifing properly unique visitors.
- Improved session counter and visit duration calculation.
- Assign a custom user agent throught the JAD property "GAME-Custom-UserAgent".
It is important to point out that this new version will reset a cookie that is installed in your app by the API to track the user. This was necessary, since its structure had to be changed. So, don't worry when new unique users appear in your reports, when your users start updating their apps. From now on, they will be unique for sure.
Use the new JAD property "GAME-Custom-UserAgent" to customize the user agent that your app sends to Google Analytics. For instance, this can help you identify properly from which devices users are running your app.
I would like to thank Ramesh Sudini from SAAVN for your contribution in this release.
To download the API, click here! By the way, inside the package there is a sample app for reference.
Hopefully, everybody enjoy it!
See you in the next post...
Jun 28, 2012
LWUIT for Series S40
Hi, all
Nokia has done a great job on its Series S40! Of course, they are low cost devices, but they are quite functional and bring good specifications (touch, GPS, Wi-fi, etc). In addition, the design of some of them is very pleasant and thin, for instance, the Asha family. I tried Asha 303, X3-02 and C3-00, and I liked the result!
Other good news is that Series S40 has a powerful Java ME environment. A bunch of JSRs are supported (most of them present in the whole series), specific Nokia API, e.g. Maps API (you gotta check out this one!) and In-App Purchasing, and Nokia IDE (Eclipse-based) and many other tools. Nokia is now releasing its SDK 2.0 for Series S40, along with new devices: Asha 305, 306 and 311. All of them now full touch.
Now let's stick to the post's title.
Taking the opportunity of the launch of its new SDK, Nokia is also releasing LWUIT for Series 40, a work done with LWUIT team, which built an optimised version of LWUIT for S40 with a number of styling, theming, and functional changes. This version has a total integration with some features presente on S40 devices, e.g. native keyboard and S40 gesture framework. LWUIT for S40 can be used to create applications targeted at Series 40 5th Edition and newer devices.
This optmization has provided some notable changes on LWUIT components (e.g. Form, List, TextArea, TextField, etc) so they can take advantage of platform's features and look more integrated to S40's UX. On the other hand, these changes are transparent to developers. So if you are already familiar with LWUIT's APIs, don't worry!
You can find all those changes and other useful information, e.g. installation and other resources, about LWUIT for S40 in this Wiki page.
The link to donwload is here.
Nokia, thanks for boosting Java ME for real.
See you in the next post...
Nokia has done a great job on its Series S40! Of course, they are low cost devices, but they are quite functional and bring good specifications (touch, GPS, Wi-fi, etc). In addition, the design of some of them is very pleasant and thin, for instance, the Asha family. I tried Asha 303, X3-02 and C3-00, and I liked the result!
Other good news is that Series S40 has a powerful Java ME environment. A bunch of JSRs are supported (most of them present in the whole series), specific Nokia API, e.g. Maps API (you gotta check out this one!) and In-App Purchasing, and Nokia IDE (Eclipse-based) and many other tools. Nokia is now releasing its SDK 2.0 for Series S40, along with new devices: Asha 305, 306 and 311. All of them now full touch.
Now let's stick to the post's title.
Taking the opportunity of the launch of its new SDK, Nokia is also releasing LWUIT for Series 40, a work done with LWUIT team, which built an optimised version of LWUIT for S40 with a number of styling, theming, and functional changes. This version has a total integration with some features presente on S40 devices, e.g. native keyboard and S40 gesture framework. LWUIT for S40 can be used to create applications targeted at Series 40 5th Edition and newer devices.
This optmization has provided some notable changes on LWUIT components (e.g. Form, List, TextArea, TextField, etc) so they can take advantage of platform's features and look more integrated to S40's UX. On the other hand, these changes are transparent to developers. So if you are already familiar with LWUIT's APIs, don't worry!
You can find all those changes and other useful information, e.g. installation and other resources, about LWUIT for S40 in this Wiki page.
The link to donwload is here.
Nokia, thanks for boosting Java ME for real.
See you in the next post...
May 14, 2012
The Death of RIM: The fall of a big Java ME player
Hi, all
Check out this interesting infographic about RIM's trajectory from top to the bottom. It is a sad picture of a big company and a big Java ME player as well.
I hope you guys enjoy it.
See you in the next post...
Created by: MBAOnline.com
Check out this interesting infographic about RIM's trajectory from top to the bottom. It is a sad picture of a big company and a big Java ME player as well.
I hope you guys enjoy it.
See you in the next post...
Created by: MBAOnline.com
Jan 3, 2012
Google Analytics ME v2.0: Unique visitors
Hi, all
Today, I would like to announce that Google Analytics ME v2.0 has been released. This new version comes with some good news and important changes. See them below:
- Identification of unique visitors.
- Better visitor's features identification.
- Small code refactoring.
- Android support deprecated.
Identification of unique visitors
Now GAN ME identifies properly who is a new visitor or not. This way, your visitors report is 100% accurate about the number of new and old visitors.
Better visitor's features identification
More visitor's features are being collected by GAN ME. For instance, now the app's name, version, screen size and number of colors are being collected.
Small code refactoring
To implement some of the new features and fix some of the bugs, some code changes were required, which may cause some compilation errors for your app. But it is not a big deal from developer's view. Actually, most developers will just have to fix the call to Tracker.getInstance(), which now requires to pass the MIDlet instance as well as the GAN app Id.
Android support deprecated
From this version on, we decided to deprecate the Android support. It turns out that there is already an official GAN API for Android, built by Google. So, we strongly recommend you to use that one in your Android app. It is very good!
I hope everybody enjoy this new version. Let me know your feedback.
To download the API, click here! By the way, inside the package there is a sample app for reference.
See you in the next post...
Today, I would like to announce that Google Analytics ME v2.0 has been released. This new version comes with some good news and important changes. See them below:
- Identification of unique visitors.
- Better visitor's features identification.
- Small code refactoring.
- Android support deprecated.
Identification of unique visitors
Now GAN ME identifies properly who is a new visitor or not. This way, your visitors report is 100% accurate about the number of new and old visitors.
Better visitor's features identification
More visitor's features are being collected by GAN ME. For instance, now the app's name, version, screen size and number of colors are being collected.
Small code refactoring
To implement some of the new features and fix some of the bugs, some code changes were required, which may cause some compilation errors for your app. But it is not a big deal from developer's view. Actually, most developers will just have to fix the call to Tracker.getInstance(), which now requires to pass the MIDlet instance as well as the GAN app Id.
Android support deprecated
From this version on, we decided to deprecate the Android support. It turns out that there is already an official GAN API for Android, built by Google. So, we strongly recommend you to use that one in your Android app. It is very good!
I hope everybody enjoy this new version. Let me know your feedback.
To download the API, click here! By the way, inside the package there is a sample app for reference.
See you in the next post...
Dec 6, 2011
Multiple HTTP Headers: No cookie for you
Hi, all
As you may know, HTTP Cookies are mostly used to track sessions between a client and a server. The flow is pretty simple: you access a server and it returns a piece of information (a cookie), which the client stores, in order to send back in every subsequent request. Based on this cookie, the server identifies the client.
Unfortunately, this session management must be handled by the developer, since HttpConnection does not do that automatically. This is achieved in a very simple way and a few lines of code. If do not know how to do it, please learn now here.
According to the example at Nokia's page, session management using a single cookie is very easy. How about two? It should be easy as well. Instead of only one, now you have to store two and send them back.
In a project that I am currently working on, there are two cookies to manage the session. As I said above, it is very easy, right? It should be. I am porting a code from Nokia S60 5th Edition series to S40 6th Edition. This session management works like a charm, but it fails on S40. Any guess? No? Read the post's title again. The answer is:
Series 40 platform devices up to Series 40 6th Edition and Series 40 5th Edition, Feature Pack 1 Lite, and S60 devices prior to S60 3rd Edition, Feature Pack 1 does not support multiple HTTP header. It means that two cookie cannot be handled, because only one is available. Nice, hah?
Long story short, we had to implement a workaround in our server for S40 version, where only one cookie is used for session management. As a consequence of it, this version accesses a no scalable server, since the second cookie was used for load balancer.
W.O.R.A does not work so well on mobile devices.
See you in the next post...
As you may know, HTTP Cookies are mostly used to track sessions between a client and a server. The flow is pretty simple: you access a server and it returns a piece of information (a cookie), which the client stores, in order to send back in every subsequent request. Based on this cookie, the server identifies the client.
Unfortunately, this session management must be handled by the developer, since HttpConnection does not do that automatically. This is achieved in a very simple way and a few lines of code. If do not know how to do it, please learn now here.
According to the example at Nokia's page, session management using a single cookie is very easy. How about two? It should be easy as well. Instead of only one, now you have to store two and send them back.
In a project that I am currently working on, there are two cookies to manage the session. As I said above, it is very easy, right? It should be. I am porting a code from Nokia S60 5th Edition series to S40 6th Edition. This session management works like a charm, but it fails on S40. Any guess? No? Read the post's title again. The answer is:
Series 40 platform devices up to Series 40 6th Edition and Series 40 5th Edition, Feature Pack 1 Lite, and S60 devices prior to S60 3rd Edition, Feature Pack 1 does not support multiple HTTP header. It means that two cookie cannot be handled, because only one is available. Nice, hah?
Long story short, we had to implement a workaround in our server for S40 version, where only one cookie is used for session management. As a consequence of it, this version accesses a no scalable server, since the second cookie was used for load balancer.
W.O.R.A does not work so well on mobile devices.
See you in the next post...
Subscribe to:
Posts (Atom)
News