Michal Čihař - Archive for May 7, 2007

I just spent some time on improving my website. Well I'm not graphic designer, so the site won't ever be according to latest trends and won't look sexy.

Anyway I tried to improve visibility of some things a bit. The main page now includes small screenshots of some programs I want to point out, small screenshots on application page are clickable and there is more visible download link on some pages as users complained they have problems finding this. While working with stylesheets, I also added maximal width of main content. This probably does not work with all browsers, but I don't care, the text is still visible.

Other thing I updated is information about last year talk about Gammu, which now contains links to videos. I haven't seen them yet, but they might contain interesting information for Czech speaking people :-).

Current Gammu versioning scheme confuses people a lot. For some time 1.x.0 versions are stable and 1.x.y are testing. However when somebody sees 1.10.5, he things this is updated version of Gammu 1.10.0. So it's probably time to move to something more obvious starting from next development cycle.

To stay as much compatible as possible with current scheme, I thing about minor change - so start testing releases on something like 1.11.90. I thing this is also quite often used (I've seen such versions in PyGTK in past) and nobody will confuse it with patch releases. Or should I switch to something completely different? I currently do not consider 1.11.0-rc1 as I'd like to keep version only numeric.

I just released new version of Gammu, you can download it from download server. The biggest change is improved gnappled and it's support in Gammu. It also had to became incompatible with previous versions, so you have to upgrade it in your phone. Full list of changes:

• Backup file uses ; instead of # (bug #85, patch by Marcin).
• Updated shell script gammu-config to generate configuration.
• Install gammu-config script to ease generating configuration.
• Correctly encode text in iCalendar (bug #262).
• Correctly encode recurrance in iCalendar (bug #262).
• Read last modified field from vCalendar.
• Support for last modified field from vCard.
• Use unsigned char to avoid trimming at 60 chars (bug #274).
• Properly handle vCard style continuation (bug #268).
• Detect Motorola specific error while reading SMSes (bug #288).
• Fix OBEX listing to behave according to specs (bug #290).
• Fix crash on invalid SMS reply from phone (bug #293).
• Improved gnapplet and support for it (Matthias Lechner).

I currently do not plan further testing release before next stable one, but in case some serious problem is found, this can change. This time really :-).