David Soulayrol
9 months ago
commit
1538631d84
@ -0,0 +1,15 @@ |
||||
module.exports = { |
||||
env: { |
||||
browser: true, |
||||
commonjs: true, |
||||
es2021: true |
||||
}, |
||||
extends: [ |
||||
'standard' |
||||
], |
||||
parserOptions: { |
||||
ecmaVersion: 12 |
||||
}, |
||||
rules: { |
||||
} |
||||
} |
||||
@ -0,0 +1,2 @@ |
||||
dist |
||||
node_modules |
||||
@ -0,0 +1,5 @@ |
||||
{ |
||||
"extends": "stylelint-config-standard", |
||||
"ignoreFiles": ["**/*.min.css"] |
||||
} |
||||
|
||||
@ -0,0 +1,34 @@ |
||||
@font-face { |
||||
font-family: colombia; |
||||
src: url(/fonts/Colombia-Rp0DV.ttf); |
||||
} |
||||
|
||||
@font-face { |
||||
font-family: colombia; |
||||
src: url(/fonts/ColombiaItalic-BWGZB.ttf); |
||||
font-style: italic; |
||||
} |
||||
|
||||
body { |
||||
margin: 1em 0; |
||||
} |
||||
|
||||
h1, |
||||
h2, |
||||
h3, |
||||
h4, |
||||
h5, |
||||
h6 { |
||||
font-family: colombia, sans-serif; |
||||
margin: 1em 0 0.4em 0; |
||||
padding: 0; |
||||
} |
||||
|
||||
footer { |
||||
padding: 0; |
||||
} |
||||
|
||||
p { |
||||
margin: 0 0 0.4em 0; |
||||
padding: 0; |
||||
} |
||||
File diff suppressed because one or more lines are too long
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
@ -0,0 +1 @@ |
||||
dev/ |
||||
@ -0,0 +1,77 @@ |
||||
David Soulayrol |
||||
Français, 23 ans, célibataire. |
||||
Dégagé des obligations militaires. |
||||
|
||||
60, Les Hauts de la fontaine |
||||
34980 - COMBAILLAUX |
||||
|
||||
Tel.: 0 671 057 557 |
||||
david.soulayrol@enib.fr |
||||
Ingénieur en Développement Informatique |
||||
|
||||
Expérience professionnelle |
||||
========================== |
||||
* Stage en entreprise -- Ifremer, Centre de Brest. Durée : 5 mois |
||||
|
||||
Développement d'un logiciel de navigation en temps réel pour le |
||||
positionnement de bouées acoustiques sous-marines. |
||||
Le logiciel a été réalisé sous LabVIEW de National Instruments. Il |
||||
comprend essentiellement trois parties : manipulation de données GPS (à |
||||
l'aide d'une bibliothèque de fonctions C), réception et tri des données |
||||
provenant de l'unité acoustique BENTHOS DS-7000 à travers une liaison série |
||||
RS-232 et enfin intégration de ces données dans un algorithme de type |
||||
moindres carrés. |
||||
Ce stage m'a permis de découvrir les outils LabVIEW et MatLab. J'ai |
||||
en outre participé à l'installation de Linux (SuSE 6.1) sur plusieurs PC, |
||||
ainsi qu'à leur intégration dans le réseau du laboratoire. Cela m'a permis |
||||
d'approfondir mes connaissances sur les systèmes UNIX. |
||||
|
||||
Formation |
||||
========= |
||||
Elève Ingénieur |
||||
Actuellement en dernière année à l' Ecole Nationale d'Ingénieurs de |
||||
Brest. |
||||
|
||||
Projet de Fin d'études : ARéVi |
||||
ARéVi est un outil de gestion et de navigation au sein |
||||
d'environnements virtuels orienté agents. Il est développé sous Visual C++. |
||||
|
||||
Mon rôle consistait à implémenter une interface entre le logiciel et |
||||
des moteurs de synthèse et de reconnaissance vocale. J'ai en outre porté le |
||||
support de périphériques (gant de données) depuis une version Unix sur |
||||
Windows. |
||||
|
||||
Modules d'approfondissement suivis : |
||||
* Systèmes Temps Réel |
||||
* Intelligence Artificielle |
||||
* Interfaces |
||||
* Réalité virtuelle |
||||
|
||||
Baccalauréat Série E |
||||
Lycée Mas de Tesse, Montpellier (1994). |
||||
|
||||
Connaissances acquises |
||||
====================== |
||||
Langages maitrisés : |
||||
C, C++, Prolog, Langage G de LabVIEW. |
||||
|
||||
Langages abordés : |
||||
Assembleur (sur MC68k et Intel x86), Java, Scheme, Perl, HTML, |
||||
JavaScript. |
||||
|
||||
Systèmes d'exploitation : |
||||
Unix (Linux, System V et BSD, Irix), Windows 9x/NT, DOS. |
||||
|
||||
Systèmes temps réel : |
||||
VxWorks. |
||||
|
||||
Langue vivante : |
||||
Anglais : lu+++, parlé++, écrit+++ |
||||
|
||||
Autres activités |
||||
================ |
||||
* Administration des services réseaux pour les étudiants de l'Enib. Ce |
||||
réseau comprend une dizaine de machines sous Linux. |
||||
* Participation au projet DreamOs (www.dreamos.fr.st). |
||||
* Musique (guitare), lecture... |
||||
* Activités de plein air : marche, cerf-volant, ... |
||||
File diff suppressed because it is too large
Load Diff
Binary file not shown.
Binary file not shown.
Binary file not shown.
@ -0,0 +1,65 @@ |
||||
\documentclass[a4paper,french,arial,narrow]{europecv} |
||||
\usepackage{ucs} |
||||
\usepackage[T1]{fontenc} |
||||
\usepackage[utf8x]{inputenc} |
||||
\usepackage[frenchb]{babel} |
||||
\usepackage{graphicx} % Required to draw the logo |
||||
\usepackage[a4paper,top=1.27cm,left=1cm,right=1cm,bottom=2cm]{geometry} |
||||
\usepackage{url} |
||||
\usepackage{ifthen} |
||||
|
||||
% Type of document |
||||
\newboolean{europass} |
||||
\setboolean{europass}{true} |
||||
\newboolean{cv} |
||||
\setboolean{cv}{false} |
||||
\newboolean{details} |
||||
\setboolean{details}{false} |
||||
|
||||
% Define personal data. |
||||
\input{fragments/contact} |
||||
|
||||
\begin{document} |
||||
\begin{europecv} |
||||
\ecvpersonalinfo[5pt] |
||||
%\ecvitem{\large\textbf{Desired employment/ Occupational~field}}{\large\textbf{(Remove if not relevant)}} |
||||
|
||||
\ecvsection{Expérience professionnelle} |
||||
\input{fragments/netcentrex} |
||||
\input{fragments/atlantide} |
||||
|
||||
\ecvsection{Éducation et formation} |
||||
\input{fragments/formation} |
||||
|
||||
\ecvsection{Aptitudes et compétences personnelles} |
||||
\ecvmothertongue[5pt]{français} |
||||
\ecvitem{\large Autre(s) langue(s)}{} |
||||
\ecvlanguageheader{(*)} |
||||
\ecvlanguage{Anglais}{\ecvCOne}{\ecvCTwo}{\ecvBTwo}{\ecvCOne}{\ecvCTwo} |
||||
\ecvlanguagefooter[10pt]{(*)} |
||||
|
||||
% \ecvitem[10pt]{\large Aptitudes et compétences sociales}{} |
||||
% \ecvitem[10pt]{\large Aptitudes et compétences organisationnelles}{} |
||||
% \ecvitem[10pt]{\large Aptitudes et compétences techniques}{} |
||||
\ecvitem[10pt]{\large Aptitudes et compétences informatiques}{ |
||||
\begin{itemize} |
||||
\item \input{fragments/skills_languages} |
||||
\item \input{fragments/skills_protocols} |
||||
\item \input{fragments/skills_tools} |
||||
\item \input{fragments/skills_systems} |
||||
\item \input{fragments/skills_methods} |
||||
\end{itemize} |
||||
} |
||||
\ecvitem[10pt]{\large Aptitudes et compétences artistiques}{ |
||||
\begin{itemize} |
||||
\item pratique de la guitare |
||||
\end{itemize} |
||||
} |
||||
% \ecvitem[10pt]{\large Other skills and competences}{Replace this text by a description of these competences and indicate where they were acquired (remove if not relevant).} |
||||
\ecvitem{\large Permis de conduire}{B} |
||||
|
||||
\ecvsection{Additional information} |
||||
\ecvitem{}{\textbf{Personal interests}} |
||||
\ecvitem{}{\input{fragments/interests}} |
||||
\end{europecv} |
||||
\end{document} |
||||
@ -0,0 +1,24 @@ |
||||
\ifthenelse{\boolean{europass}}{ |
||||
\ecvname{\textbf{David Soulayrol}} |
||||
\ecvfootername{David Soulayrol} |
||||
%\ecvaddress{__EXT_STREET, __EXT_CITY (France)} |
||||
%\ecvtelephone[__EXT_MOBILE]{__EXT_PHONE} |
||||
\ecvemail{\url{david@soulayrol.name}} |
||||
\ecvnationality{Française} |
||||
\ecvdateofbirth{11 Mai 1976} |
||||
\ecvgender{Masculin} |
||||
\ecvfootnote{\url{http://david.soulayrol.name}} |
||||
}{ |
||||
\firstname{David} |
||||
\familyname{Soulayrol} |
||||
\ifthenelse{\boolean{details}}{ |
||||
\title{Expériences} |
||||
}{ |
||||
\title{Curriculum Vit\ae} |
||||
} |
||||
%\address{__EXT_STREET}{__EXT_CITY} |
||||
%\mobile{__EXT_MOBILE} |
||||
%\phone{__EXT_PHONE} |
||||
\email{david@soulayrol.name} |
||||
\extrainfo{\url{http://david.soulayrol.name}} |
||||
} |
||||
@ -0,0 +1,5 @@ |
||||
Membre de l'APRIL (\url{http://april.org}). |
||||
\newline{} |
||||
Participation à des projets libres divers, traduction d’articles et |
||||
d’applications libres. |
||||
|
||||
@ -0,0 +1,3 @@ |
||||
Littérature, musique, jardinage, voyages. |
||||
\newline{} |
||||
Pratique du tir à l'arc. |
||||
@ -0,0 +1,22 @@ |
||||
\ifthenelse{\boolean{europass}}{ |
||||
\ecvitem{Dates}{Décembre 2011 $\rightarrow$} |
||||
\ecvitem{Fonction ou poste occupé}{Ingénieur en Recherche et Développement} |
||||
\ecvitem{Principales activités et responsabilités}{TODO} |
||||
\ecvitem[15pt]{Nom et adresse de l'employeur}{ |
||||
Nexcom Systems -- 4 Rue Ampère, BP30255, 22303 Lannion (France)} |
||||
}{} |
||||
|
||||
\ifthenelse{\boolean{cv}}{ |
||||
\ifthenelse{\boolean{details}}{ |
||||
\cventry{2006 -- }{Ingénieur R\&D}{NetCentrex}{Lannion}{}{ |
||||
NEXCOM Systems est un cabinet d’architecture technique, de |
||||
formation et de réalisation logicielle spécialisé dans le |
||||
domaine des nouveaux réseaux de télécommunications. |
||||
\\ |
||||
\skills{Linux (Debian), C, Java, protocole SIP, JSR289} |
||||
} |
||||
}{ |
||||
\cventry{décembre 2010-- }{Ingénieur R\&D}{Nexcom Systems}{Lannion}{}{} |
||||
} |
||||
}{} |
||||
|
||||
@ -0,0 +1,2 @@ |
||||
Connaissance approfondie du C, C++, Python, XML. Bonne connaissance de |
||||
Java, JavaScript, Lisp, Lua, XHTML, XSLT, Vala et notions de Sed, Awk, PHP. |
||||
@ -0,0 +1 @@ |
||||
Pratiques agiles, UML. |
||||
@ -0,0 +1 @@ |
||||
Internet (HTTP, IMAP, SMTP, \ldots), téléphonie (SIP, SDP), XMPP, CORBA. |
||||
@ -0,0 +1 @@ |
||||
Connaissance approfondie des environnements GNU/Linux (en particulier Debian). |
||||
@ -0,0 +1,3 @@ |
||||
GNU \textit{Autotools} et Make, bibliothèques C GLib, GTK+, oSIP, |
||||
bibliothèque standard C++, bibliothèque standard Python et lxml, |
||||
Emacs, jQuery, Gestion de version (git, subversion, bazaar) \ldots |
||||
@ -0,0 +1,38 @@ |
||||
FRAGMENTS := $(shell ls fragments/*.tex)
|
||||
|
||||
SCRIPT := ' \
|
||||
/__EXT_\w*/ { \
|
||||
while (match($$0, /__EXT_\w*/, m)) { \
|
||||
if (!ENVIRON[m[0]]) { \
|
||||
next \
|
||||
} \
|
||||
sub(/__EXT_\w*/, ENVIRON[m[0]]); \
|
||||
} \
|
||||
sub(/%/, ""); \
|
||||
} \
|
||||
{ print }'
|
||||
|
||||
.PHONY: all clean distclean |
||||
|
||||
all: |
||||
rm -f fragments/contact.tex
|
||||
$(MAKE) cv.pdf experience.pdf europass.pdf
|
||||
|
||||
clean: |
||||
rm -f *.aux *.log *.out
|
||||
|
||||
distclean: clean |
||||
rm -f *.dvi *.pdf fragments/contact.tex
|
||||
|
||||
fragments/contact.tex: fragments/contact.tex.in |
||||
awk -v ad_street="$(CV_ADDRESS_STREET)" \
|
||||
-v ad_city="$(CV_ADDRESS_CITY)" \
|
||||
-v ph_mobile="$(CV_PHONE_MOBILE)" \
|
||||
-v ph_home="$(CV_PHONE_HOME)" \
|
||||
$(SCRIPT) $< > $@
|
||||
|
||||
%.dvi: %.tex ${FRAGMENTS} fragments/contact.tex |
||||
latex $<
|
||||
|
||||
%.pdf: %.dvi |
||||
dvipdf $< $@
|
||||
@ -0,0 +1,14 @@ |
||||
La génération du document repose sur la police de caractères *Latin Modern* qui peut être télé-chargée depuis l'adresse suivante. |
||||
|
||||
http://www.gust.org.pl/projects/e-foundry/latin-modern |
||||
|
||||
L'installation de la police pour `groff` est grandement facilitée grâce au script `install-font.sh` de Peter Schaffter (merci à lui). |
||||
|
||||
http://www.schaffter.ca/mom/mom-06.html#install-font |
||||
|
||||
Pour l'installation, copier le script dans le répertoire contenant les fichiers de l'archive, et entrer les lignes suivantes avec les droits de l'utilisateur `root`. Le processus est interactif : donner les réponses proposées par défaut aux deux questions. Le drapeau `-s` signifie une installation dans `/usr/share/groff`, alors que `-l` (par défaut) procède à une installation dans `/usr/local/share/groff`. |
||||
|
||||
./install-font.sh -s -F LM -f +R lmroman12-regular.otf |
||||
./install-font.sh -s -F LM -f +B lmroman12-bold.otf |
||||
./install-font.sh -s -F LM -f +I lmroman12-italic.otf |
||||
|
||||
@ -0,0 +1,99 @@ |
||||
--- |
||||
title: "How to hide long C headers" |
||||
date: 2010-03-29 |
||||
lang: en |
||||
layout: document.njk |
||||
--- |
||||
|
||||
The problem came out to me because some people or teams embed their |
||||
changelog in the source file headers. |
||||
|
||||
--- |
||||
|
||||
This gives something like this: |
||||
|
||||
/** |
||||
* @file MySource.cpp |
||||
* @desc a Foo objects protubazor. |
||||
* @date 29/03/2009 |
||||
* |
||||
* MODIFICATIONS: |
||||
* 2009-04-02: jsmith: Removed a useless variable. |
||||
* 2009-04-03: jsmith: Simplified the protubazor algorithm. |
||||
* 2009-06-10: jdoe: Fixed compilation warning. |
||||
*/ |
||||
|
||||
They will argue that this is the best way to check why a line has |
||||
changed in the past for example. I disagree with this. First, there |
||||
should be a file dedicated to the whole project history to trace |
||||
important updates. In GNU project, this is the **ChangeLog** |
||||
file. But above all, sources tracking is the very *raison d'être* of |
||||
version control. Every commit should be atomic and provide a |
||||
meaningful comment. If commits are correctly described, writing a |
||||
changelog inside the source is, at best, duplication of information, |
||||
and I *hate* that. |
||||
|
||||
Besides, I think this is a very annoying habit because this |
||||
information will grow with time and eventually become as large as the |
||||
useful part of your source file. At last, working on these files will |
||||
involve lots of scrolling just to find the beginning of the code. |
||||
|
||||
Anyway, there are those situations where I have no choice but to obey, |
||||
or to adapt myself. The solution I found is to hide these annoying |
||||
lines until I get forced to edit them (and then quickly hide them |
||||
again). To achieve this, I've written a function to customize the |
||||
**[hideshow minor mode][HS]** from **[emacs][EMACS]** behaviour on |
||||
file headers. It can be loaded this way for example: |
||||
|
||||
(load-library "hideshow") |
||||
(add-hook 'c++-mode-hook 'hs-minor-mode) |
||||
(add-hook 'c-mode-hook 'hs-minor-mode) |
||||
|
||||
**[hideshow][HS]** allows you to hide blocks of code. The meaning of |
||||
*blocks* depends on the language you are editing, I mean the current |
||||
major-mode. When hidden, the block is replaced by an ellipsis by |
||||
default, but the `hs-set-up-overlay` function can be used to customize |
||||
what is drawn inside a hidden block. |
||||
|
||||
In the following implementation, I tweak the hideshow overlay so as to |
||||
indicate the number of missing lines in hidden blocks. If I detect |
||||
that the given block is a kind of comment and is at the beginning of |
||||
the file, I also search for the **MODIFICATIONS:** token, which is used to |
||||
introduced those damn changelogs. If I found it, I don't really hide |
||||
the block, but display its content minus everything following the |
||||
token (which I replace with the count of hidden lines). |
||||
|
||||
(setq hs-set-up-overlay |
||||
(defun ds-lib-hs-overlay (ov) |
||||
(let ((content (format " [%d lines]..." |
||||
(count-lines (overlay-start ov) |
||||
(overlay-end ov))))) |
||||
(when (and (< (overlay-start ov) 80) (eq 'comment (overlay-get ov 'hs))) |
||||
(goto-char (point-min)) |
||||
(goto-char (point-min)) |
||||
(when (search-forward " MODIFICATIONS:" (overlay-end ov) t) |
||||
(setq content (format "%s [%d lines]...\n */ " |
||||
(buffer-substring (overlay-start ov) (point)) |
||||
(- (count-lines (point) (overlay-end ov)) 2))))) |
||||
(overlay-put ov 'display content)))) |
||||
|
||||
(add-hook 'c++-mode-hook 'hs-hide-block t) |
||||
(add-hook 'c-mode-hook 'hs-hide-block t) |
||||
|
||||
Thus, the sample given in the beginning would be displayed this way: |
||||
|
||||
/** |
||||
* @file MySource.cpp |
||||
* @desc a Foo objects protubazor. |
||||
* @date 29/03/2009 |
||||
* |
||||
* MODIFICATIONS: [3 lines]... |
||||
*/ |
||||
|
||||
Note that even if it seems to be displayed because I draw a large part |
||||
of it, the block is actually in an hidden state. That means that it |
||||
must be showed again before it can be edited at all. |
||||
|
||||
|
||||
[EMACS]: http://www.gnu.org/software/emacs/ |
||||
[HS]: http://www.gnu.org/software/emacs/manual/html_node/emacs/Hideshow.html |
||||
@ -0,0 +1,108 @@ |
||||
--- |
||||
title: Identifying logical contexts in logs |
||||
date: 2012-05-05 |
||||
lang: en |
||||
layout: document.njk |
||||
--- |
||||
|
||||
Some months ago, I had to track a bug for which appeared on one SIP |
||||
call, in a pre-production environment. So I had to dig a very lengthy |
||||
log file, with lots of information about many mixed calls. |
||||
|
||||
This situation is not really a problem if you know exactly the call |
||||
you are tracking, thanks to its Call-ID or indirectly with a From or |
||||
To tag for example. Hopefully, your program already offers interesting |
||||
logs to address the problem, or you can provide a modified program to |
||||
gather more information. If not, you know the rest of the week will be |
||||
a pain. |
||||
|
||||
--- |
||||
|
||||
In this case, I was lucky enough to have the opportunity to provide a |
||||
new binary with lots of logs in the area which caused the bug, but I |
||||
still had to search through thousand of lines to identify the path |
||||
which lead one call to trigger the error. |
||||
|
||||
So I came up with a simple **[python](http://python.org)** script which |
||||
parsed the file for me and built a map from the logs I was interested |
||||
in. Each entry of the map was identified by an ID which was unique to |
||||
a call, and contained all the logs for this call in order of |
||||
appearance in the file. To achieve this, the script relied on a |
||||
regular expression which identified the logs I had added. At last, the |
||||
script dumped those contexts, which were far easier to read than the |
||||
initial file. |
||||
|
||||
Then I got a new job, and I forgot this... |
||||
|
||||
Until this week, when I had to identify in a very long file some |
||||
sixteen calls out of more than one thousand which were behaving |
||||
differently. So I wrote the following script in the vein of the |
||||
previous one. It can be quite easily adapted to other problems by |
||||
modifying the `PATTERN` constant. It can read multiple log files, and |
||||
it can output the number of contexts found, the number of lines read |
||||
for each one of these contexts, and dump them. I think it is self |
||||
explanatory, and it comes with inline help. |
||||
|
||||
|
||||
#!/usr/bin/env python |
||||
|
||||
# argparse means Python 2.7 is required. |
||||
import argparse |
||||
import re |
||||
|
||||
# The pattern can be customized to adapt the program behaviour to the |
||||
# kind of logs to be analysed. It must provide a group named `key' |
||||
# which will be used to identify the logs belonging to a same context. |
||||
PATTERN = '.+ \[INFO\] .* with Call-ID = (?P<key>[a-zA-Z0-9@\.-]+)' |
||||
|
||||
def build_contexts(filenames): |
||||
contexts = {} |
||||
for n in filenames: |
||||
with open(n) as f: |
||||
e = re.compile(PATTERN) |
||||
while True: |
||||
l = f.readline() |
||||
if '' == l: |
||||
break |
||||
m = e.match(l) |
||||
if not m is None: |
||||
k = m.group('key') |
||||
if not k in contexts: |
||||
contexts[k] = [] |
||||
contexts[k].append(l.strip()) |
||||
|
||||
return contexts |
||||
|
||||
def display_context(contexts, key, cmd): |
||||
print '%s: %s' % (key, str(len(contexts[key])) + ' lines.' if cmd.summary else '') |
||||
if cmd.list: |
||||
for l in contexts[key]: |
||||
print '\t', l |
||||
|
||||
def handle_contexts(contexts, cmd): |
||||
if not cmd.key is None: |
||||
if cmd.key in contexts: |
||||
display_context(contexts, cmd.key, cmd) |
||||
|
||||
elif cmd.list or cmd.summary: |
||||
for key in contexts: |
||||
display_context(contexts, key, cmd) |
||||
|
||||
print 'Total:', len(contexts), 'contexts' |
||||
|
||||
# Main |
||||
parser = argparse.ArgumentParser( |
||||
description='Correlates log lines.', |
||||
epilog='See the PATTERN variable in the code to suit your needs') |
||||
|
||||
parser.add_argument('files', metavar='file', type=str, nargs='+', |
||||
help='the file to inspect') |
||||
parser.add_argument('--get', action='store', dest='key', |
||||
help='search only the context with this key') |
||||
parser.add_argument('--list', action='store_true', |
||||
help='dump the contexts content') |
||||
parser.add_argument('--summary', action='store_true', |
||||
help='print a summary for each context found') |
||||
|
||||
args = parser.parse_args() |
||||
handle_contexts(build_contexts(args.files), args) |
||||
@ -0,0 +1,298 @@ |
||||
--- |
||||
title: Using Firefox Micro-Summaries |
||||
date: 2007-04-29 |
||||
lang: en |
||||
layout: document.njk |
||||
--- |
||||
|
||||
What are you doing when you're a geek and a nice girl is crying for |
||||
her own refurbed Apple laptop ? Yes, you find a way to monitor the |
||||
Store so as to be the first to be ready to buy next time. |
||||
|
||||
--- |
||||
|
||||
## When geeks can be useful too |
||||
|
||||
Karine recently decided that she wanted a laptop. I cannot remember |
||||
why, but she also decided that a MacBook would be definitively |
||||
cool. So we went to town and had a look at the hardware. Karine took |
||||
the time to search for benchmarks and tests to be comforted in her |
||||
choice. We started to track [eBay][] and Apple |
||||
*Refurb*. In the end, she realized that the *Refurb* offered the |
||||
warranties that she was looking for, with an interesting price saving. |
||||
|
||||
Once the choice was made, began the time of the [Apple Store][] *Page |
||||
Refresh Syndrom*. The drama occured the day she was having a break, |
||||
and then the *one-click* susbscription refused to work before all the |
||||
nice MacBook had found new happy owners. |
||||
|
||||
## Remember your greatest quality is laziness |
||||
|
||||
There are many ways to monitor a page and to be notified when it is |
||||
updated. The easiest solution is to rely on what you can |
||||
find. Remember: *never reinvent the wheel* (or only if it's fun). |
||||
|
||||
We first tried to find a plugin for *Firefox* that would show up a |
||||
notification when a page is updated and we installed [Notify][]. But |
||||
the plugin was sending far too false positive notifications (and |
||||
actually, it continues to do so while I'm writing this). I don't |
||||
pretend it does not work, but it didn't the job we wanted out of the |
||||
box, so we tried to find something else. |
||||
|
||||
I could have written some Python script to crawl the *Refurb* for us |
||||
and provide us some summary of the available laptops. The most |
||||
difficult part of this solution would have been to handle the |
||||
notification: Karine was mainly using MS Windows both at work and at |
||||
home, and I didn't want to search for a graphical solution on this |
||||
platform. The notification could have been sent by mail, but I didn't |
||||
enjoy this solution at the moment, thinking it was too slow for our |
||||
need (I am not sure I have the same opinion today). |
||||
|
||||
Then Karine found a short description about the *Live Titles*, or |
||||
*Micro Summaries* of *Firefox*. After some search, I found out that |
||||
this was in fact a way to define a dynamic bookmark label. I first |
||||
found [some samples](http://userstyles.org/livetitle) and later some |
||||
documentation to start with. I decided that I wanted to know more |
||||
about it. |
||||
|
||||
You could say (will you ?) that this kind of notification is a very |
||||
shy one, and we have to check frequently the *Firefox* window to see |
||||
it some good news happened. And you would be right. But please |
||||
consider that for someone using a lot its computer and the web |
||||
browser, it's more interesting to have a quick glance at a label on |
||||
the windows than to have to refresh a page from a somewhat loaded |
||||
server. And *that* was what scratched my itch at this very moment, |
||||
nothing else. |
||||
|
||||
## Time to write some code |
||||
|
||||
### Micro Summaries... What's this? |
||||
|
||||
Micro summaries simply consist of one XSL stylesheet which will be |
||||
associated to all bookmarked pages matching a given pattern. When you |
||||
bookmark a page whose URL matches a micro summary definition, the *Add |
||||
Bookmark* dialog provides you a combo box to define the title instead |
||||
of a text field, thus giving you the choice to set a static label or |
||||
to use the existing dynamic one. |
||||
|
||||
[This page](http://wiki.mozilla.org/Microsummaries) introduces the |
||||
*Firefox* *micro summaries*, but |
||||
[this one](http://developer.mozilla.org/en/docs/Creating_a_Microsummary) |
||||
is far more interesting when it comes to the moment you have to write |
||||
your own. |
||||
|
||||
At first, I was worried by the fact that all the provided samples were |
||||
very simple. They were often composed of one or two labels and some |
||||
values easely extracted from the bookmarked page. Then I realized that |
||||
they were XSLT documents after all, and that I probably could use all |
||||
the power of XSL transformations to build the label I wanted. |
||||
|
||||
### Let's dive into it |
||||
|
||||
First, micro summaries are XML documents, and they make use of XML |
||||
namespaces. It is very important to know about namespaces because a |
||||
micro summary document contains at least tags from two distinct ones: |
||||
`microsummaries`, and `XSL` of course. |
||||
|
||||
A micro summary definition needs very few information. The root tag is |
||||
`generator`, from the `microsummaries` namespace, and has a name |
||||
attribute. The root tag has at least two children. |
||||
|
||||
- `transform` holds the XSL sheet. The XSL namespace |
||||
must be present here. |
||||
|
||||
- `pages` provides one or more `include` tags, each one |
||||
holding a regular expression that will be used to match a page URL |
||||
for which the micro summary can be used. |
||||
|
||||
An additional `update` tag which specifies that the Summary will have |
||||
to be refreshed every five minutes. The update involves retrieving the |
||||
data from the website of course. You will find some other tags in |
||||
documentation which I confess I didn't try to study. All I needed was |
||||
there. |
||||
|
||||
::XML |
||||
<?xml version="1.0" encoding="UTF-8"?> |
||||
<generator xmlns="http://www.mozilla.org/microsummaries/0.1" name="Applestore"> |
||||
<template> |
||||
<transform xmlns="http://www.w3.org/1999/XSL/Transform" version="1.0"> |
||||
<!-- All XSLT code goes here --> |
||||
</transform> |
||||
</template> |
||||
<pages> |
||||
<include>http://store\.apple\.com/Apple/WebObjects/francestore\.woa/.*</include> |
||||
</pages> |
||||
<update interval="5" /> |
||||
</generator> |
||||
|
||||
|
||||
### Now, the AppleStore application |
||||
|
||||
What I tried to retrieve first was some value to determine if MacBook |
||||
laptops were available. This could be done by searching the lines |
||||
announcing the refurbed products and looking for the one displaying |
||||
MacBook. So, I sit down and managed to remember the syntax of XPath |
||||
expressions to produce something like this: |
||||
|
||||
/html/body//form/table[@id='rep']/tbody/tr/td/b |
||||
|
||||
Which gave me the following result. |
||||
|
||||
![Firefox displaying the result of the first XPath expression][screenshot-1] |
||||
|
||||
**Caution:** Note that the XPath expressions given here rely on the |
||||
french refurb pages. They shall be adapted to get something |
||||
operational in other languages. |
||||
|
||||
Of course, in the end, I would have kept only the text and get rid of |
||||
pictures (but it was cool to display this for the screenshot, and it |
||||
helps to understand what I have extracted from the page). |
||||
|
||||
From there I thought I only had to search the lines where I could find |
||||
the string MacBook. But I realized that I needed to differentiate |
||||
MacBook and MacBook Pro. And I didn't know how to write some condition |
||||
with these inputs to distinguish both of them. |
||||
|
||||
So I tried to gather another source of information in the page. |
||||
Meanwhile, I also decided to not only detect if MacBook laptops were |
||||
available but also to count how many there were. Finally, I wrote the |
||||
following expression. |
||||
|
||||
/html/body//form/table[@id='rep']/tbody/tr/td/span/b[contains(normalize-space(.), 'Refurb')] |
||||
|
||||
And this time, I got: |
||||
|
||||
![Firefox displaying the result of the final XPath expression][screenshot-2] |
||||
|
||||
From these strings, all I had to do was to select the ones related to |
||||
MacBooks and to count them. To extract these lines, I chose to use the |
||||
*White* and *Black* words, which only appeared in lines concerning |
||||
MacBooks. |
||||
|
||||
To make sure the method was correct, I also decided to count the lines |
||||
related to MacBook Pro, and then even the ones for iMacs. In these |
||||
cases, I simply had to search for *MacBook Pro* and *iMac* terms on |
||||
the lines. |
||||
|
||||
Counting the lines is a bit tricky because XLST does not provide |
||||
*lvalues*. There is no way to define anything else than constants. So |
||||
computing values can be achieved using recursivity only. In the |
||||
following template, `nodes` is the list of gathered strings, `item` is |
||||
the pattern we are looking for. The inner variable `count` is used to |
||||
carry the temporary value of the result count through iterative calls. |
||||
|
||||
::XML |
||||
<template name="count"> |
||||
<param name="nodes" /> |
||||
<param name="item" /> |
||||
<choose> |
||||
<when test="$nodes"> |
||||
<variable name="node" select="$nodes[1]" /> |
||||
<variable name="count"> |
||||
<call-template name="count"> |
||||
<with-param name="nodes" select="$nodes[position() != 1]" /> |
||||
<with-param name="item" select="$item" /> |
||||
</call-template> |
||||
</variable> |
||||
<choose> |
||||
<when test="contains($node, $item)"> |
||||
<value-of select="$count + 1" /> |
||||
</when> |
||||
<otherwise> |
||||
<value-of select="$count" /> |
||||
</otherwise> |
||||
</choose> |
||||
</when> |
||||
<otherwise>0</otherwise> |
||||
</choose> |
||||
</template> |
||||
|
||||
### Building the label |
||||
|
||||
Counting lines containing a given item is only a matter of calling the |
||||
previous template with the list of lines and the wanted pattern. The |
||||
result of the call gives the count value. Here is an excerpt of the |
||||
code showing how is displayed the count of white MacBook laptops. Note |
||||
the `text` element to display some text around the value computed. |
||||
|
||||
::XML |
||||
<text>MacBooks: </text> |
||||
<variable name="count-macbooks-w"> |
||||
<call-template name="count"> |
||||
<with-param name="nodes" select="$entries" /> |
||||
<with-param name="item" select="string('White')" /> |
||||
</call-template> |
||||
</variable> |
||||
<value-of select="$count-macbooks-w" /> |
||||
<text>w </text> |
||||
|
||||
### Registering the micro summary |
||||
|
||||
If no micro summary is registered in your browser, or if the `pages` |
||||
directives do not match the page you are currently watching, then |
||||
trying to bookmark will raise the following dialog. |
||||
|
||||
![The default Add bookmark dialog][screenshot-3] |
||||
|
||||
Micro summaries can be registered using a simple script. Its main job |
||||
will be to check that the browser can register the sheet, and then a |
||||
simple line will suffice. |
||||
|
||||
::HTML |
||||
<script> |
||||
const warning = "Sorry, you need a microsummary-enabled browser like Firefox 2.0"; |
||||
function addGenerator(url) { |
||||
if (typeof window.sidebar == "object" && |
||||
typeof window.sidebar.addMicrosummaryGenerator == "function") |
||||
window.sidebar.addMicrosummaryGenerator(url); |
||||
else |
||||
alert(warning); |
||||
} |
||||
</script> |
||||
<button onclick="addGenerator('http://10.165.16.164/applestore.xml')"> |
||||
Install the Apple Store MacBook microsummary!</button> |
||||
|
||||
Again, there is more than one way to do this. But remember it was only |
||||
a quick hack to monitor the store and a nice way have an overview of |
||||
the technology. |
||||
|
||||
Now, if you used the previous script, and are trying to bookmark a |
||||
page, then your *Add Bookmark* dialog is updated so that you can |
||||
choose the *live title* instead of typing a static one. Hey Karine, |
||||
there are laptops available! |
||||
|
||||
![The updated Add bookmark dialog][screenshot-4] |
||||
|
||||
The complete micro summary code for the Apple store can be downloaded |
||||
[here](/objects/files/micro_summaries). Note that the short script I |
||||
used to register it needs its complete location. |
||||
|
||||
## Waiting for kisses |
||||
|
||||
As said before, micro summaries are a very tiny way to notify |
||||
something to the user. If the content of the title is rather |
||||
important, the best use is probably to store it on your personal |
||||
toolbar. |
||||
|
||||
![The micro summary in action][screenshot-5] |
||||
|
||||
To conclude, I shall add that I discovered quite recently that micro |
||||
summaries were stored in your Firefox profile under the |
||||
`microsummary-generators` directory (I am using Firefox under Debian |
||||
to do this). It is very easy to remove a generator simply by deleting |
||||
the XML file stored there. |
||||
|
||||
For the record, a week later the Apple Store offered many refurbed |
||||
laptops and Karine bought her MacBook. And after that, she still tells |
||||
I'm staying too much in front of my computer! |
||||
|
||||
|
||||
[Apple Store]: <http://store.apple.com> |
||||
[eBay]: <http://www.ebay.fr> |
||||
[Notify]: <https://addons.mozilla.org/en-US/firefox/addon/3149> |
||||
|
||||
[screenshot-1]: <screenshot-xpath-1.png> |
||||
[screenshot-2]: <screenshot-xpath-2.png> |
||||
[screenshot-3]: <screenshot-live_titles-1.png> |
||||
[screenshot-4]: <screenshot-live_titles-2.png> |
||||
[screenshot-5]: <screenshot-live_titles-3.png> |
||||
|
After Width: | Height: | Size: 7.2 KiB |
|
After Width: | Height: | Size: 8.0 KiB |
|
After Width: | Height: | Size: 13 KiB |
|
After Width: | Height: | Size: 28 KiB |
|
After Width: | Height: | Size: 20 KiB |
File diff suppressed because it is too large
Load Diff
@ -0,0 +1,53 @@ |
||||
--- |
||||
title: "Accueil" |
||||
permalink: false |
||||
--- |
||||
Je suis ingénieur diplômé de l'[École Nationale d'Ingénieurs de Brest][ENIB]. Je travaille actuellement dans le domaine de la domotique, à [Lannion][LANNION]. |
||||
|
||||
Je suis passionné d'informatique, de littérature et de musique. Je suis adhérent à l'[April][APRIL], [nooSFere][NOOSFERE] et au [Club Présences d'Esprits][CPE]. Je suis le président de l'association [Pérégrine][PEREGRINE] à Lannion et membre du bureau de l'hébergeur alternatif et solidaire [Ti Nuage][TINUAGE]. |
||||
|
||||
Dans une autre vie, j'ai vécu à [Montpellier][Montpellier], [Brest][BREST] ou près de [Blois](https://fr.wikipedia.org/wiki/Blois). J'ai pratiqué la danse sur glace et le tir à l'arc. Plus récemment, j'ai été co-fondateur et président de l'association [Scorfel][SCORFEL]. |
||||
|
||||
## Curriculum Vitae |
||||
|
||||
Mon parcours professionel est détaillé à [cette adresse](cv/2022/2022_cv_dsoulayrol.pdf) ([sources](cv/2022) pour [groff](https://www.gnu.org/software/groff/)). |
||||
|
||||
Des itérations passées sont toujours disponibles : |
||||
|
||||
- à la sortie de l'école en [2000](cv/2000_cv_dsoulayrol.txt) |
||||
- au moment où je m'apprête à quitter Atlantide pour Lannion, [fin 2005](cv/20051010_cv_dsoulayrol.pdf) |
||||
- En 2012, lorsque je suis chez Nexcom, j'expérimente différents modèles avec [LaTeX](https://www.latex-project.org/) et je produis un [CV](cv/2012/2012_cv.pdf), un document détaillant mes [expériences professionnelle](cv/2012/2012_experiences.pdf), et un « [europass](cv/2012/2012_europass.pdf) » ([sources](cv/2012)). |
||||
|
||||
## Contact |
||||
|
||||
Je peux facilement être joint aux adresses suivantes. |
||||
|
||||
* <a href="mailto:david@soulayrol.name">david@soulayrol.name</a> |
||||
* <a href="xmpp:david@ti-nuage.fr">david@ti-nuage.fr</a> sur XMPP. |
||||
* <a href="https://pouet.chapril.org/@ds">@ds@pouet.chapril.org</a> sur Mastodon. |
||||
|
||||
Le code que je produis de nos jours est stocké chez l'hébergeur alternatif Ti Nuage, et de temps en temps par nécessité chez Github. |
||||
|
||||
* [Ti-Nuage](https://apps.ti-nuage.fr/gitea/david) |
||||
* [Github](https://github.com/dsoulayrol) |
||||
|
||||
## Archives |
||||
|
||||
Les documents que j'ai conservés, ou que j'exhume à l'occasion de mon disque dur... |
||||
|
||||
* [La traduction](documents/le-monde-merveilleux-de-linux-2.6) du document [Wonderful World of Linux 2.6](http://www.kniggit.net/wwol26.html), Copyright 2003, Joseph Pranevich (jpranevich AT kniggit.net). |
||||
* [Un article sur l'utilisation des *micro-summaries* dans Firefox en 2007](documents/using-firefox-micro-summaries), en anglais. |
||||
* [Un script Python pour isoler des blocs dans un long fichier de *logs* ](documents/identifying-logical-contexts-in-logs), en anglais. |
||||
* [Une astuce pour masquer les longs entêtes d'un fichier source dans Emacs](documents/how-to-hide-long-c-headers) en anglais. |
||||
|
||||
|
||||
[APRIL]: <https://april.org> |
||||
[BREST]: <https://fr.wikipedia.org/wiki/Brest> |
||||
[CPE]: <http://www.presences-d-esprits.com> |
||||
[ENIB]: <http://www.enib.fr> |
||||
[LANNION]: <http://fr.wikipedia.org/wiki/Lannion> |
||||
[MONTPELLIER]: <https://fr.wikipedia.org/wiki/Montpellier> |
||||
[NOOSFERE]: <https://noosfere.org> |
||||
[PEREGRINE]: <https://www.associations.lannion.bzh/index.php?option=com_content&view=article&id=135:peregrine> |
||||
[SCORFEL]: <httsp://scorfel.fr> |
||||
[TINUAGE]: <https://ti-nuage.fr> |
||||
@ -0,0 +1,24 @@ |
||||
<!DOCTYPE HTML> |
||||
{% import "footer.njk" as footer %} |
||||
{% if lang == undefined %}{% set lang = 'fr' %}{% endif %} |
||||
{% set lang = moment.locale(lang) %} |
||||
<html lang="{{ lang }}"> |
||||
<head> |
||||
<title>{{ site.title }} | {{ title }}</title> |
||||
<meta charset="utf-8"> |
||||
<meta name="author" content="David Soulayrol"> |
||||
<meta name="generator" content="Metalsmith" /> |
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0"> |
||||
<link rel="stylesheet" href="/css/simple.min.css"> |
||||
<link rel="stylesheet" href="/css/ds.css"> |
||||
</head> |
||||
<body> |
||||