The comments section of ShadedBorder just exploded - and often questions got asked multiple times, even when there was already an answer.

A comments sections simply isn't suited for that - So here it is: The ShadedBorder Forum! Feel free to ask any question - again ;-)

With Rails 2.1 cache_erb_fragment has been replaced by write_fragment. This breaks a plugin I really enjoy to use: timed_fragment_cache by Richard Livsey.

It basically allows you to specify an expiry for the fragments you cache, e.g. inside memcache, by adding a "meta" fragment for the fragment you store containing the expiry time.

Some usage examples - pretty self-explaining:

In your view:

<%- cache 'my_key', 1.hour.from_now do -%>
	...
<%- end -%>

With extensive queries - your view ...:

<%- cache 'some_posts' -%>

Version 1.90.0 of GetText for Ruby has quite some memory leaks in its Rails support files. In my case, the memory Mongrel used increased by 1 MB with each request it served... Quite amazing that you don't really find someone else having the problem... Well there's at least a bug report on rubyforge...

Monkey-patching gettext.rb with the following code made things quite more relaxed:

  def bound_target(klass = self) # :nodoc:
    ret = nil

Ryan gave the idea and some code for a new ShadedBorder feature. Fat semi-transparent borders:

And thanks alot NewTrax for fixing the hover issues on IE6. It needs a bit more CSS to get going, but will solve any issues. Check out the CSS included in test.html on how to use it.

Ah, right: it's version 0.6 which has all these features. :-)

Yeah well, it was raining... And I'll be on holiday for quite some days from Tuesday on - without any computer. So this weekend was kind of the perfect time to hack a little bit on my neat little fun project ShadedBorder.

The result: after version 0.3 yesterday, today comes version 0.4. ;-) The new features:

• Graceful Degradation: If JavaScript is disabled, your page will look almost as good as if ShadedBorder could do its job.