Oscar in El arte de programar presents an SMS -> Email -> SMS gateway that he has just set up for use in Spain. It is a neat tool, but I would have thought that each phone company should have this on offer as part of their service. I believe that BT in the UK, before they became O2, had some domain like mmail.com and messages to <phone number>@mmail.com appeared as SMS messages on your phone. You could also send an SMS to an email address - but no, this does not seem to work with Movistar.
José Luis Sánchez in avemundi continues his series of learnings since the release of Cuaderno de Bitácora (version 6) and el Puchero (version 4) last November.
error #2: Usar registro ligado a máquina y complicar el proceso de registro del programa (creating a registration process tied to an individual PC and complicating the registration). A registration process based on a machine is bad for two reasons. Firstly it gives the user a licence to use the software on only one machine, so that when they change machine they have to ask for a new key. This puts a lot of people off evaluating the software because of the uncertainty it creates in the mind. Secondly, this type of process complicates registration for both the user and the supplier. José believes that in making this decision for his two software products he has reduced his potential sales. He is going to release versions with a more friendly registration process soon. [Note: I agree with his diagnosis because I looked at his registration process and decided not to bother with the download. On the other hand, I downloaded and used an evaluation version of Joel Spolsky's City Desk for some months before finally being "persuaded" to purchase a full licence when Joel offered a small discount. I would suggest that the option to receive upgrades after registration was sufficient incentive to register for someone who genuinely finds a program useful. ]
Rafa Carmona in Thefull comments on the importance of using version control when writing source code and explains how to tag the executable with the version number directly from the source code management system (CMS). Most of these have some sort of macro which looks like this:
#define VERSION ' $Id: $' or #define VERSION ' $Revision: $
which you write into your source code. On returning the code to the CMS, the $Id:$, or $Revision:$ automagically gets replaced with the appropriate information. When the code is compiled it is possible to view this information in the executable and then know exactly which version of the source code the executable was produced from. This simplifies the tracking down of bugs reported by users.
Technorati tag: programming
![[Image]](../../Images/MadeWithCityDesk.gif){kind=small}