I decided to split Wammu site to several pages. The one page seemed too large so this was logical step which I wanted to do for a long time. I hope there are no broken links or any other broken stuff.
Wammu 0.15 has been just released. New features:
This is a bad day. I'm bad guy because I don't have web pages about Wammu in my native language, I hacked absolutely useless CSV import code in phpMyAdmin. What comes next?
I would make bilingual pages if I'd have time for that, but I will rather write new feature in Wammu than spend time on this.
And I know export is not perfect, everything can be improved and you are welcome to do that!
It looks like anybody didn't notice that it is not possible to login to bug tracker. I didn't because I use permanent login and nobody didn't tell me.
Anyway I just upgraded Mantis to 1.0.5 which fixes this issue, feel free to report bugs :-).
It looks like Wammu for Windows was deployed quite good. Three days after annoncement and no major complains were reported so far to bug tracker (only one minor which I managed to find just after release). And people are downloading big installer as frequently as source codes (and I hope they actually use this tool :-)).
But if you have a problem, don't affraid of reporting, I will do my best to fix it.
For upcoming Wammu-ng I have to resolve again same question that I solved for many times - what version control to use?
I know I want something distributed. I know I want to go away from arch/bazaar as they are not maintained anymore. However where to go? Mercurial? Bzr? Darcs? All of them seem to be good candidates, but I don't see much difference. I'd like to use something in Python as it's something what I can fix in case of problems (well I don't want to fix that, but who knows …).
I like bzr, but it's still quite moving target. Anyway it has some interesting ideas and it's probably what I will use at the end.
As you might have noted in Wammu 0.14 announcement, I made Wammu for Windows reality. At the end there is more support for that than I expected :-). All you need it to download full installer and everything will be done automatically including start menu entry.
Wammu on Windows looks almost identically as GTK version on Linux, there is really no big difference as you can see from screenshot.
It revived my memories about creating native Windows application years ago as I used same tool for creating instalator (Inno Setup). It works still same way and is very easy to use even when I didn't remember anything from time I created installator for CodeConv.
Wammu 0.14 has been just released. New features:
There is imortant change in this release - we finally have Windows support! On download pakge you will find Windows installer which includes all needed (thanks to py2exe and Inno Setup). Please share experiences, as I'm definitely not experienced in this area :-).
There wasn't much progress on Wammu in past months. Partly it has been caused by changes in real life, but major reason was that I want to go away from wxPython and this step is quite large to happen over night :-).
Meanwhile I didn't do much in current Wammu codebase, but few bugfixes were applied. I will fix few more bugs during weekend and release new version. Don't expect much of it, I will only try to test it a bit on Windows and fix some recently reported bugs. So most changes are already in and you can see them in arch repository.
It will be most likely latest which is using wxPython and I will start writing completely (well this it not true, most code will be reused) new Wammu which will use PyGTK. It will be highly modullar and should provide all those heavilly missing features as remembering of read data and support for multiple phones.
I don't have any timeframe when new version will be ready, but I'd like to make preview available somewhere in September. But life can bring completely different worries, so everything might be completely different :-).
Users always request support for their latest shiny new phone. But how to manage such support in environment where you can not buy each new phone to implement support for it?
You can try write driver only by using documentation for manufacturers who provide it (like Sony-Ericsson), but there will most likely be bugs which need hardware to be debugged.
For phones where is no documentation available (eg. Nokia), it is almost impossible to support them without having access to actual device (at least through user who has enough interest in improving support).
I'd like to implement full support for Sony-Ericsson to achieve comparable feature set to FMA. However I still have more important expenses than buying phone from them, so this task stuck for long time in my queue. In fact it also holds Wammu development as I'd like to start with more complex feature set than my current phone supports and it's impossible to implement it without phone.
So what now? Maybe is here somebody who would be interested enough in improved tools and will help me buying such phone. But I don't believe this will happen, at least my current experiences tell so…
