Slashdot Mirror

There might be better ressources, but this one has a few stations on the list.

"People can make apps using XAML and a few lines of .NET code."

However you can use existing technology to do some XAML stuff in less code. Look at this example. The MSDN article says that the slider program in Win32 API took 250 LOC, Windows.Forms took 100, and XAML took 60. From the article: "And that, my friends, is what is commonly called progress." However, the same thing designed in QT Designer (which uses XML) took 11 lines of code, some of which were includes and only contained curly braces. Maybe for them it is progress, but for most developers this would be a step backwards (if they previously used QT).

Not really. Just setup DistCC for the Zaurus, and you can let a desktop or laptop do the compiling for you via WiFi. Heck, you could even dialup to your machine with a modem for Zaurus distcc, as most Zaurus programs are less than 200k.

..which really doesn't take that long when you've got 2-3 i686's linked together via distcc. OpenOffice is, of course, the gluntenous exception. Heck, there's even a distcc build for my Zaurus.

Giving him a user account would be insane. kpf is "Very simple, and doesn't expose any more of my system to tampering than needs to be exposed."

tkcMail does non-latin1 languages.

While theKompany's server is down, here's a (very old) screenshot at my own site.

Rik

But what would the second one look like in XHTML2.0?

I currently use a 'section' tag to divide up my XML, then use XSL to mark up those sections into XHTML, using the name and depth of each section to generate a table of contents.

An example: this XML is rendered to this XHTML.

The new tags make a lot of sense IMO. It seems the W3C have some understanding of how HTML is used in the real world.

I currently use a 'section' tag to divide up my XML, then use XSL to mark up those sections into XHTML, using the name and depth of each section to generate a table of contents.

An example: this XML is rendered to this XHTML.

The new tags make a lot of sense IMO. It seems the W3C have some understanding of how HTML is used in the real world.

Hey, it really happens:

<bfinn> THE QUACK IS GAME TO PLAY TO KILL OF PEOPLE TO GUN

ASUS (A7M266-D) and IWill (MPX2) also make dual Athlon motherboards, though I'm not sure how much they cost.

My ASUS was GBP 200.

BTW - You can run a dual Athlon setup with a ~430W power supply

I'm using a 340W.

My notes about life with the A7M266-D

I'm very happy with my dual athlon box. I need the CPU grunt to compile lots of C++ code all day (g++ is horribly slow, as is the Linux linker.)

Why didn't I buy Intel ? Simple. To get an equivalent level of performance, I'd have had to pay twice as much.

Rik

To enter characters that aren't on your keys, you probably want to use the 'compose' method. This is part of X, so it works for all apps. Once you start using it, you can forget about app-specific hacks.

First you need to decide which key(s) will be used for composing. I have <> keys, so I use them, but you may want to use something like AltGr if you have a typical PC keyboard.

To find the code generated by a key, run xev and then press the key. On my keyboard, pressing the right 'alt' key generates code 113.

Now you need to tell X to use this key as a compose key, using something like this:

After doing this, pressing the compose key and then a combination of other keys will generate the characters you're after. For example: Compose + e + " generates ë (lowercase e with an umlaut).

Now you may add the above xmodmap invocation to your ~/.xinitrc or ~/.xsession or both, to have the setting ready when you next log in.

I have tried to tabulate all the available compositions for iso-8859-1 (latin-1) on my website, here.

Rik