> If the usage of inherited class variables in Rails is significant,
> might it not be something to be raised with the ruby core team before
> they finalize the change? It's not clear to me that the change is
> actually a good one, although I'm not much of a direct user of class
> variables mysel
> What's the next step with this?
Sorry for the delay, I had a bit of a patch backlog. That's been applied now.
--
Cheers
Koz
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post
On 10/24/07, Julian Tarkhanov <[EMAIL PROTECTED]> wrote:
> > DEFAULTS: &DEFAULTS
> > created_on: <%= 3.weeks.ago.to_s(:db) %>
>
> /me smells structs & macros, but maybe that's that odd YAML smell
> getting over ;-)
Yeow! Serves me right for using the YAML anchor/merge syntax in those
examples
A patchified version of Rathole is available for your amusement:
http://dev.rubyonrails.org/ticket/9981
~ j.
On 10/22/07, John Barnette <[EMAIL PROTECTED]> wrote:
> All,
>
> I've recently extracted a plugin that significantly improves (well, I
> hope) fixtures. I'd originally written it as a
Hmm, perhaps you could be more clear? Refactoring in terms of being
able to read the code easily? Or do you mean that when using this
syntax that it would be harder to make changes to it? Additonally, I
think an observer should 'declare' what it is observing, rather than
defining callback methods
On Oct 24, 6:29 pm, zdennis <[EMAIL PROTECTED]> wrote:
> Ticket 9900 adds a declarative way to define observer callbacks which
> seems more in line with the Rails way of thinking.
>
>http://dev.rubyonrails.org/ticket/9900
>
> The patch is rather simple and the tests are great. Ping for core to
Ticket 9900 adds a declarative way to define observer callbacks which
seems more in line with the Rails way of thinking.
http://dev.rubyonrails.org/ticket/9900
The patch is rather simple and the tests are great. Ping for core to
give it a look,
Zach
--~--~-~--~~~---
Sorry I intended this to go to the rails-talk list but gmail outsmarted me.
On 10/24/07, Rick DeNatale <[EMAIL PROTECTED]> wrote:
> Prompted by some discussion on rails-talk last week, I worked up a
> patch to add an option to ActiveRecord::Base#find which allows
> associations to be :included f
Prompted by some discussion on rails-talk last week, I worked up a
patch to add an option to ActiveRecord::Base#find which allows
associations to be :included for purposes of the where clause, but
defers instantiating the included association objects.
The use case is where there are a large numb
Comments welcome.
http://dev.rubyonrails.org/ticket/9979
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send email to rubyonrails-core@googlegroups.com
To unsubs
Comments welcome.
http://dev.rubyonrails.org/ticket/9979
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send email to rubyonrails-core@googlegroups.com
To unsubs
Future Googlers, I was wrong : )
On Oct 24, 5:02 pm, "James H." <[EMAIL PROTECTED]> wrote:
> You bet I do! However... not today :P
>
> For future Googlers, until I can get a good work around what I'm doing
> is using the snazzy Chronic gem. This means I can use a simple text
> field and parse t
Sorry, we got together few times, but I'm in the middle of the San Diego
fires so we had to postpone our meetings. We are really close to a proposal,
just working on the details.
-Matt
--
http://railsontherun.com
On 10/24/07, Mislav Marohnić <[EMAIL PROTECTED]> wrote:
>
> O
On 10/5/07, Matt Aimonetti <[EMAIL PROTECTED]> wrote:
>
>
> FYI people a bunch of us got together today to discuss the proposed
> API.
>
> Globalize, Simple Localization and GlobaLite plugins were represented.
> We had a good discussion and tried to come to an agreement and a
> suggestion for the c
You bet I do! However... not today :P
For future Googlers, until I can get a good work around what I'm doing
is using the snazzy Chronic gem. This means I can use a simple text
field and parse the _before_type_cast version into a Date (or Time)
object.
James
On Oct 24, 4:38 pm, "Michael Kozia
> Are you
> suggesting that some script goes through all patches on Trac after each
> commit to Rails trunk and checks if they still apply cleanly? That would be
> one heck of a post-commit hook. The idea is not bad, however.
I know the SvK guys have talked about building something like this
into
> The problem appears to be that Rails doesn't know to put the date-
> select information into an Array.
That certainly looks like it. Have a look at trac and see if anyone
else has reported this, otherwise you'll need to open a new ticket
yourself. Do you feel like taking a crack at fixing it
On 23-okt-2007, at 7:45, Courtenay wrote:
> The syntax is great! But this defaults thing is difficult to remember
>
> DEFAULTS: &DEFAULTS
> created_on: <%= 3.weeks.ago.to_s(:db) %>
/me smells structs & macros, but maybe that's that odd YAML smell
getting over ;-)
--
Julian 'Julik' Tarkh
I think I've found a bug with Edge.
I'm trying out Ryan Bates' multi-object form technique shown in one of
his Rails-casts (railscasts.com/episodes/75). If you use a fields_for
similar to that shown (here: http://pastie.caboo.se/110480), you get a
Server Error 500:
--
Status: 500 Internal S
On 10/24/07, Rick DeNatale <[EMAIL PROTECTED]> wrote:
> Oops,
>
> It looks like the edge testing setup changed out from under me so that
> the patch won't apply to edge.
>
> I'll update the patch once I've figured it out.
I attached a new patch which fixes the test case which was broken
since a s
I should mention here are a few examples of its usage (besides the
README):
http://svn.practical.cc/plugins/acts_as_tokenized
http://svn.pluginaweek.org/trunk/plugins/active_record/attributes/encrypted_attributes
On Oct 24, 12:59 pm, Aaron Pfeifer <[EMAIL PROTECTED]> wrote:
> We released a plugi
We released a plugin/gem that provides support for this type of thing:
http://wiki.pluginaweek.org/Plugin_test_helper
We use it in many of our own plugins.
On Oct 24, 12:59 am, Josh Peek <[EMAIL PROTECTED]> wrote:
> On Oct 23, 11:49 pm, "Krishna Dole" <[EMAIL PROTECTED]> wrote:
>
> > Is this no
Oops,
It looks like the edge testing setup changed out from under me so that
the patch won't apply to edge.
I'll update the patch once I've figured it out.
On 10/24/07, Rick DeNatale <[EMAIL PROTECTED]> wrote:
> http://dev.rubyonrails.org/ticket/9971
>
> This one cost me a few hours trying to d
On 10/24/07, mikong <[EMAIL PROTECTED]> wrote:
>
>
> I just noticed I frequently encounter patches that need to be updated
> because of applied changes. Maybe this can be automated? Not
> automating the "updating of the patch" part, but the part where a
> comment is posted to the ticket so the subm
I just noticed I frequently encounter patches that need to be updated
because of applied changes. Maybe this can be automated? Not
automating the "updating of the patch" part, but the part where a
comment is posted to the ticket so the submitter is informed.
--~--~-~--~~~
On 24-Oct-07, at 7:24 AM, alancfrancis wrote:
> I just tried to use text_field_with_auto_complete on the beta gems and
> discovered it's been removed for 2.0 as per the deprecation warnings.
> There are some comments suggesting it'll be a plugin by the time 2.0
> ships, but I can't locate the plug
On 10/24/07, Michael Koziarski <[EMAIL PROTECTED]> wrote:
>
> > I don't think we have full coverage, so that's not going to work.
>
> We do, however, have > 0 coverage ;) If someone can set up a 1.9 test
> environment, I think that's a good step in the right direction.
>
> > Besides, the tests mi
http://dev.rubyonrails.org/ticket/9971
This one cost me a few hours trying to debug my test cases when I
really needed to be debugging ActiveRecord.
If you define a table with a key other than id, the db/schema.db will
NOT define any primary key for the table. ActiveRecord::SchemaDumper
has a m
Howdy,
I just tried to use text_field_with_auto_complete on the beta gems and
discovered it's been removed for 2.0 as per the deprecation warnings.
There are some comments suggesting it'll be a plugin by the time 2.0
ships, but I can't locate the plugin.
I was able to steal the code from the 1.2
Just some quick cleanup and documentation.
Remove obsolete ActiveSupport::JSON::Variable -
http://dev.rubyonrails.org/ticket/9969
Add documentation for Hash#to_json and Enumerable#to_json -
http://dev.rubyonrails.org/ticket/9970
Please review :) Thanks!
Cheers,
Chu Yeow
--~--~-~--~--
Hello
I am very sorry for this.I had mistakenly posted in this forum
Thanks
Jagan
On Oct 24, 2:31 pm, Manfred Stienstra <[EMAIL PROTECTED]> wrote:
> On Oct 24, 2007, at 11:08, Jagan wrote:
>
> > can any one give me a idea of how can i do this
>
> The Core list is meant for discussion of
On Oct 24, 2007, at 11:08, Jagan wrote:
> can any one give me a idea of how can i do this
The Core list is meant for discussion of development on the
framework, not for support questions. Please redirect your question
to RoR: Talk: http://groups.google.com/group/rubyonrails-talk.
Manfred
Jagan,
This mailing list is for the development of the framework itself. You
should resend your question to support/general mailing lists -
http://groups.google.com/group/rubyonrails-talk
On 10/24/07, Jagan <[EMAIL PROTECTED]> wrote:
>
> Hello All,
>
>
>
> I have a table for which i need to ta
Hello All,
I have a table for which i need to tag and i am applying
acts_as_taggable for that
I have a table called localities and I created a table called tags
and tags_localities ,Now my requirement is i need to create new tags
and i should be able to add sub tags to the new tags
So it
> I don't think we have full coverage, so that's not going to work.
We do, however, have > 0 coverage ;) If someone can set up a 1.9 test
environment, I think that's a good step in the right direction.
> Besides, the tests might have to re-written for 1.9 too.
I wouldn't anticipate any breakag
35 matches
Mail list logo
