Note, that it’s in no way complete, nor usable for anything other than toy examples (due to very little code, it’s probably stable, but especially with the Html-generation stuff, there might be problems).

You can download the sources directly from viewcvs here: www.ntecs.de/viewcvs/viewcvs/Wee/

There are no dependencies. To get started change into the examples directory and run example.rb, then point your browser to localhost:2000/app/ and have fun, or play with it online here:

ntecs.de/wee/counter

You can find some documentation on my blog. www.ntecs.de/blog/?cat=web

Any comments, bug fixes etc. very welcome!

Many thanks goes to Avi Bryant, who guided me into the right direction by answering a lot of question. Thanks!

I really wonder what impact this might have on the US-elections. Videomirror

Microsoft hates the fact that email is in plaintext. My Outlook Express client is buggy when it comes to handling the simplest of all tasks: receiving and responding to a text email. I’ve fiddled with all the internal settings, trying to get it to convert HTML mail to text, responding in text, and including all these simple plaintext protocols like adding ">" to quoted parts of an email I’m responding to. But my Outlook still insists on having things pop-up in tiny, colored fonts that are impossible to read, and then not tagging quoted text. In this environment, emails quickly bloat and become incoherent.

I found that I needed to know more about Ruby’s garbage collector in order to write robust extensions. This page is an attempt to fill this gap. It assumes the reader has some knowledge of Ruby’s C API, for example they have read the introduction in Programming ruby.

It’s a test-balloon. Maybe they will sell it as online pdfs in the future.

  class Float
    def truncate(sd=2)
      scale=(10**sd).to_f
      (self * scale).to_i / scale
    end
  end
  a=0.255
  a.truncate(2) #-> 0.25

Very nice picture. Belgium has the lightest sky, as they have lights on their highways. Germany is only on Nr. 4.

easyHotel

They copied the idea from Japan.

 I do this regularly, though most of the work so far has tended to be much
 more centric on web based applications.

 >> 1. A database
 >>     Java world: Oracle, MySQL or another relational DB of your choice

 MySQL

 >> 2. Some way to persist domain objects and manage transactions
 >>     Java world: entity EJBs, JDO, hand-coded DAOs, O/R <censored>
 >> mappers, etc

 Kansas has been maturing wonderfully for my purposes for this.

 >> 3. An RPC (remote procedure call) mechanism for communication between
 >> the front-end and the back-end (assuming that the front-end is a
 >> thick GUI).         Java world: session EJBs, servlets

 drb.  Works great.

 >> 4. A thick GUI
 >>     Java world: Swing

 TK, Qt, Fox

 >> 5. A Web GUI
 >>     Java world: JSP, XSLT, XMLC and all the other stuff

 I've use Iowa very successfully for this every day for a couple of years.

 >> 6. An asynchronous communications infrastructure
 >>     Java world: message-driven EJBs

 I am using Drb/Rinda/Tupleserver pretty effectively for this.  No problems
 with it at all so far.

 Kirk