My ongoing intenship
Quick peek what I'm up-to these days
This entry is more personally oriented, to reflect on what I'm currently up to, in comparison to my other entries in mobile development.
Back in July I received fair offer for 8 weeks internship with SourceSense, London office. Company is involved and interested in open source development, Agile methods with Extreme Programming (XP) and Scrum.
How to browse file structure of mobile device with JME
Example of simple way to browse files on mobile phone
Display - Best Practice (hopefully)
How-To manage display change from screen to screen
For some time I was happy with the way I've written the code to handle showing information on device display. This topic was not discussed at my university, I guess no one actually does it, we were just provided with sample application that did whatever task been showcased during the lecture. Same applies to books that I've read so far, in regards to mobile development ( Beginning J2ME: From Novice to Professional, Kicking Butt with MIDP and MSA - Creating Great Mobile Applications, Enterprise J2ME Wireless Applications and J2ME in a Nutshell), not one of them actually explained how display changing action should be performed. After recently starting to study for my SCJP exam (SCJP Sun Certified Programmer) I asked my self "Do I really do it the best way?".
Contact sorting - Contact List, Part 3
Simple sorting of data from RecordStore
This is the final part of my little tutorial/coursework re-do, where I will show you how easily can stored contacts be organised.
Some of you may know that RecordStore works on base of LIFO - Last In, First Out approach. For example if record has been added in the order: peter, marta, bruno, mark they will be read out of RecordStore in reversed order as: mark, bruno, marta, peter. To get contacts sorted, there are two options; either try to put contacts in order every time new contact is added or, try to put them in order once they read out from RecordStore, just before they get displayed on screen. The first option is overkill as it is just too much work for application to perform each time new record is stored and pretty much useless (read all records, add new record in correct position and overwrite previous data), so second option is the obvious choice.