Le coComment nouveau est arrivé [fr]

[en] With the new coComment extension activated, browse to this article by 24heures. Click on the coComment logo once. Don't spill your coffee.

Je parlerai plus longuement de la nouvelle version de [coComment](http://cocomment.com) qui vient d’être déployée (après l’annonce officielle, par exemple), mais je tenais à vous montrer ceci avant de filer à [Paléo](http://paleo.ch).

1. Avec un navigateur FireFox ([ou Flock!](http://www.cocomment.com/teamblog/?p=94 “Et avec la nouvelle extension, plus même besoin de convertir, ça marche d’office!”) muni de [la magnifique extension coComment](http://cocomment.com/tools/extension-install “Réinstallez la nouvelle version pour plus de sécurité — mais je ne suis pas certaine que ce soit nécessaire.”), rendez-vous sur [la page de l’article 24heures sur les blogs](http://www.24heures.ch/vqhome/edition/ls/blogs_200706.edition=ls.html “Profitez, ça reste en ligne 2 jours max.”). *Edit: [version archivée ici on dirait](http://www.24heures.ch/vqhome/archives_2006/blogs_200706.edition=ls.html).
2. Remarquez que le logo coComment en bas à droite devient orange. (Au lieu de bleu.)
3. Cliquez sur le dit logo, une fois, avec le bouton de gauche.
4. Lisez et extasiez-vous!

(Je n’en dit pas plus, il faut essayer. Oui, ça marche partout. Dingue.)

Similar Posts:

Intégrer coComment sur votre blog [en]

Vous savez probablement que je ne jure que par [coComment](http://cocomment.com “Visitez le site coComment, et créez un compte si ce n’est pas déjà fait!”), dans la genèse duquel j’ai eu la chance de jouer [un petit rôle](http://climbtothestars.org/archives/2006/02/04/cocomment-enfin-public/ “Lisez un petit bout de l’histoire de coComment.”).

**Ça sert à quoi?**

Ça sert principalement à choses pour l’instant:

1. collectionner ses commentaires faits sur différents blogs en un seul endroit, comme on peut le faire en les [bookmarquant avec del.icio.us](http://del.icio.us/steph/my_comments “Voir mes commentaires sauvagardés.”), mais de façon bien plus pratique;

2. voir facilement si quelqu’un d’autre a répondu à un de nos commentaires — mais attention, ceci ne marche pas très bien pour l’instant, car coComment est [seulement capable de suivre les commentaires de gens ayant un compte coComment](http://www.cocomment.com/teamblog/?p=40 “Voir les explications. Recherche de solution en cours.”).

**S’inscrire**

[Ouvrir un compte, c’est super facile](http://www.cocomment.com/register “Allez-y maintenant.”), il suffit de donner nom et e-mail et de choisir un nom d’utilisateur et un mot de passe.

On notera qu’il n’est pas nécessaire d’avoir un blog pour trouver une utilité à coComment. Il y a des personnes qui participent activement à la blogosphère à travers leurs commentaires, sans pour autant être blogueurs. CoComment est pour vous!

**Rendre coComment plus pratique**

Une fois le compte ouvert, coComment vous fournit un [bookmarklet](http://www.cocomment.com/tools/bookmarklet), une sorte de lien “favori” que vous pouvez faire glisser dans la barre d’outils de votre navigateur ou dans vos favoris. Ensuite, quand vous laissez un commentaire chez quelqu’un, vous cliquez sur le bookmarklet dans votre navigateur avant de publier le commentaire.

Ça, ça devient très vite barbant. On oublie de cliquer sur le bookmarklet. Du coup, notre commentaire n’apparaît pas sur notre [page de conversations coComment](http://www.cocomment.com/comments/steph “Voir ma page de conversations.”). Il paraît qu’on peut maintenant [cliquer sur le bookmarklet après avoir envoyé le formulaire](http://www.cocomment.com/teamblog/?p=43 “Ils le disent ici.”), mais personnellement je n’ai pas testé.

Les commentateurs peuvent faire quelque chose pour se simplifier la vie. Les auteurs de blogs peuvent faire quelque chose pour simplifier la vie de leurs commentateurs.

**Plus pratique pour moi qui laisse des commentaires**

Pour ça, il faut utiliser [Firefox](http://www.mozilla-europe.org/fr/ “C’est le moment de le télécharger et de l’installer si ce n’est pas encore fait.”). Deux solutions s’offrent à vous.

1. [Le script GreaseMonkey](http://userscripts.org/scripts/show/3165 “Page du script.”). Ce script vous évite de devoir cliquer sur le bookmarklet à chaque fois. Vous pouvez donc oublier coComment quand vous laissez vos commentaires, c’est tout automatisé. Sympa, non?

Script, GreaseMonkey, chinois? Pas peur, instructions pour les nuls. D’abord, installer l’extension GreaseMonkey (non, ça fait pas mal). Pour ça, on commence par s’assurer que l’on a Firefox 1.5 (voir lien ci-dessus), puis on va sur [le site de l’extension GreaseMonkey](http://greasemonkey.mozdev.org/ “C’est par ici.”). Une fois là -bas, on cliquera sur le lien qui s’appelle “Install GreaseMonkey” dans la deuxième moitié de la page. On dit oui à tout ce que nous demande Firefox (oui on veut installer l’extension, oui, oui, OK on ferme le navigateur et on le rouvre…)

Ensuite, [on clique sur ce lien-ci qui va installer le script](http://userscripts.org/scripts/source/3165.user.js “Lien direct d’installation, faut dire oui à tout.”) et on dit également oui à tout.

Voilà ! C’est fait 🙂

2. [L’extension Firefox pour coComment](http://the-enginerd.blogspot.com/2006/02/firefox-extension-for-cocomment.html “C’est par ici.”). Même chose que plus haut, on clique sur le lien, on clique ensuite sur “Download coComment! for Firefox”, et on dit oui, amen à tout ce que nous demande notre navigateur chéri. L’extension me paraît moins utile que le script GreaseMonkey, car elle ne fait qu’ajouter le bookmarklet coComment au menu contextuel qui apparaît lors d’un clic droit (ou long clic pour les personnes qui ont un Mac). Mais il paraît que c’est utile parfois lorsque les commentaires sont dans une fenêtre pop-up. Personnellement, j’ai vu que ça ne marchait pas tout le temps, mais j’essaie quand même.

**Note:** j’ai désactivé l’extension Firefox vu que je ne l’utilise pas. A vous de voir si elle vous sert.

**Plus pratique pour moi qui ai un blog**

Si vous avez un blog, vous pouvez faire en sorte que vos commentateurs, s’ils ont un compte coComment, n’aient pas besoin de cliquer sur le bookmarklet, même s’ils n’ont pas installé l’extension GreaseMonkey décrite ci-dessus. Cool, non? Pour cela, il faut rajouter du code javascript pas trop loin du formulaire de commentaires.

[Le code est fourni à la fin de ce billet](http://www.cocomment.com/teamblog/?p=37 “Code à la fin, explications au début.”) par Merlin. Comme j’utilise une version assez standard de WordPress, je n’ai eu personnellement qu’à copier-coller ce qui était donné dans le billet. Bon, faut encore voir si ça fonctionne 😉 Attention, donc, si vous avez un autre outil de blog, il faut peut-être adapter le code. Cet autre billet [explique plus précisément quel rôle joue chaque ligne](http://www.cocomment.com/teamblog/?p=21 “Décorticage du javascript en question.”) et vous aidera certainement à modifier le code si nécessaire.

**Attention!** Pour le moment, j’arrive pas à faire marcher ça. Plus de nouvelles dès que c’est réglé. Ça marche maintenant, mais il faut faire attention aux [guillemets malins pas si malins quand ils sont dans du code](http://climbtothestars.org/archives/2006/02/19/integrer-cocomment-sur-votre-blog/#comment-55276 “Lire les explications.”)…

**Oui mais… DotClear, autres plateformes de blog, etc…?**

Pas de panique. Premièrement, il faut savoir que les gars de coComment bossent d’arrache-pied pour [augmenter le nombre de plate-formes avec lesquelles ils sont compatibles](http://www.cocomment.com/supported “La liste, à ce jour.”). Si votre blog n’est pas compatible avec coComment, mais que vous pouvez modifier votre formulaire de commentaires, tout n’est pas perdu.

[Le dernier billet que j’ai mentionné](http://www.cocomment.com/teamblog/?p=21 “Oui, c’est un poil technique, mais pas impossible.”) explique comment faire. Il faut donc rajouter un certain nombre de lignes javascript dans le formulaire, et voilà ! Je suis certaine que DotClear fournit toutes les informations nécessaires mais avec d’autres noms que ceux auxquels s’attend coComment. Il suffirait donc qu’un(e) DotClearien(ne) prenne le taureau par les cornes et adapte le javascript aux variables de DotClear (la version publiée utilise les variables WordPress). Si vous faites ce travail, rendez-le public sur votre blog, et je lancerai un lien dans se direction! Qui s’y colle?

**Mise à jour:** Nicolas propose en commentaire [le code à intégrer à DotClear](http://climbtothestars.org/archives/2006/02/19/integrer-cocomment-sur-votre-blog/#comment-55665). Quelqu’un peut confirmer que ça marche?

Similar Posts:

Requirements for a Multilingual WordPress Plugin [en]

[fr] Quelques réflexions concernant un plugin multilingue pour WordPress.

My blog has been bilingual for a long time now. I’ve [hacked bilingualism into it](http://climbtothestars.org/archives/2004/07/11/multilingual-weblog/) and then [plugged it in](http://climbtothestars.org/archives/2005/01/23/basic-bilingual-plugin/). Other [plugins for multilingual bloggers](http://codex.wordpress.org/Plugins/Translation_and_Languages) have been written, and some unfortunately [got stuck somewhere in the development limbo](http://doocy.net/archives/2005/01/20/the-multilingual-acknowledgement/).

Defining specs is a hairy problem. They need to work for the person visiting the site (polyglot or monoglot). They need to work for the person (or people! translation often involves more than one person) writing the posts. They need to work for all the robots, search engines, and fancy browsers who deal with the site.

Here is what I would like a multiple language plugin to do (think “feature requirements”, suggestion, draft):

1. Recognize the browser language preference of the visitor and serve “page furniture” and navigation in the appropriate language. This can be overridden by a cookie-set preference when clicking on a “language link”.
– “WordPress” furniture can be provided by the normal localization files
– how do we deal with other furniture content in the theme (navigation, taglines, etc.)? should the plugin provide with guidelines for theme localization? do such guidelines already exist? extra information appreciated on this point
– “language links” shouldn’t be flags, but language names in their respective languages; can this list be generated automatically based on present localization files? otherwise, can it be set in an admin panel?
– upon “language change” (clicking on a language link), could the localization (action) be done in an [AHAH](http://microformats.org/wiki/rest/ahah)- or [AJAX](http://en.wikipedia.org/wiki/AJAX)-like way?
– inevitable hairy problem: tag and category localization
2. Manage “lazy multilingualism” in the spirit of the [Basic Bilingual plugin](http://climbtothestars.org/archives/2005/01/23/basic-bilingual-plugin/) and “true multilingualism” elegantly and on a per-post basis.
– allow for “other language abstracts”
– allow for actual other language version of the post
– given the “general user language” defined above, show posts in that language if a version for that language exists, with mention of other language versions or abstracts
– if that language doesn’t exist, show post in “main blog language” or “main post language” (worst case scenario: the wordpress install default) and show alongside other language abstracts/versions
– abstract in one language (would be “excerpt” in the “main” language) and existence of the post in that language are not mutually exclusive, both can coexist
– does it make more sense to have one WordPress post per language version, or a single post with alternate language content in post_meta? For lazy multilingualism, it makes more sense to have a single WP post with meta content, but fore “translation multilingualism”, it would make more sense to have separate posts with language relationships between them clearly defined in post_meta
3. Use good markup. See [what Kevin wrote sometime back](http://epeus.blogspot.com/2005_01_01_epeus_archive.html#110513233021128637). Make it nice for both polyglot and monoglot visitors. [Inspiration?](http://blogamundo.net/dev/2005/10/31/a-nice-language-switching-widget/)
– use <div lang="xx"> and also rel attributes
4. Provide a usable admin panel.
– when I’m writing the other version of a post, I need access to the initial version for translation or abstracting
– ideally, different language version should be editable on the same admin panel, even if they are (in the WordPress database) different posts
– languages in use in the blog should be defined in an options screen, and the plugin should use that information to adapt the writing and editing admin panels
– idea: radio button to choose post language; N other language excerpt/abstract fields with radio buttons next to them too; abstract radio buttons change dynamically when main post language is set; in addition to other language abstract fields, another field which can contain a post id/url (would have to see what the best solution is) to indicate “this is an equivalent post in another language” (equivalent can be anything from strict translation to similar content and ideas); this means that when WP displays the blog, it must make sure it’s not displaying a post in language B which has an equivalent in language A (language A being the visitor’s preferred language as defined above)
5. Manage URLs logically (whatever that means).
– if one post in two languages means two posts in WP, they will each have their own slug; it could be nice, though, to be able to switch from one to an other by just adding the two-letter language code on the end of any URL; a bit of mod_rewrite magic should do it
6. Integrate into the WordPress architecture in a way that will not break with each upgrade (use post-meta table to define language relationships between different posts, instead of modifying the posts table too much, for example.)
– one post translated into two other languages = 3 posts in the WP posts table
– excerpts and post relationships stored in post_meta
– language stored in post_meta

I have an idea for plugin development. Once the specs are drafted out correctly, how about a bunch of us pool a few $ each to make a donation to (or “pay”) the person who would develop it? Who would be willing to contribute to the pool? Who would be willing to develop such a plugin (and not abandon the project half-way) in these conditions?

These specs need to be refined. We should start from the markup/reader end and get that sorted out first. Then, think about the admin panel/writer end. Then worry about code architecture. How does that sound?

We’ve started a discussion over on [the microformats.org wiki](http://microformats.org/wiki/multilingual-brainstorming). Please join us!

Update: this post is going to suffer from ongoing editing as I refine and add ideas.

Similar Posts:

Software: FreeMind [en]

Trying out FreeMind, mind-mapping software that runs on OSX (and other operating systems).

[fr] Je suis en train d'utiliser FreeMind, un logiciel gratuit de "mind-mapping" (comme MindManager) qui tourne sous OSX. J'y ai mis ma liste de choses à faire, et c'est bien mieux que dans iCal.

The less I post, the less I post. One reason being that there would be a ton of things I could talk about, but I don’t want to discuss here. Another being that my hands hurt. But the most important one is that as I don’t write much these days, the things I actually do publish had better be overly important and overly interesting.

So, to hell with that. I’ll lower my interestingness expectations.

I’ve just been trying out FreeMind, a free mind-mapping application that runs under OSX, Windows, and Linux. Following Suw‘s advice, I’m using it to keep track of things I must do. I’m not certain it will replace my fun to-do list, but it sure beats iCal’s To Dos.

Similar Posts:

Reconnaissance vocale pour OSX [fr]

A la recherche d’une solution pour avoir de la reconnaissance vocale en français sur mon Mac.

[en] Because of the limitations imposed on the purchase of US products in France, there is no planned French version of iListen, the most viable speech recognition software for Mac.

**Mise à jour 09.2007:** Bonne nouvelle pour tous, [Dragon NaturallySpeaking tourne très bien sous Parallels avec OSX](http://climbtothestars.org/archives/2007/04/01/success-dragon-naturallyspeaking-in-parallels/). On peut donc dicter sur nos Macs!

J’aime mon Mac. Mon entourage a d’ailleurs remarqué que depuis ma conversion, je suis devenue une irrépressible ambassadrice Mac.

Quand je pense à ma vie avant OSX, je regrette une seule chose: mon Dragon.

Ces temps, j’ai de nouveau mal aux mains, donc je me dis de nouveau que je dois vraiment acheter un logiciel de reconnaissance vocale pour mon iBook. Puisque Dragon n’existe pas pour Mac, il y a deux solutions: ViaVoice et iListen. ViaVoice n’est plus en développement actif, donc le choix serait plutôt iListen, dont j’ai entendu beaucoup de bien, et qui a l’avantage de bien s’intégrer dans l’environnement OSX.

Seul hic? Pas de version française, et pas de projets (aux dernières nouvelles) d’en produire une, vu les limitations imposées aux institutions françaises concernant l’achat de produits non-français.

Solution, que me souffle mon ami Kevin: mettre un place une société française pour faire l’intermédiaire avec MacSpeech et vendre le produit en France.

Il y a des volontaires?

Autre, idée, si l’architecture du logiciel le permet: faire développer indépendamment le vocabulaire et la grammaire français. Il existe en tous cas une version allemande et une version italienne de iListen, donc, ce n’est pas un problème technique, mais bien politique.

Similar Posts:

Emergency SMTP Server for OS 10.3 [en]

PostfixEnabler is a small utility that allows you to use your OSX machine as an SMTP server to send e-mail when you cannot use your regular SMTP server.

[fr] PostfixEnabler est une petite application qui vous permet d'utiliser votre machine tournant sous comme serveur SMTP, pour envoyer des mails lorsque vous ne pouvez pas utiliser votre serveur SMTP habituel.

My ISP’s SMTP server is acting up these days, which means I can’t always send out mail. (Which, you’ll agree, can be frustrating.) Dave pointed me to a very easy solution to set up a local SMTP server on OSX (10.3 only with this tool, earlier versions require another similar tool). It can also be useful when you’re on the road.

  • Download PostfixEnabler and install it.
  • Launch it and click on “Enable Postfix”.
  • Send your mail.
  • Stop Postfix when you’re done.

Whenever possible, use an “official” SMTP server, as e-mail from private SMTP servers is often treated like SPAM.

Similar Posts:

Keeping The Flat Clean: Living Space As User Interface [en]

How I applied what I have understood about designing user interfaces to organising my flat so that it too is ‘usable’ and remains clean.

One of my ongoing post-study projects is reorganising my flat from top to bottom, hopefully throwing out half my stuff in the process. I have been thinking a bit about the way I store things.

First of all, I tend to try to minimise waste of space. I will organise things into cupboards and drawers so that they occupy the less space possible. Second, I tend to organise things with taxonomy rather than function in mind. I will try to store objects of the same type together, regardless of their respective frequency of use.

The result is a perpetually messy flat, with whole areas that I never use (places I do not go, cupboards I never open).

I have therefore been rethinking my whole living environment in terms of function and process. What do I use this thing for, and when? How do I deal with common tasks like washing up or doing my mail? And most important, how does clutter arise? An environment where each thing has a place is not sufficient to prevent clutter. If clutter arises, it is not due to “laziness”. It is because the storage system is not usable enough. It was not designed with the user in mind.

I have switched to considering my living space as a user interface rather than as a library of categorised items.

If I catch myself dumping something on the table instead of putting it away, I’ll try to identify what is preventing me from putting it where it belongs. I’ll try to bring this “where it belongs” closer to where I am naturally tempted to put it. (Instead of thinking “ooh I’m a bad girl, I’m not putting things away as I should,” which we all agree does not help in the least.)

Here are a couple of examples of what I have been doing.

First, I identified the main sources of clutter in my flat: dirty kitchen things, clothes, papers and books. Then I tried to analyse how these things ended up lying about my whole flat. I know that I can clean my flat spotless, and that within a couple of weeks it will be messy again. So obviously, there are things I do mechanically which create clutter. Something which breaks the natural “keeping clean” flow.

Let’s take the dirty dishes to start with. (Not the most glamorous example, but I’m sure there are many of you out there who can relate.) Why do I leave cups, glasses, or even plates lying around in various places? A first reason for this, obviously, is that I do not only eat in my kitchen. That’s a fact we will just have to live with. But why don’t I bring things back to the kitchen? Well, more often than not, the kitchen is in such a state that there wouldn’t really be any place to put them. The sink, of course, is already full of dirty dishes. We have here are perfect example of how disorganisation in one area leads to clutter elsewhere.

One factor which helps stuff pile up in my sink (despite my “fool-proof” method for taming dirty dishes) is that I usually have to make space on the drainer before I start washing up. (I’m one of these people who don’t dry dishes but leave them on the drainer to put them away “later”.) And putting the dishes away is a pain because my cupboard is so crammed with stuff that I have to empty half of it before being able to put my plates were they belong. That is where the bottleneck is. Or the limiting factor, if you prefer.

I realised that out of my four kitchen cupboards, there are only two that I regularly open. I proceeded to empty all the junk out of the others and get rid of the most of it (if I never open the cupboards, then I can’t really need what’s inside them, can I?) I then reorganised the things I use on a regular basis in all the available cupboards, focusing on “how easy will it be to put it back there?” rather than “could I use less space for this?”

One significant result concerns plates. (Don’t worry, we’ll soon be done with the kitchen things.) I have big plates and small plates, four of each. I used to keep the small plates piled up on the big ones, which meant that each time I wanted to put a big plate back in the cupboard, I had to lift up all the small plates first (see what I mean?) That didn’t help prevent things from accumulating on the drainer. Now I have the small plates on one shelf, and big ones on another. I use up more storage space, but it’s easier to put things away. I have rearranged all my kitchen cupboards along the same principle, and the kitchen is now much more usable.

This post is getting much longer than what I expected. However, I don’t want to leave you without letting you know what I have come up with for dealing with my incoming mail. I have been using a tray-based system for sorting paperwork for a long time, but it has shown its limitations regularly over the past years. The new system still uses trays, that groups papers according to what I have to do with them instead of what they are. So now, this is what my trays look like; I’ll see as I use it if it needs any modifications:

  • to do (bills to pay, things to investigate or have a closer look at)
  • to do, ASAP (anything urgent)
  • to file, daily business (bank papers, medical papers, salary slips)
  • to file, important (tax stuff and other important things)
  • to look at (optional) before throwing out (various newspapers, information leaflets)
  • to throw out (envelopes and anything else I don’t keep; the bin is often not close at hand)
  • to sort (anything unopened; sometimes I fetch my mail and don’t deal with it straight away

In conclusion, here is my line of conduct:

  1. pay attention to cupboards that are never opened or shelves that are never reached at
  2. keep an eye on what I do automatically and try to adapt the environment
  3. think “actions”, “process”, and “frequency” instead of “categories” and “families”
  4. accept my limitations

The last point is important: there will always be clean washing waiting to be ironed, because no matter how hard I try, I’ll never get around to ironing and putting it away as soon as it’s dry. I therefore need to take this into account and explicitly plan a space for my huge pile of Clothes Waiting To Be Ironed, even if in an ideal world, Clothes Waiting To Be Ironed should not be around.

Similar Posts: