Comments on Thomson ST2030 Feature Key Sheet Templatehttps://romain.blogreen.org/blog/2011/12/thomson-st2030-feature-key-sheet-template/ Comment by Jean-Marie Favreau Since SVG is a text-based format (an XML language), you may create a script that inserts into an SVG template your top-20 numbers (you can have a black-list file to remove the unwanted numbers, the ones you don't want to flaunt on your desk).
The next step is to add a line in your crontab, that checks if your numbers has been modified, and print the new PDF in case of modification. :)

Merry Christmas!

]]>https://romain.blogreen.org/blog/2011/12/thomson-st2030-feature-key-sheet-template/#comment-1https://romain.blogreen.org/blog/2011/12/thomson-st2030-feature-key-sheet-template/#comment-1Fri, 30 Dec 2011 12:41:22 +0100 Comment by Romain TartièreHi JM!

Well, I though about writing a script for automagically filling-in the SVG document but I saw a few issues in my case and I don't think it worth the time (can be an amusing exam subject for students anyway):

  1. As you mentioned, there are some numbers I don't want to have as fast call keys (e.g. *1, 123);
  2. Another point is that the log only has the numbers, not the caller-id (i.e. real name) and in my LDAP directory, a single telephone-number can belong to multiple persons (I am considering to register places in addition to people to circumvent this limitation but I am not sure that this would really help making my life easier anyway). In such a situation, I can't rely on the directory information to retrieve the label corresponding to the number, and I have to pick a custom name myself;
  3. Some names in the LDAP directory are a bit too long and required to be shortened to fit in;
  4. A last point is grouping: I didn't want to order the numbers by how often I use them, but rather by the category they belong to (e.g. family, friends).

Taking all these rules into account would have required some non-trivial development, and as I don't plan to change these numbers every once a while, I stuck to filling-in the sheet myself.

However, in a company context, auto-filling-in the template definitively makes sense. In this case, using the same source to generate both the filled-in template (using XSLT) and the provisioning configuration files would make the fast call keys update for internal calls as easy as changing the sheet and rebooting the telephone!

Happy end of year season!

]]>https://romain.blogreen.org/blog/2011/12/thomson-st2030-feature-key-sheet-template/#comment-2https://romain.blogreen.org/blog/2011/12/thomson-st2030-feature-key-sheet-template/#comment-2Fri, 30 Dec 2011 13:29:06 +0100