I swear I had fixed this. Will have another look.
On Fri, Jul 2, 2010 at 12:54 PM, Ernie Miller wrote:
> I think the article entitled "Named Scopes Are Dead" had some good
> insights along those lines.
>
> http://www.railway.at/2010/03/09/named-scopes-are-dead/
>
> In the Rails 3 app I've been wo
Hi Scott,
While we appreciate you releasing open source libraries, this group is
for discussing only Rails core related issues. So please refrain from
sending such emails in the future.
On Thu, Apr 29, 2010 at 11:57 PM, frogstarr78 wrote:
> Assuming that a large majority of developers here use g
I thought about doing that. But the current behaviour is for
consistency with with_scope :
>> User.send(:with_scope, :find => {:select => 'id'}) { User.first(:select =>
>> "name") }
User Load (0.3ms) SELECT name FROM `users` LIMIT 1
Maybe we can change the behaviour for 3.1 though.
On Wed,
I suppose you could override Relation#build_where
def build_where(*args)
if result = super
case args.first
when Hash
# Figure out table names from *args here and add them to
join_values or something
else
super
end
end
end
I'm
Thanks for the report Nick. It's back up now.
On Tue, Apr 20, 2010 at 12:51 AM, Nick Quaranto wrote:
> Not sure of the best person to bug, but we've got an error:
> http://rubyonrails.org/
> -Nick
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails:
Agree with what Koz said. This isn't needed very frequently and it's
easier to just use a before/after save callback if/when it's needed.
On Mon, Apr 19, 2010 at 5:34 AM, Diego Carrion wrote:
> Hi Michael,
> in my case, an user gets only updated when he puts more money in his account
> or when so
scribe from this group, send email to
>>> rubyonrails-core+unsubscr...@googlegroups.com.
>>> For more options, visit this group at
>>> http://groups.google.com/group/rubyonrails-core?hl=en.
>>>
>>>
>>>
>>
>
> --
> You received this
t;Ruby on Rails: Core" group.
> To post to this group, send email to rubyonrails-c...@googlegroups.com.
> To unsubscribe from this group, send email to
> rubyonrails-core+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/rubyonr
l pair of nonzero? and nonblank? because they map
> values (0, empty/blank string respectively) to nil that are typically
> equivalent to not being present at all. Other languages like Python
> found it convenient to have 0 and empty string treated as false for
> just this reason I think.
ved this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To post to this group, send email to rubyonrails-c...@googlegroups.com.
> To unsubscribe from this group, send email to
> rubyonrails-core+unsubscr...@googlegroups.com.
>
gt; sql << " #{merged_joins} "
> + when NilClass
> + else
> + raise "Illegal joins value: #{merged_joins.class.name}"
> end
> end
>
> --
>
> You received this message because you are subscribed
7;_my_apps_session',
> :secret => 'oh-so-secret'
> }
> end
>
> Cheers,
> Eloy
>
> >
>
--
Cheers!
- Pratik
http://m.onkey.org | http://twitter.com/lifo
--~--~-~--~~~---~--~~
You received this messa
less it's an Array. Converts the
> # object to an Array using #to_ary if it implements that.
> def self.wrap(object)
> case object
> when nil
> []
> when self
> object
> else
> if object.respond_to?(:to_ary)
> obje
7;
is the process of saving records to the db. It'd be good to get more
feedback from people who're actively using these callbacks.
On Tue, Aug 18, 2009 at 1:46 AM, Brennan Dunn wrote:
> Pratik,
> In my use case, I'm wanting to fire off an auditing method when a
> polymorphi
r_add) being
> invoked, I wasn't expecting instantiation to. Was this an intentional
> decision?
> If not, I'd be more than happy to supply a patch.
> Thanks,
> Brennan
> >
>
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-~--~~~---~--~~
rmation *is* important.
I understand the change you people are suggesting is desired in many
situations. However, it's very easy to add that and it does not belong
in scaffolding.
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-~--~~~---~--~~
You received this me
this to delete confirmation screens as well?
When you edit/create - you don't just press one button. You enter a
good amount of data too. That's not true when you DELETE the record in
99.99% of the cases.
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-~--~~~-
Yeah I agree with Paul that :unique is a bit misleading. Also, I'm not
sure if I've had a case using .first() where it'd matter if there were
more than one matching row. Could you mention your actual use cases ?
Thanks.
On Thu, Jul 30, 2009 at 6:22 PM, Joris wrote:
>
>
no longer accept a
> string? (or if they will, then a string value will be ignored to
> determine if preloading must occur or not)
>
Well, we'll definitely need a way to supply string joins, even if they're
gonna be ignored to dete
c case, you could just use :joins too - which uses INNER
JOIN.
As for your scope example, I think that's a different problem altogether.
Thanks!
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-~--~~~---~--~~
You received this message because you are subscribed t
a nicer way for people to do this (fred cheung
> > was playing with an array proxy to enable this kind of thing)
> > 2) We might want to make :strategy=>:preload an option to find.
> >
> > I've no idea if :strategy is a good name for the option, but I thi
Right. And Public API != "interfaces targetted at framework extension
programmers". That's plugin API.
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
and able (regarding skills and free time) to give it a shot, I say go
>> for it: Fork, refactor, push, and show us!
>>
>> IMHO there's never a better time to refactor than right *now*. Besides
>> yesterday of course..
>>
>> Best,
>> Niels
>>
>> P
; to
>
> /page/83/edit
>
> is it simply a routes change?
>
> thanks for any kind of reply, as long as it's nice. :)
>
> >
>
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-~--~~~---~--~~
You received this message because you are s
Probably when someone in the core team wants to push backwards
incompatible or not-so-stable changes.
On Mon, Mar 16, 2009 at 11:18 PM, Ken Collins wrote:
>
> Is the master branch still the home for 2.3? Will there be a branch made for
> origin/2-3-stable?
>
> - Ken
--
C
to a hash using Hash.from_xml
>
> * libxml-ruby was 25 faster than REXML
> * nokogiri was only 1.6 times faster
> * JRuby-REXML was 3 times faster than MRI 1.8.6
> * JRuby-JDOM was 10 times faster
>
>
> >
>
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-~--~-
ide actually gives this as an example of usage.
>>
>> Instead of fixing the guide, I thought it was a nice idea to have
>> multiple layout methods, so I wrote this patch - which also fixes the
>> kind-of bug of conditions being merged but layout names being
>> overwritten
l
>>
>> On Mar 10, 12:00 pm, Chris Cruft wrote:
>>
>> > Not a patch, but last I checked assert_select_email didn't work -
>> > undefined method in ActionMailer::TestCase subclasses.
>>
>> > On Mar 9, 8:03 am, Pratik wrote:
>>
>> &
es at this point as they can wait. But if there are any
critical bug fixes or anything that should block the release, do post
it in the replies.
Thanks for all the contributions. 2.3 is looking really solid !
--
Cheers!
- Pratik
http://m.onke
oring like these makes almost all the relevant patches in LH
stale and screws up the history. I just don't think the patch in
question here is worth that.
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-~--~~~---~--~~
You received this message because you are subscribed
On Sat, Mar 7, 2009 at 4:40 PM, Eloy Duran wrote:
> So maybe a patch to add the after_commit API, as used in the article,
> would be a good idea.
Or if possible, just use observers.
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-~--~~~---~--~~
You receive
t; works,
> :having => ['sum(credit_limit) > ?', 50]
> doesn't. It should do the same as :conditions...
>
> Easy patch:
> http://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/2158-having-conditions-need-sa
de.
> http://is.gd/a8dn
>
> :)
> >
>
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, sen
r.
>
> If you like the idea and want to send feedback, please CC me. I'm not
> subscribed to the list.
>
> Regards,
> Andreas
> --
> OTTO Software Partner GmbH, Freiberger Str. 35, 01067 Dresden, Germany
> Andreas Gungl (e-mail: [EMAIL PROTECTED])
> Tel. +49-351-49723-
So if you want to help out, you could drop by the
channel or shoot me an email.
Thanks!
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To
by wider introduction of
> unit testing ?
>
Sorry I don't follow you ?
> --
> Aliaksey Kandratsenka <[EMAIL PROTECTED]>
>
>
> >
>
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-~--~~~---~--~~
You received this message bec
xy_respond_to?
>>
>> def proxy_respond_to?(method, include_priv = false)
>> super || @reflection.klass.respond_to?(method, include_priv)
>> end
>>
>> How could I test this to submit a patch?
>>
>> PS: Even this is kinda curious because it throws the Ex
of the ideas here, and I've been annoyed by this issue
>> quite a few times. Did a new ticket get created, or was a consensus
>> about an approach reached?
>
> No consensus :-/
>
> I think the resolution was "we don't want yet another migration helper" (?).
&
`require`, then it instantiates a new object on each call.
> After removing the require and memoizing the object, I've upped the
> performance of our application by 5 req/s.
> Is there a reason for the current implementation?
> >
>
--
Cheers!
- Pratik
http://m.onkey.org
rrent
> version is dangerous (not rolling back).
>
> --Matt
>
> >
>
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to
Cody : Patch is missing documentation.
Fred : Let's handle that :select issue post 2.2
Thanks.
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: C
me-for-select_tag-when-using-multiple-true#ticket-1146-1
>
> Thanks
>
> On Mon, Oct 6, 2008 at 5:32 PM, madlep <[EMAIL PROTECTED]> wrote:
>>
>> Hi Pratik
>>
>> Could we get this one in
>> http://rails.lighthouseapp.com/projects/8994/tickets/1085-asset_tag_help
01-enable-use-of-select-with-include.patch
>>> (which personally I mostly want because I've been working on
>>> making :include of hmt a bit leaner and need that patch to cover all
>>> cases)
>>
>> Applying this makes it possible to fix the #1110 issue for HABTM
On Mon, Oct 6, 2008 at 6:58 PM, Manfred Stienstra <[EMAIL PROTECTED]> wrote:
> It would be awesome if you could take a look at: #1179 [1].
Pushed.
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-~--~~~---~--~~
You received this message because you are s
k any features should make it
in, please let your voices be heard. Same goes for any critical bug
fixes. If you have any pending patches that you want in 2.2, speak
now.
Thanks.
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-~--~~~---~--~~
You received this me
/jq4r.blogspot.com/
> which one is better?
> >
>
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send em
want any half baked changes to be in stable
release. But I'd be happy to apply the patch again, and work incremently
after we have a 2.2 branch.
On Wed, Sep 10, 2008 at 8:36 PM, Zack Chandler <[EMAIL PROTECTED]>wrote:
>
> I noticed that Pratik just reverted the ":accessible opt
ll
someone, who has time, cares enough to submit a patch.
> It comes down to "IMO removing valid issues just because they involve docs is
> a bad idea". Moving on..
Closing the ticket doesn't remove them. They'll still show up in search results.
--
Cheers!
- Pratik
htt
n somewhere.. For those that find issues but don't have
> the resources to submit a patch at the time..
>
> Cheers,
>
> Tim.
> >
>
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-~--~~~---~--~~
You received this message because you ar
2008 at 1:44 AM, Michael Koziarski
>> <[EMAIL PROTECTED]> wrote:
>>>
>>>> Hey Pratik,
>>>>
>>>> Could I ask why?
>>>
>>> We've gone back and forth so much on the file names for migrations I
>>> think people are
Has anyone any strong opinions against this ? I'm very interested in
hearing more thoughts on this and/or if you have any suggestions to
improvise David's approaches.
Thanks,
Pratik
On Jul 14, 6:38 pm, David Dollar <[EMAIL PROTECTED]> wrote:
> Recently the following patch
&g
gt; --
>
> Nik Wakelin
> +64 27 424 5433
>
> * Blog: http://codetocustomer.com/blog
> * WWR: http://workingwithrails.com/person/7401-nicholas-wakelin
> * Company: http://codetocustomer.com
>
> >
>
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-~--~~-
nd make it simpler
to write such plugins. Patches welcome :)
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send email t
ers, that flexibility is
> needed.
> Otherwise I would need to hack any new template installed.
>
> On Jun 2, 1:50 pm, Pratik <[EMAIL PROTECTED]> wrote:
>> I am curious to know why you need to change the value of
>> ActionView::Base.erb_variable ? I'm mo
Erb.new().
>
> I also added the line below in fragment cache tests setup to assure
> that they are working with any variable set:
>
> ActionView::Base.erb_variable = '_buf'
>
> Patch here:
> http://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/
>
> This should definitely go into 2.1 and be backported to 2.0.
>
> I'm not sure I should post the exact problem here. Could somebody from
> the core team contact me?
>
> Jonathan
>
> --
> Jonathan Weiss
> http://blog.innerewut.de
> http:/
d please test it and make sure it works for them that
>>> would be great.
>>>
>> Those tests fail on 4.1 (in a different way. sigh) before & after your
>> patch. I'll have a look at what mysql have changed
>>
>> Fred
>>> http://rails.li
rb:67:in `run']:
> name column should be DEFAULT "".
> <""> expected but was
> .
>
> It appears MySQL has changed how its defaults work, but before I try
> to make a patch, can anyone confirm this problem on their system? Or
> is it something wr
; >
>>
>
>
>
> --
> http://jeremymcanally.com/
> http://entp.com
>
> Read my books:
> Ruby in Practice (http://manning.com/mcanally/)
> My free Ruby e-book (http://humblelittlerubybook.com/)
>
> Or, my blogs:
> http://mrneighborly.com
> http://rubyinpr
submit a
ticket at Lighthouse with "backport-2.0-stable" ( and upload the patch
as well ) and assign it to me.
In an ideal world, backported changes should mainly be tiny bugfixes.
So please keep that in mind :)
--
Cheers!
- Pratik
http://m
Hi all !
I finally managed to sync docrails branch with mainstream rails branch
and in the process, I changed the repository location as well.
New branch is at : http://github.com/lifo/docrails/tree/master
--
Cheers!
- Pratik
http://m.onkey.org
"rails" account, referencing the Trac ticket. Does the "rails"
> account's inbox get checked? Should I be sending pull requests to
> others?
>
> It would probably be a good idea to get the wiki going so we can start
> enjoying
(We need to drop the one in the
> mongrel handler). I suggest working on this stuff in a different
> branch (aka my thread_safe branch :) until we've got it done.
>
Agree.
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-~--~~~---~--~~
You received
;t know how to find "html/document".
>
> On a related note: both ActionController and ActionView depend on
> ActiveSupport, but only action_controller requires active_support, and
> action_view doesn't.
>
> I would gla
Session, but that
> could be changed without too much trouble.
>
> We only really use CGI as a standard way of getting an environment and
> input stream for the request and a an output stream to send the
> response. There's nothing particularly magic or
be wrapped up into a 2.1 release?
> Cheers
> Chris
>
> --
>
> http://pushrod.wordpress.com -- old dogs, new tricks
> http://autopendium.com -- a place your old car can call home
>
>
> >
>
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-~--
:
> On Jan 26, 2008 1:12 PM, Pratik <[EMAIL PROTECTED]> wrote:
>
> >
> > On Jan 26, 2008 12:07 PM, Jean-François Trân <[EMAIL PROTECTED]>
> wrote:
> > > - Yes it's useful
> >
> > Except, someone needs to kick CC.rb. It is showing com
On Jan 26, 2008 12:07 PM, Jean-François Trân <[EMAIL PROTECTED]> wrote:
> - Yes it's useful
Except, someone needs to kick CC.rb. It is showing completely irrelevant errors.
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-~--~~~---~--~~
You receive
Sevn,
I'm not really satisfied with this use case. From plugins, you're much
more likely to monkeypatch ActionController::Base and much more less
likely to monkeypacth ApplicationController. In fact, if plugin is
monkeypatching ActionController::Base, it's a lot easier to override
it in Applicati
>
> "monkeypatch" in quotes as this is a recommended (and successfull)
> practice for quite some apps out there.
>
> So, yes, there's a real benefit.
Could you explain on that part ?
Btw, I like the idea of renaming it to Application instead of
ApplicationContro
A little correction. I'm the "-1" guy. "+" was a typo :)
On Jan 15, 2008 5:48 PM, Pratik <[EMAIL PROTECTED]> wrote:
> On Jan 15, 2008 5:45 PM, Gabe da Silveira <[EMAIL PROTECTED]> wrote:
> > Maybe Rails has matured to
> > the point where th
of this change. application.rb used to
be called abstract_controller.rb - so we've already been on that road
before.
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ru
ame => "blah", :status_id =>
> Status.find_by_name("active"))
>
> or is it
>
> p = Project.new(:name => "blah", :status =>
> Status.find_by_name("active").id)
>
> or is it
>
> p = Project.new(:name => "blah",
sue?
>
>
> Thanks!
>
> --
> Best regards,
> Yuri Leikind
> >
>
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails
the people
> problems that we see in the Rails community?
>
> - Rob
> http://robsanheim.com
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Cor
hope that's okee.
>
> Please +1 or comment it.
>
> Thanks,
> Remco
> >
>
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
e, many people found some defect in their apps when the
current behavior was introduced.
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
g/ticket/10437
>
> I think alot of the other template compile logic that is in
> ActiveView::Base private methods could be move over to the
> TemplateHandlers as well.
> >
>
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-~--~~~---~--~~
You rec
hat'd be a design choice. You can always use post.taggings.new
or post.taggings.build
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
T
generator to
> > generate a new key - rake secret:generate:key
>
> What are the use cases for generating a new key? (not being
> contentious, just can't think of any off hand)
>
> >
>
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-~--~~~-
te the bluster patches never
> arrived.
>
I had always considered that to be a feature, rather than a defect in
design, which reminds developer not store any sensitive/secret data in
session.
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-~--~~~---~--~~
You rec
t.
>
> --
> http://www.5valleys.com/
> http://www.workingwithrails.com/person/8078
>
>
> >
>
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups &quo
ML
> syntax doesn't. I think readability is more important.
>
>
> >
>
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To p
t 8054 (they assume :join => :stuff should behave
> like :include rather than like :join).
>
> I have no idea what I'll do if it turns into an angry-dance-off
> between the "Includys" and the "Joinys".
>
> Thanks for taking the time to look at this.
> T
ible, or am I missing
> something that makes this fundamentally impossible?
> 3. If it is possible, is it a worthwhile feature that other's would find
> useful, or is it a bad idea or not worth the changes required to Rails
> that w
person
end
Data : 1 Person and 1000 items belonging to that person.
Performance Script : http://pastie.caboo.se/111774
Before the patch : http://m.onkey.org/before.html
After the patch : http://m.onkey.org/after.html
Please test the patch if you can and also post your comments/suggestions.
--
>
> > We already have the stale tickets report, the odds of the patches on
> > that list applying are pretty slim.
> >
> > http://dev.rubyonrails.org/report/69
> >
> > If you feel like closing some old patches / reports, that's where to find
> >
are dispatcher
callbacks and rescue_from, on top of my head.
Having said that, I don't see any harm in #9900 if it's a simple
patch. Always good to have options :)
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-~--~~~---~--~~
You received this message because
gt;
> So its basically applying Tagging on tags agian
>
>
> can any one give me a idea of how can i do this
>
>
>
> Thanks
> Jagan
>
>
> >
>
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-~--~~~---~--~~
You received this mes
mbined into one leading to just 1
> HTTP request for the cached js file. In development mode, they're
> separately referenced to allow any changes to be instantly reflected.
>
> JSMin and similar approaches are imo not worth it in a world of gzip
> compression.
>
>
&
ow, unless someone
> beats me to it.
>
> Bye !
> --
> François Beausoleil
> http://blog.teksol.info/
> http://piston.rubyforge.org/
>
> >
>
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-~--~~~---~--~~
You received this message because you
r should appear in the partial.
>
> Ideally f.partial 'form' would give you something sensible, but I'm
> not sure how you would pick such a default
>
> f.partial 'form', :name => 'f' would work, but then it's almost as
> awkward as :loca
nclude and when :preload.
Fred : It would be interesting if you can compare results of :preload
with :include after applying Gabe's patch - http://darwinweb.net/ Just
a thought.
-Pratik
On 9/24/07, Frederick Cheung <[EMAIL PROTECTED]> wrote:
>
> So eager loading via :include is f
> Sorry for being harsh, but I'lll try to explain what I meant. I tried
> to keep my head down but it just has to be said.
> Callbacks should stay if you ask me. It's also not something I
> consider easily pluginizable (this is deep, nasty backend stuff).
Or instead, you could have spent some tim
as plugins.
>
> > - spacer_templates
>
> Yeah, I don't find them helpful either.
Same here. If they're pluginized, it'll be easier to improve them for
the rare bunch of people who actually use them.
>
>
> >
>
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-
orry for the novel. Executive summary: These aren't new problems. Let's
> learn from at old solutions.
Exactly. That's why plugins as gems approach is better, as you can
have versioning of your plugins and any other plugin can easily say "I
need version X of plugingem Foo"
to the days where we all had to roll our own
> linked lists?
>
> --
> Jay Levitt|
> Boston, MA| My character doesn't like it when they
> Faster: jay at jay dot fm | cry or shout or hit.
> http://www.jay.fm | - Kristoffer
>
"It'd be nice to know how many people actually use'em."
On 9/19/07, Jay Levitt <[EMAIL PROTECTED]> wrote:
>
> On Wed, 19 Sep 2007 14:25:32 +0100, Pratik wrote:
>
> > I feel the following should go to plugins as well :
> >
> > - components ( r
uplication the functionality I guess.
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-~--~~~---~--~~
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@g
--
Cheers!
- Pratik
http://m.onkey.org
--~--~-~--~~~---~--~~
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 unsubscribe f
1 - 100 of 175 matches
Mail list logo
