After the scrolling wheel of my old Typhoon mouse went crazy (I think because of a loose contact) I bought a Logitech MX1000. A very nice mouse with superior surface detection which made a mouse pad unnecessary for me. If you’re in my position you have a mouse with tons of buttons and want to use them all. This is how I did it:
You’ll need the following programs:
- xbindkeys: for remaping button events
- xvkbd: used to send specific keyboard events
- xmacro: used to send specific mouse events
- kompose: a program for the “Application-Switch” button
- lmctl: for disabling cruise control Download and install those programs, Ubuntu users will find most of them in the repositories.
Follow the instructions of this wiki article, it worked like a charm for me. If you have done what stands there, logout of KDE / Gnome and restart X to see if it works.
Yesterday, the latest working draft of XHTML 2.0 was released. Oh my, what would I give to live in the future - like in 5-10 years from now. In a paradise for every web developer where XHTML 2.0 was the common standard and all browsers support it…
Ok, enough of that
day night dreaming. Here are the “Major Differences with XHTML 1” I’m most looking forward:
- Images in every element - no need for fancy image replacement!
- Any element can serve as a link. Very nice! That way you won’t have to use something like
<li href="...">...</li> will do it.
- Navigation lists
- Last but not least the
role attribute. That will be a good replacement for semantic classes such as
<p class="note"> at least if all browsers support CSS 2 selectors (
Update: Use Markdownify, it’s the successor to html2text.
I changed my html2text.php function and it now supports non markdownable elements better. Previously something like
<p class="foobar">...</p> would have resulted in
<p>...</p>. Now these elements (which could be ported to markdown) will be left in plain html.
Additionally I made some changes which should lead to an improved performance.
Get it while it’s hot: html2text.php 1.1 (.tar.gz ~ 120.9 KB)
Yes, there are some, which I’ll try to fix in the next days (note: to better point out the bugs I just write what happens if you convert html to markdown to html):
What else is left to say? Well, comments will follow soon. And I think I’ll move the 3co website to this server (I have to admit that Sourceforge’s web server are pretty slow and you have to configure a lot).
So - take a look at my two projects 3co and html2text and keep an eye on this site. More features are about to be revealed.