Association Subscribers Manager and Open source stuffs

Hi,

The first beta version of Association Subscribers Manager version 3.1 have just been released ! Has usual, you can find files and bug tracker/feature requests tracker at :

You can download packages and installer at :
https://sourceforge.net/projects/assuma/files/

You can report bugs and ask for new features at:
http://sourceforge.net/tracker/?group_id=211536

This version features many changes and the most important are:

• add theme feature
• add custom fields feature
• add more compilation macros to help packagers
• huge settings system code rewrite to make it simpler
• GUI changes to reflect settings update
• many bugfixes

I would like to use this release announcement to welcome and thanks Márcio Moraes for his work on the Brazilian Portuguese translation. He is the new official maintainer of this translation. Welcome aboard matey !

For the moment only the source packages is available, windows and GNU/Linux installers will comes later. As usual, this beta version's translation and documentation are not up-to-date, they will be in the stable release 2 weeks from now.

Enjoy !

Arnaud Dupuis & the Association Subscribers Manager team.

Hi,

I was ask today if I have plan to better integrate Association Subscribers Manager with KDE. Since the answer can be of interest for other people that the person who asked me, I will (also) answer here.

First, Association Subscribers Manager is designed and developed to be multi-platform (GNU/Linux, *BSD, MS windows and Apple's Mac OS X). On some of the supported platforms, KDE is not really widely installed. And amongst the target audience of Association Subscribers Manager there are people who are far from being geeks. Those are facts.

In the other hand, I am a firm supporter of KDE, I use it everyday both at home and at work and I would like to integrate Association Subscribers Manager a lot more into KDE.

So, to answer the question : I will do it and make it possible to enable at compile time. At least until I made a clear evaluation of KDE on windows and mac os X (since I have no windows nor mac boxes, I am not friendly with those platforms and the state of KDE on them).

But considering the road things are taking it is likely that Association Subscribers Manager will get a better KDE integration before it's 3.3 release...

Arnaud Dupuis

Hi,

After many months (years...) Geo::Coder::GoogleMaps have a new release ! The original company which paid me to develop this module have bankrupted so I resumed the work on this module on my free time. It took some time...

This version introduce the new Geo::Coder::GoogleMaps::Response object, fix for the user agent, documentation, a better test suite and many improvements. It also brings a major change in the API which will require you to update your scripts. Here is a non-exhaustive list of the changes since the 0.2 version (well... 0.3, 0.3.1 and 0.3.2 were kind of tests... and thanks to Slaven Rezic and RT it's now stable) :

• Huge API change : geocode() now returns a  Geo::Coder::GoogleMaps::Response ;
• Documentation update ;
• KML update (KML 2.2 with ExtendedData support)
• many bug fixes.

Hi,

The topic have been treated already on the internet but since the official build of Google Chrome only landed few hours ago, some extra informations and "re-post" cannot be bad.

So ! Google Chrome is not packaged for Slackware GNU/Linux distributions, well... That's not completely unexpected. And it is not packaged as a universal GNU/Linux binary either, which is more troublesome. Anyway here is my 2 ways to install Google Chrome on Slackware 13.

Important: I made everything on my EeePC (since I'm currently in holidays snowboarding in the French Alps) which runs a Slackware 13 x86, but everything should be exactly the same on Slackware64. I also have to warn you about my own install method : it's dirty and not especially quick

Method 1: 

My own method, it's what I used to install Chrome as soon as I got the Google's email telling me the beta version of Chrome official Linux build was out in the wild ! So it's pretty dirty, and not the quickest way to do it. It's how I installed it even before thinking about looking at the web to see if something have been done by somebody else. You have been warned.

So first, download the Fedora RPM (32 or 64 bits), then run rpm2tgz :

su -c "rpm2tgz google-chrome-beta_current_i386.rpm"

Then install the resulting package. Do not waste your time to launch it, it will not start. For me the first reason is : I have not installed seamonkey and I miss the libnss3, so a quick sprint to slackbuilds.org and I had the mozilla-nss package installed (compiling and installing a package from a slackbuild script is very well documented on slackbuilds.org).

Almost, but it does not launch... The  reason is, some poor links against libnss3. Well, at this point, I know I will not back off ! Let's shoot some ln shots !

ln -s /usr/lib/libnss3.so /usr/lib/libnss3.so.1d

ln -s /usr/lib/libnssutil3.so /usr/lib/libnssutil3.so.1d

ln -s /usr/lib/libsmime3.so /usr/lib/libsmime3.so.1d

ln -s /usr/lib/libssl3.so /usr/lib/libssl3.so.1d

ln -s /usr/lib/libplds4.so /usr/lib/libplds4.so.0d

ln -s /usr/lib/libplc4.so /usr/lib/libplc4.so.0d

ln -s /usr/lib/libnspr4.so /usr/lib/libnspr4.so.0d

If you are running a Slackware 64, just replace /usr/lib/ by /usr/lib64/ and if you are using this way to install Google Chrome, bookmark this post to be able to clean your system

If you are not very fond of the manual linking (you are a wise person), please follow the Method 2 !

Method 2:

Well, the result is the same : you will get a working Google Chrome. The path to this result is considerably easiest and quickest (given the fact you have libnss3 on your system) :

Go to slackbuilds.org and get the Google Chrome slackbuild, install it (please refer to Method 1 for the link to the howto use a slackbuild).

That's all !

As a conclusion I would say that there is the equivalent of Method 1 for the Debian 5 package, but the Slackbuild do it better than I care to explain

Enjoy Google Chrome and do not hesitate to give your feedback on it in the comments. So far for me, the difference in performance and CPU usage with Firefox on my EeePC is amazing ! I could barely run 4 tabs in Firefox, and look at the screenshot ! With 9 opened tabs it's still amazingly fast  ! I will benchmark it against Fennec soon !

Arnaud Dupuis

Hi,
once again I gave no news for a while... My bad, but this time I have tons of good reasons !
First, my wife and me are awaiting an "happy event", this kept me busy.
Moreover, I work a lot (and I really mean a lot). I am currently in mission for Orange (European ISP, phone carrier, etc.) where I am technical project manager/coordinator (and developer) on their next set-top box. Believe me it is a lot of work.
The box is the next Intel's STB based on the Sodaville processor, my team and I are developping/integrating lots of cool stuff in this box like a full browser with Flash 10, a video game portal (from Transgaming), and a full bluray player. All those features are well presented in a brand new 3D GUI (thanks to Intel's plateform performances ! See around 1'45 of the video).

Well, all this kept me out of the web for a while but that do not means I have not coded anything ! So on Association Subscribers Manager's side, there was some changes too :

• theme feature is fully functionnal and fully supported
• flash plugin have been activated in the help browser and a new entry in the help menu allows you to directly the YouTube help channel in Association Subscribers Manager
• lots of compilation options added like the possibility for packagers to not compile all code related to the updater
• initial work on the custom fields editor

I will soon post a screen cast  of all those new features to show you guys the reality behind the words ! You can of course test all this by compiling the code from the trunk.

Enjoy !

Arnaud Dupuis

I am very pleased to announce the immediate availability of Association Subscribers Manager 3.0.1 !
This one is a major bugfixe version of the 3.0 branch of Association Subscribers Manager.
I want to particularly thanks all testers for their feedback and particularly two of them : Fabrice Eyraud for all his bug reports and his French translation of the documentation and the French association Forme et Santé (from La Couture Boussey) for the feedback on live usage they did.

You can download packages and installer at :
https://sourceforge.net/projects/assuma/files/

You can report bugs and ask for new features at:
http://sourceforge.net/tracker/?group_id=211536

You can also visit the website for more information :
http://www.associationsubscribersmanager.org

Here is a list of the main changes :
Association Subscribers Manager version 3.0.1
 - integration of the patches from Sascha Manns and David Haller from OpenSUSE packaging team
 - fix a bug in the re-translation of the UI's tooltips
 - fix a bug in the passive message system (messages still visible after being hidden if the window is made biggest)
 - fix a bug in the federation editor (see bug 2848046 on the tracker)
 - fix a bug in the search feature
 - fix a bug in the mail sending system
 - add French documentation translated by Fabrice Eyraud
 - made packagers life easier by adding an install target to the Makefile and possibility to configure the install destination (see README file).

Association Subscribers Manager is available as a source package (GNU/Linux, Mac OS X, BSD*, Windows, require a compiler), binary package for Linux and windows installer.

Enjoy !

Arnaud Dupuis

Hi,

This post will be in French since it only is relevant for French people using an Android smartphone with the French carrier SFR.

Bonjour à toi visiteur !

Si toi aussi tu es grand, beau, fort et intelligent, félicitation ! Tu as donc un smartphone sous Android. C'est bien mais... Je sens que tu me cache quelque chose... Ah ! Mais c'est bien sur ! Tu es chez SFR ! Ne t'en veux pas trop, nous sommes plusieurs à avoir fait ce choix, judicieux (haem...), pour pouvoir avoir un HTC Magic tout beau tout neuf.

Visiteur, si toi aussi tu as un magic avec une ROM qui n'est pas celle d'origine, ou que tu n'as pas de Magic mais que tu es chez SFR, et si tu veux utiliser le répondeur visuel quand même, lit la suite ! (Si tu veux la gloire, la fortune et l'honneur tu peux aussi lire la suite mais je ne garantit pas l'efficacité, d'autant que si tu es l'heureux possesseur d'un téléphone sous Android tu as déjà tous cela).

Donc voilà, SFR fait parfois (qui a dit "souvent" !?) des choix qui laisse rêveur. Par exemple, un jour, à une foire à tout / brocante dans le Gers, SFR a troqué tout ses designer (et ceux de 9telecom) contre 763 Kg de courgettes... Du coup maintenant, c'est le laveur de carreaux qui fait le design des applis SFR. Voilà pourquoi SFR ne sort que de très très laid "design" rouge et blanc tout carré.

Une autre fois, par mesquinerie pour se venger d'Orange qui avait sortit un smartphone sous Android en premier, SFR a réservé l'accès à son service de répondeur visuel aux seuls possesseur de HTC Magic ! Et malgrès des commentaires assassin sur le market, aucune mise à jour corrigeant ce trait de caractère pour le moins singulier d'une application qui, sinon, serait tout à fait honorable (exception faite du design) n'est disponible.

Heureusement, le tableau n'est pas si noir : une solution existe et celle-ci te permettra, cher visiteur, d'utiliser toi aussi cette application bien pratique.

Viennent maintenant les traditionnelles mises en garde : en suivant ce how-to, vous allez touchez à des fichiers système d'Android. Ceci est une opération périlleuse (d'aucun dirais "dangereuse") qui peut faire du mal à votre smartphone. Bref, si vous cassez votre Android, ce n'est pas de ma faute ! Je décline toute responsabilité en cas de pépin te forçant, cher visiteur, a réinstallé ton système voir pire.

Ceci dit en avant ! Ah au fait, il vous faut un smartphone rooté pour pouvoir mettre en place ce how-to.

Le contexte : j'ai récemment installé une ROM CyanogenMod 4.0.2 sur mon Magic. Problème, le numéro de modèle du téléphone est "T-Mobile mytouch 3G", et comme de juste, le répondeur visuel de SFR ne veut pas se lancer :

Premier constat, je suis sur un Magic, et l'appli ne le détecte pas. Donc le test doit être succin voir même simpliste. Et ça l'est. Il suffit de modifier le numéro de modèle dans le fichier /system/build.prop. Dans mon cas (CyanogenMod 4.0.2) il faut modifier le /system/build.sapphire.prop.

Note: dans la suite, les commandes à taper peuvent être suivit de mes commentaires (à ne pas taper) entre parenthèses.

Dans un premier temps, récupérer ledit fichier (visiteur, n'oublie pas de brancher ton smartphone à ton ordinateur préalablement à toute manipulation. Sans cela tu t'expose à un cuisant échec) :

adb pull /system/build.prop build.prop
adb pull /system/build.sapphire.prop build.sapphire.prop (pour les utilisateurs de ROM CyanogenMod 4.0.2)
cp build.prop build.prop.backup (car on est jamais trop prudent)
cp build.sapphire.prop build.sapphire.prop.backup (même punition)

Une fois les fichiers sur votre ordinateur éditez les (avec un éditeur qui supporte les retours à la ligne UNIX pour les BillGatesiens). Les clés à changer/ajouter sont les suivantes (dans le fichier build.sapphire.prop pour les CyanogenMod-addict et dans le build.prop pour les autres) :

ro.product.model=HTC Magic
ro.product.brand=generic
ro.product.name=htc_sapphire
ro.product.device=sapphire
ro.product.board=sapphire
ro.product.manufacturer=HTC
ro.product.locale.language=fr
ro.product.locale.region=FR
ro.board.platform=msm7k
ro.build.product=sapphire

Vous devriez en avoir un certain nombre déjà présentes. A mon humble avis, seul le ro.product.model est vraiment important. Maintenant il ne reste qu'a remettre le fichier en place :

adb remount
adb push build.sapphire.prop /system/build.sapphire.prop (pour les utilisateurs d'une ROM CyanogenMod)
adb push build.prop /system/build.prop (pour les autres)
reboot

Et après le reboot, vous devriez, une larme à l'oeil, pouvoir utiliser SFR Répondeur visuel. Cool isn't it ?

Quelques remarques en vrac. Ce petit "truc" devrait pouvoir permettre aux utilisateurs de Hero et de Dream d'utiliser le répondeur visuel. Attention, modifier l'identité peut (va) certainement avoir des effets de bords sur le reste de votre téléphone (pour ne citer que ça : HTC fait peut être le même genre de test dans l'interface du Hero). Dans tous les cas, n'oubliez pas de faire un backup de votre build.prop ou build.sapphire.prop ! Mon petit truc n'a pas été testé sur d'autre smartphone ou ROM que le HTC Magic 32B avec une ROM CyanogenMod 4.0.2, tout autre configuration est donc à tester avec précautions. N'hésitez pas à laisser le résultat de vos tests dans les commentaires.

Les informations nécessaires à ce petit "truc" ont été récupéré un peut partout sur le net, mais particulièrement sur les forum dédiés à la ROM SPF.

Enjoy !

Arnaud Dupuis

Hi,

Thanks to Sascha Manns Association Subscribers manager is now packaged for OpenSUSE 11.1 ! The package is available here, the 1-Click install is here, and the repository is available here.

I am very grateful to Sascha and David Haller for their work and their patches. I will integrate their patches upstream and maintains them (if needed).

Arnaud Dupuis

Hi,

I am falling asleep in front of my computer... Release 3.0 is ready but I have not enough remaining power to test all packages extensively tonight, so the release of Association Subscribers Manager is postponed until tomorrow.

Arnaud Dupuis