It is simple to load a BlackBerry application packaged as cod file to your device using JavaLoader.exe. With JavaLoader, you do not have to install the desktop manager if you just want to have an ability to quickly load applications to your blackberry

1. Connect your BlackBerry to your computer through USB
2. Open command prompt and navigate to the location of JavaLoader.exe
3. Run JavaLoader.exe -u=USB load path_to_your_cod_file command and you should be all set

It is easier if you have the JavaLoader and the COD files in the same dir because then the command is simply

JavaLoader.exe -u=USB load path_to_your_cod_file

UPDATE: The JavaLoader command will not work if you don't have the BlackBerry desktop manager installed. You will get an error that the port can not be open.

It seems that GPU computing is becoming more and more ubiquitous. Tools are becoming better and better, the applications are becoming wider and wider and the hardware is becoming faster and faster too.

CPU are steadily gaining in productivity. It's a steadily rising curve. Is it good news though? Depends how you look at it. It's good that the speeds and efficiency are improving, but apparently CPUs  are improving much slower than GPUs. GPUs computational power for suitable problems (like number crunching) was apriory much higher to start with, but what's really important is that GPUs are moving much faster i.e. the curve of the speedup is much sharper than that of CPUs.

For about $500 you can get the Nvidia GTX 480 right now with 400+ cores and super fast memory. GPUs in general also require much less space and power and thus are in general much more efficient for heavy number crunching computations than CPUs. Of course GPUs are quite limited in their capabilities and are really suitable for specific tasks, but there are more and more areas where people are starting to employ the power of highly parallel GPU computing with lightweight threads.

There is another caveat with GPU - it's the slow bus connection. The bus is too slow for the speeds of GPU and there is nothing you can do about it at the moment. One thing that can be done since GPU has so much computing power in parallel, is to compress the data that is passed between the GPU and the rest of the system. 1 to 10 ratio is the standard compression ratio of text, so you can increase the throughput of the bus by a factor of 10 using compression. Of course there is still some overhead and you should make an experiment and see whether this is beneficial in your setup.

Overall though, it seems pretty exciting area at the moment and the true technoratis should definitely pay attention to that area.

It's been long advocated by software developer luminaries that you have to "eat your own dog food" which means you have to use the software you are producing as extensively as possible to realize the shortcomings and things that are broken. This is the "I am not a fish" category as explained by Seth in the series of the following 3 videos. Extremely valuable series for anyone dealing with user experience.

If you have "can't locate tools.jar" error when trying to run "ant", you've come to the right place. The fix is apparently very easy, you have to properly set up the "JAVA_HOME" environment variable to Java JDK. The tools.jar is found in the bin folder of the JDK but you only need to point the JAVA_HOME to your JAVA SDK installation and you should be all set!

Easy, right? Go get them!

If you've been experiencing horrendous performance of Eclipse on OS X, or maybe you even did not know that Eclipse actually can run very fast, you'd be surprised to learn that apparently it is very easy to make Eclipse run 4-5 times faster  on OS X with proper settings to your eclipse.ini file.

First I will give you a bit of  background. If you want the gist of it or how to make it fly - just go the end of the post.  So a few days ago, PSU fried on my main desktop development machine. It is a newer Quad Core i5 2.6 machine with 4GB 1066Mhz memory and a standard 7200 RPM drive. Since the machine is dead and I am waiting for a replacement power supply, I had to move to my new and shiny MacBook Pro, which I have recently purchased and which is from the latest batch of the updated MacBooks and is quite powerful. It is also i5 (only dual core though) with the same 4GB of 1066Mhz memory and 5400 HD.

So, yeah, I would say that the systems are pretty close right. Nevertheless, working with Eclipse on OS X felt horrendously slow! I had already noticed this nuance in the past and I thought that the Eclipse is just not meant to fly on Mac-s (oh well...), especially when there are so many different distributions for OS X, it signals that the project is in a shifting phase basically (it is shifting from Carbon to Cocoa) and that you should expect all kinds of problems.

I bet many people not having experience with Eclipse on other platforms would think this is normal. It's Java, so it is supposed to be slow and they just go and hate it and sing how X-Code is great. The thing is, they probably never experienced the full potential of Eclipse - a pity. Hopefully this post can change your mind and help you experience the wonderful world of Eclipse (ok, I am being a little dramatic here). Ok, let's dive into that.

Since I am pretty heavy user of Eclipse [intlink id="75" type="post"]developing both for Android and BlackBerry[/intlink] the slowness of Eclipse quickly grew on me and I started looking for ways to try and do something about it.

In the past while experiencing slowness with Eclipse on Windows, I played with the memory allocation within it to increase the memory cap and this usually helped a bit. Being desperate, I decided to try that and off I went to try that. But, that was not so easy. I wandered a bit around the eclipse folder looking for the location of the eclipse.ini but it was nowhere to be found. So I tried searching for it - nop, no luck there as well.

Apparently eclipse.ini is packaged inside the eclipse app so what you need to do is to get inside the eclipse.app package

after that edit eclipse.ini which you will find in Contents->MacOS folder and increase the memory limits for the following directives:

-Xms***m
-Xmx***m

replace the *** with whatever memory you think should work for you as a rule of the thumb, just try to double it at first.

While this is good, this is NOT what will actually make your Eclipse fly. The most important part here is the:

-Dosgi.requiredJavaVersion=1.5

now, you have to switch that to 1.6 and make it

-Dosgi.requiredJavaVersion=1.6

Now THAT will make your Eclipse really shine! Just make sure you actually HAVE the JDK 1.6 installed. You can validate this by running "java -version" in the terminal. If you got 10.6 - Snow Leopard though, you are most likely covered.

If you already had that in the eclipse.ini file - well, unfortunately this already has been optimized for you and the only thing you can try from there that we know of is to play with the memmory limits.

If you know any other tips and tricks, please let me know in the comments!

I've got the Motorola Droid from Google through their device seeding program a while ago. Which is nice although Nexus One would be much better since then I would have been actually using as my phone. The Droid has to be tied to Verizon and I am a T-Mobile lad all the way.

Anyways, I've tried a few times to get adb debugging talk to my Droid on my Win7 64 bit and I could not get it to work for a long long time. I tried to search around for the solution, but none of the drivers that I've found worked until today I started the search again and found the Win7 64 bit Droid drivers from Motorola here which worked perfectly fine!

Don't forget to go to "Settings->Applications->Development" and enable "USB Debugging"

People that are fascinated by Apple usually don't look around for other things, they like the polished products that just work. But for other people and technologists it's not like that. We usually are looking for the best tool for the job. So my point here is that not many Apple fans even heard of Chrome OS. Yes, they probably heard about Chrome browser (and this was very smart move by Google by the way, first to release the browser by the same name for many reasons, but one reason is that people are getting used to the Chrome web experience).

Anyways, the question that I really wanted to address here is: was the development of Chrome OS and the Chromium project in general a response to the iPhone OS thread and the coming (now released) iPad or maybe it was exactly the other way around?

So Google started actively working on the Android OS about 2 years ago while iPhone was already available but doing the first baby steps. The pace of development of Android was quite fast and at the moment these rival operating systems  are somewhat comparable in futures stability and usability. Some are lacking on Android and some are lacking on the iPhone. Last year Google started working on the Chrome OS which is essentially an operating system inside the browser and just about a month ago Apple released the iPad to the public. While there are already a few tablets running on spin offs of Android OS, Google is rumored to be soon releasing its own tablet and what it will run is yet unclear.

Anyway however, it seems that Google is targeting the same space that the iPad does right now with its Chrome OS. Simple operating system. Or is it an operating system and can it be compared with the iPhone OS which is actually an operating system. Very limited at that but still. If the Chrome OS would be the strictly in browser OS it is questionable how it will stack up against iPad. Users are used to having free access to their file system and being able to install software rather than use webapps. In that sense the iPad is revolutionizing and laying out the ground for the change of computing paradigm we got used to so far.

It is not clear what came first (as the concept) and what was developed first but it would be sure very interesting to watch this evolution of computing in the near future.

If you were wondering whether you can use  apache licensed code in your commercial applications and what do you need to do in order to comply with the license here's the unofficial simple ans short answer.

You can use Apache 2.0 licensed source code in your project as long as you include the copy of the license in your distribution and provide attribution in an applicable way in your distribution.

The slightly lengthier and detailed (but still very simple explanation) is below, taken from Apache license FAQ

Describing legal documents in non-legalese is fraught with potential for misinterpretation. Notwithstanding the text that follows, the actual text of the license itself is legally binding and authoritative.

That said, here's what the Apache license says in layman's terms:

It allows you to:

• freely download and use Apache software, in whole or in part, for personal, company internal, or commercial purposes;
• use Apache software in packages or distributions that you create.

It forbids you to:

• redistribute any piece of Apache-originated software without proper attribution;
• use any marks owned by The Apache Software Foundation in any way that might state or imply that the Foundation endorses your distribution;
• use any marks owned by The Apache Software Foundation in any way that might state or imply that you created the Apache software in question.

It requires you to:

• include a copy of the license in any redistribution you may make that includes Apache software;
• provide clear attribution to The Apache Software Foundation for any distributions that include Apache software.

It does not require you to:

• include the source of the Apache software itself, or of any modifications you may have made to it, in any redistribution you may assemble that includes it;
• submit changes that you make to the software back to the Apache Software Foundation (though such feedback is encouraged).

If you don't want the preamble of why I wanted to serve JAD files from Amazon S3, skip to the second paragraph.

I have recently came across the need to push OTA update of the DailyHoroscope application for BlackBerry. I conjectured that OTA updates have different behavior and thus different impact on the web server. There are still many people using their smartphones in general and BlackBerries in particular over the slower EDGE connections as opposed to 3G, not to mention 4G and/or WiMax. So to download 300K file over EDGE connection in the real usage example can take anywhere between 10 seconds to couple minutes. All this time the webserver's thread serving this specific client will remain running. So it seems like you (or rather your server) can be in a nasty situation when 1000 users simultaneously or almost simultaneously decide to do the OTA update. Also quick calculation with Amazon WS calculator shows that serving files from S3 would be rather cheap even comparing to renting a cheap VPS for that purpose. My estimate was that the whole upgrade process (considering the fact that almost all the users update from S3) will cost me about $15. And this is independent of the time span. For $15 you could get a very cheap VPS for one month (if you are lucky). So it seemed like a no brainer. It indeed was until I faced a few problems with setting this up which I will cover here so that you don't have to spend much time looking for solutions if you want to do the same.

Setting up S3 is a breeze. Using it - not so much. It is just like any other service pretty much - when you want to sign up and call sales you are answered immediately but if you have a problem and need customer service, well, you can be on hold quite a while. If you have Amazon account already set up, you can use this account. You will have the option to opt for the payment to any of the payment options (now it seems that this is only credit cards) already on file with Amazon or you could add a new credit card so that your S3 bill is billed separately.

When you signed up, you are almost ready to begin using S3. Once you receive confirmation email which can take a few minutes until your request is processed and billing information verified, you are set to go.

• Open your Amazon account dashboard and login with your Amazon account you had or just created
• Click on Security Credentials
• Under the Access Credentials table, look at the first tab - Access Keys
• Next to your access key, will be a column Secret Access Key which will have the secret key hidden from the screen.
• Press the Show and your secret access key will be revealed

Now you can use this information to log in to S3 and start uploading files. To access S3 you can use S3Fox from any platform since it is FireFox plugin. You can use CyberDuck if you are on Mac which is an excellent free general purpose FTP client which also supports WebDav and SFTP. If you are on Windows, there is also free and feature rich client CloudBerry. S3Fox is very nice and fast and you do not have to install anything on the system, only plugin for FireFox, but I will be using CloudBerry since we will need to set custom Content-Type for the JAD and COD files and CloudBerry is more feature rich than S3Fox.

• Open CloudBerry
• Enter your credentials and open your S3 account
• Create a bucket - it has to have unique system wide name like a domain name (actually subdomain, because after it is created it is references by http://yourUniqueName.s3.amazonaws.com)
• Enter into the bucket and create folders, or just upload the files you want to serve. If you like me want to serve OTA BlackBerry application, you probably want to create a separate folder for each release
• After you create the folder, use the ACL (access control levels/list) menu button to open the ACL controls

• Using the ACL controls, give "Read" access to "All Users" (note that if you place check mark on the bottom "Apply for all subfolders and files" the permissions will propagate down the tree)

Now the whole world can read the files you uploaded. The problem with BlackBerry OTA distribution is that Amazon does not send the right mime-types in the HTML Content-type header. And this is something that you will need to get fixed before people can actually install your application over the air directly from S3.

The right content types for the the JAD and COD are:

• jad -  text/vnd.sun.j2me.app-descriptor
• cod - application/vnd.rim.cod

So using the custom HTTP headers menu button we will be setting those types for JAD file and all the COD files respectively.

• Select your JAD file and click on "Set HTTP Headers" button

You will get the custom HTTP headers dialog:

• Select the "Content-Type" field and replace it with the text/vnd.sun.j2me.app-descriptor for the value

Now you can repeat the above step for each COD file individually, or you can select all the COD files and set the headers at once but then you would need to add the "Content-Type" header manually for the right COD mime type - application/vnd.rim.cod. Just use "Add" and in the HTTP-Header enter "Content-Type" and in the Value enter "application/vnd.rim.cod". You should see something like the following dialog

***IMPORTANT to check the "Keep existing headers" or you will loose all your default defined headers which is not good in most cases.

That's it, you are DONE! Check that you did everything right by pointing your BB browser to http://yourUniqueName.s3.amazonaws.com/yourReleaseFolder/AppName.jad and make sure that you can install the application from there. If you did everything right it should work.

Overall S3 seems like a very nice (and apparently very cheap) service and anyone who serves lots of static content should consider using it for that purpose. But not everything seems so pink in the world of S3 and I am sure you will face many other small problems and nuances while setting it up as I did for my task. But hopefully if serving BlackBerry application is all you want, you should now have everything to get you started.

The next version of the BlackBerry Eclipse plugin will fix most of the [intlink id="75" type="post"]annoying things about blackberry development[/intlink].

Some of the most important things are:

1) No need to restart emulator for new build to be loaded to the emulator (Hallelujah!!!)

The new build should be just loaded onto the already started simulator, pretty much as on Android and iPhone.

2) Ability to add external libraries i.e. *.jar files to the project

This is actually pretty peculiar since RIM was pushing hard 3-d party (external library) integration as one of important concepts and obviously it would be very beneficial for the BlackBerry ecosystem but if you did not want to use JDE, there was pretty much no clean way to add external library. That is until the 1.1 plugin comes out from beta, or at least that what was promised at the [intlink id="167" type="post"]New England BlackBerry developers meetup[/intlink].

3) The BlackBerry plugin would follow the "Eclipse way"

The 1.1 plugin is very different from previous version. Instead of following the "JDE way" it will be much more the natural "Eclipse way". This is both good and bad. This is very good for developers that have experience with Eclipse and just now start to develop for BlackBerry. This will however be somewhat painful for the seasoned developers who got used to the old plugin and will need to discover many things from scratch. (I personally felt quite lost with the new 1.1 plugin and decided to stick with the old one until 1.1 comes out of beta).

You can download the beta of 1.1 from here (you would need to have BlackBerry developer account which is free and can be obtained with simple sign up immediately)