Frodo as a Hacker
Just because I am a shameless nerd, here is, in all it's geekitude, my 2002 essay about hacking and Lord Of The Rings, rescued from its deserved obscurity for a few minutes, with some extra footnotes...
Just because I am a shameless nerd, here is, in all it's geekitude, my 2002 essay about hacking and Lord Of The Rings, rescued from its deserved obscurity for a few minutes, with some extra footnotes...
Bilingual entry here:
Yo nací en Santa Fe. Me gusta Python. Hay un evento de Python en Santa Fe.
Pienso asistir solamente como espectador, quedarme callado y escuchar cosas interesantes que digan los demas.
Sin embargo, si quieren experimentar un lugar donde se pueden comer 30 platos de pescado por 20 pesos (y te podes comer los 30, aunque yo conozco solamente una persona con la suficiente fortaleza estomacal), mas toda la cerveza que puedas tomar... bueno, nos vemos en Santa Fe el 3 de junio.
Mas informacion aca
I come from Santa Fe. I like Python. There is a Python event on Santa Fe.
I intend to attend in a strictly spectator fashion. I will listen to other guys telling interesting stuff, and keep quiet.
However, if you want to experience a place where you can eat 30 different fish dishes for about 7 dollars (and I mean you can eat all 30, although I know only one person of such superhuman fortitude), plus all the beer you can drink... well, I will be in Santa Fe on June 3rd.
More information here
I wrote Linux/Unix applications for ten years before I wrote my first man page.
I used all the excuses:
My app has interactive help
My app is for private use
Someone will write it eventually
But of course there are only two reasons not to write man pages.
You think the man pages are obsolete.
This is what the FSF thinks. So, they give you info pages. And they put, at the bottom of each manpage some warning about how that may look like the docs, but the real docs are the info pages.
Then they don't provide a decent info reader outside of emacs. But hey, who cares. On KDE, just use a info: URL.
You hate writing man pages.
Which is perfectly understandable, since this is how a man page looks like (and yes, I know it's specially ugly example):
.de }1 .ds ]X \&\\*(]B\\ .nr )E 0 .if !"\\$1"" .nr )I \\$1n .}f .ll \\n(LLu .in \\n()Ru+\\n(INu+\\n()Iu .ti \\n(INu .ie !\\n()Iu+\\n()Ru-\w^G\\*(]X^Gu-3p \{\\*(]X .br\} .el \\*(]X\h^G|\\n()Iu+\\n()Ru^G\c .}f
And it is even possible that for some man pages you need to write such a thing.
But for the average program? Just take something like txt2man and be happy.
I wrote man pages for each of my qmail-spp plugins in a few minutes. Although they probably are lacking in their man-pageness in matters of style, they are ok.
And they are not hard to write at all (full):
NAME authchecks DESCRIPTION This plugin is meant to be used on the AUTH command and does two things: 1. Logs the user (see LOGGING) 2. If the user is authenticated, it sets QMAILQUEUE "/var/qmail/bin/simscan-nospam", which is probably not what you want, but is what I use right now ;-)
And there is no reason why your program, be it KDE-based or not, should not have such a thing.
Wrote a whole queuing suite for efax. It kinda works, but not really, because it's not tested at all.
Rewrote the web app to work with said suite instead of mgetty+sendfax
Added status and sent pages
Implemented I18N for the web app
Next step: spending some actual cents sending and receiving faxes from my home phone line to the guy across the street.
What will happen: I need to do lots of other things, so I will shelve it for a week or so.
I decided to redo most of it, because I think I figured out a better way.
Use efax instead of mgetty+sendfax
After all, efax works with my modem and sendfax doesn't ;-)
Write a generic spooling thingamajig for efax (this is easy)
Rewrite printfax.pl in a simpler way (done)
Simplify the windows side.
Forget about a Qt app. All that's needed is a proggie that listens on a port, accepts connections. The connection gives it a URL. It launches the default browser with that URL.
If anyone reading this can write that program, I would really like it. Use VB, use .NET, use Java, I don't care.
Use the web app as the only interface.
What's missing yet:
Writing the queuing program (should use same format as mgetty+sendfax's)
The windows "client"
Minor tweaks to the web app ( basically a form for the sending data)
And that's it.
Other than the windows thing, it's about a day's work.