BTW, is there any way to get the docs for 3.0.0.beta3?
El Martes, 25 de Mayo de 2010 17:35:31 Xavier Noria escribió:
> On Tue, May 25, 2010 at 4:01 PM, Michael Breen wrote:
> > I wasn't exactly sure where this should go but I figured this would be a
> > good place start.
>
> Thanks for the heads
http://api.rails.info
On 27 May 2010 18:43, Antonio Tapiador del Dujo wrote:
> BTW, is there any way to get the docs for 3.0.0.beta3?
>
> El Martes, 25 de Mayo de 2010 17:35:31 Xavier Noria escribió:
> > On Tue, May 25, 2010 at 4:01 PM, Michael Breen
> wrote:
> > > I wasn't exactly sure where th
Edge docs are periodically generated from docrails. The API is here
http://edgeapi.rubyonrails.org
and guides here:
http://edgeguides.rubyonrails.org
The main source of API docs is rails/master, docrails is mainly for
patching. So, there's always a little mismatch between what's in
rail
On Mon, May 24, 2010 at 5:54 PM, Daniel Schierbeck
wrote:
> 1. It is my feeling that the vast majority of the Rails community use
> jQuery exclusively.
This report from RailsLab says jRails is used by about 16% of RPM users:
http://railslab.newrelic.com/2010/05/25/state-of-the-stack-a-ruby-on-
Projects using jQuery dont necessarily use jRails so I dont think that
16% is a real indicator of the usage of jQuery in Rails projects.
At least to me it seems like the problem of having Prototype as
default affects mostly to new people. Advanced users will just install
jRails and use jQue
At every talk I give at a conference, I ask whether people use jQuery
in their Rails apps. In every case, close to 100% of the room raises
their hands. jRails is a replacement for the Rails helpers only; I
personally know a huge number of people who use jQuery with jRails.
In short jRails usage !=
On Thu, May 27, 2010 at 4:58 PM, Albert Llop wrote:
> Projects using jQuery dont necessarily use jRails so I dont think that 16%
> is a real indicator of the usage of jQuery in Rails projects.
As I said, I don't expect that to be a significant percent.
> At least to me it seems like the problem
On 27.5.2010, at 18.11, Yehuda Katz wrote:
> At every talk I give at a conference, I ask whether people use jQuery
> in their Rails apps. In every case, close to 100% of the room raises
> their hands.
In all fairness, I think that's a bit misleading question. I raised my hand
when you asked it i
The idea that 16% of Rails users use jQuery is divorced from reality.
I can devise some experiments to prove that, but I have seen no
evidence in my travels of a huge amount of people using anything else.
I freely agree that people use Protoype, MooTools and Dojo. The number
of people who do so, in
On Thu, May 27, 2010 at 5:32 PM, Yehuda Katz wrote:
> The idea that 16% of Rails users use jQuery is divorced from reality.
But you are talking perceptions, and the sample talks numbers.
Of course 16% has to be taken with some margins, but you can't deny it
makes difficult to claim that the vas
On 27-May-10, at 11:32 AM, Yehuda Katz wrote:
The idea that 16% of Rails users use jQuery is divorced from reality.
I can devise some experiments to prove that, but I have seen no
evidence in my travels of a huge amount of people using anything else.
I freely agree that people use Protoype, Moo
This is that api I propose. If it is agreed upon by core team then a
patch can easily be created.
# create a demo app with prototype javascript
# in this way current behavior is not changed
> rails init demo
# create a demo app with latest stable jquery
# http://github.com/rails/jquery-ujs should
> Of course 16% has to be taken with some margins, but you can't deny it
> makes difficult to claim that the vast majority of Rails developers
> use jQuery exclusively, which was the claim in (1). That is a strong
> claim! (1 was originally stated as a feeling not a fact, that's fine).
>
> If the p
On Thu, May 27, 2010 at 12:45, Xavier Noria wrote:
> On Thu, May 27, 2010 at 5:32 PM, Yehuda Katz wrote:
>
>> The idea that 16% of Rails users use jQuery is divorced from reality.
>
> But you are talking perceptions, and the sample talks numbers.
>
> Of course 16% has to be taken with some margin
Taking a sampling of libraries from the home pages of the six example sites
listed on http://rubyonrails.org/ (Who is already on Rails?)
jQuery: Twitter, Shopify, Yellow Pages, Github
Prototype: Basecamp, Lighthouseapp
I only looked at the source of the home pages, and may have missed a jQuery
On Thu, May 27, 2010 at 5:55 PM, Andy Jeffries wrote:
> I completely disagree, just because people don't use jrails, doesn't
> mean they're a prototype user. I generally bring in jQuery manually
> and delete all the prototype cruft from my projects, but I then write
> my own jQuery code to do sp
Xavier, I for one never use jRails -- in fact, neither do most of the
rails devs i know. We do, however, use jQuery.
The JavaScript helpers in Rails 2.3 were rather ugly, from a jQuery point
of view, which probably explains why not that many people felt like using
jRails.
Daniel
On Thu, May 27,
On May 27, 2010, at 12:51 PM, Daniel Schierbeck wrote:
> Xavier, I for one never use jRails -- in fact, neither do most of the
> rails devs i know. We do, however, use jQuery.
>
> The JavaScript helpers in Rails 2.3 were rather ugly, from a jQuery point
> of view, which probably explains why not
Hi all,
I just submitted a patch to 2-3-stable on lighthouse and wanted to
bring it to folks general attention.
https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/896-be-a-little-more-discerning-about-which-exceptions-to-handle
My explanation is a bit long-winded, but here's the
I would not go changing this in a minor release. Major or bust.
Ryan Bigg / Radar
On 28/05/2010, at 1:58, Norman Clarke wrote:
On Thu, May 27, 2010 at 12:45, Xavier Noria wrote:
On Thu, May 27, 2010 at 5:32 PM, Yehuda Katz
wrote:
The idea that 16% of Rails users use jQuery is divorced f
I personally disagree. With a limit backwards compatibility, current
Prototype users could have a simple command line switch to regain
their old default. Furthermore, I feel that the default JS library is
the least coupled piece of Rails 3 -- changing it is rather
unobtrusive, as long as bindings a
Why? SQLite3 was made the default database in 2.0.2 and the world
didn't stop. It's a change that affects people creating new Rails
applications - not ones that have already been created.
I'm a big fan of jQuery too but maybe at this point it would be nice
to take an issue off the core team's tabl
I agree. Let's get 3.0 out and table this until then.
Deal?
Yehuda Katz
Architect | Engine Yard
(ph) 718.877.1325
On Thu, May 27, 2010 at 2:24 PM, Norman Clarke wrote:
> Why? SQLite3 was made the default database in 2.0.2 and the world
> didn't stop. It's a change that affects people creating
On 28 May 2010 07:24, Norman Clarke wrote:
> Why? SQLite3 was made the default database in 2.0.2 and the world
> didn't stop. It's a change that affects people creating new Rails
> applications - not ones that have already been created.
>
There's a big difference between changing the default dat
I'd like to see vbscript as the default, but I guess we can wait until
Rails 3 ships first.
On Thu, May 27, 2010 at 4:57 PM, Ryan Bigg wrote:
>
> On 28 May 2010 07:24, Norman Clarke wrote:
>>
>> Why? SQLite3 was made the default database in 2.0.2 and the world
>> didn't stop. It's a change that
25 matches
Mail list logo
