I have seen the ideas of GSoC for rails and they are quite amazing,
lot of infrastructure work. But I am personally more interested in
working on other kind of idea for GSoC. Something that is maybe of
more direct application.
I was thinking on creating a plugin, web based games framework. A
plug
For this years Google Summer of Code, I want to implement a set of
Dtrace [1] probes in Rack [2]. The idea is to create a profiling tool
that easily works across a number of Ruby web-frameworks and web-
servers and provide insight into a web-app's performance.
Node monitoring and management are wi
On Sun, Mar 22, 2009 at 7:56 AM, tekwiz wrote:
> In the docs for ActionView::Helpers::FormHelper#check_box, when
> discussing why the method adds a hidden input tag _after_ the checkbox
> tag, it says
>
> "...Rails parameters extraction always gets the first occurrence of
> any given key..."
>
> Nothing new there though, it's caching 101, but I'm wondering if it
> makes sense to accommodate for this in the ActionController helpers
> (fresh?/stale?/fresh_when, by either setting another etag/modified if
> the flash hash is non-empty or always including the flash hash's
> checksum as part
The only updates I'm getting nowadays from Trac are spam comments, and
they're getting in more often by time.
Is it time to lock Rails Trac in read-only mode?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on R
The flash has no other purpose but the display of messages in the
view, right? The other session stuff we can't assume anything about,
but the flash?
On Sun, Mar 22, 2009 at 12:14 PM, DHH wrote:
>
>> Nothing new there though, it's caching 101, but I'm wondering if it
>> makes sense to accommodat
On Sun, Mar 22, 2009 at 10:00 AM, Mislav Marohnić
wrote:
> The only updates I'm getting nowadays from Trac are spam comments, and
> they're getting in more often by time.
> Is it time to lock Rails Trac in read-only mode?
Agreed. Comments are off now.
jeremy
--~--~-~--~~---
I wondered why routing does not pass the current route segment key to
to_param if to_param accepts a parameter.
This would allow to have a route like
map.article "articles/:permalink"
and then pass the named url generation helper an article like so:
article_path(article)
# => "artic
