Yeah I definitely agree that this should change. It's actually bitten
me a couple of times where I, when writing my initial tests, would
forget to write the XML view, but the test still passed because it
rendered the HTML template. Bad Rails! Bad!
Would love to see this implemented to be more
Hey guys and gals,
I suggested that perhaps we should use Integrity
(http://github.com/foca/integrity) for the CI for Rails rather than
CC.rb. DHH said he was all for it, but I should bring it before you
all before he made a decision.
So, here's why I like Integrity:
1. It needs less hacking t
Looks awesome. Thanks for doing that; you did all the refactorings I
didn't have time to get to! :)
--Jeremy
On Fri, Dec 26, 2008 at 12:10 PM, AQ wrote:
>
> Since this email, Lifo urged me to write tests for the Template Runner
> (which has 0 tests in master currently).
> I've submitted anothe
Such as http://guides.rails.info ? That's all part of the docrails stuff.
Anything other than contributing to those would be completely
redundant, in my opinion. :P
--Jeremy
On Thu, Oct 30, 2008 at 11:51 AM, Daniel Schierbeck
<[EMAIL PROTECTED]> wrote:
>
> I'm thinking about essentially having
Then how would any software ever progress?
I have Windows 95 software that's incompatible with Windows XP. I
still have licenses for OCX controls from VB4 that don't work with
.NET. But this incompatibility is necessary to ensure progress and
refinement of the software products.
I realize the
You say it like "we just need volunteers." I've worked feverishly to
little result to wrangle people into writing Rails documentation.
If you know of a mythical large group of people who want to write
docs, then please whip them into a documentation fury and unleash them
upon Rails.
--Jeremy
O
The fact that there are two caveats to the theoretical approach are
probably a testament as to how useful it will actually be.
I think the UTC timestamps are great. Someone earlier said this
should be solved by communication, but then people are now saying that
it's a problem that people have to
I actually had 3 different people come up to me at MySQLConf and tell
me their AR connections were dropping like this and not reconnecting.
It might be something you want to check into (though I don't think
there's a verifiable way to test it).
I'll try to find out more information from those guy
I didn't really see where he was getting ahead of himself. He's done
a lot of hacking on this and he was saying that if you take his
patches/changes then backwards compatibility could be hard. If you
don't, well, who cares? That's the beauty of Git: he can maintain his
own repos of the code, yo
No, no, no! You see, if you do that then it's one step to
EigenClass::ClassFactory::ApplicationFactory::Application::ApplicationSpace::MyApplication::Factories::ModelFactory::Interfaces::IModel
<
EigenClass::Namespace::Rails::ApplicationAPI::Abstract::Interface::Models::ActiveRecord::Base
Then
I believe someone received/is working on getting a dump of the wiki to
set it up somewhere on an anti-spammed, stable wiki package.
I'm not sure of the status of that...
I would suggest setting that up before doing any work on it; otherwise
your edits will get overrun by spammers.
--Jeremy
On
There is already a considerable group of us laboring on documentation.
We have a Basecamp if you'd like access, and a mailing list (I think;
if not, we need one).
That goes for anyone else also. :)
--Jeremy
On Jan 4, 2008 5:09 PM, Anthony Kelly <[EMAIL PROTECTED]> wrote:
>
> DHH wrote:
> > Tha
Yeah we moved all the book work over to the Basecamp. I think we're
keeping the core work there and then we'll handle tickets, issues, and
other input through Lighthouse.
We'll hopefully have some more information soon (we're hacking out an
outline and such at present).
--Jeremy
On Jan 2, 2008
The typical form, I think, is something like:
DEPRECATION WARNING: The +breakpoint+ command has been renamed to
+debugger+.
--Jeremy
On Dec 27, 2007 5:01 AM, mikong <[EMAIL PROTECTED]> wrote:
>
> On Dec 27, 5:53 pm, Frederick Cheung <[EMAIL PROTECTED]>
> wrote:
> > On 27 Dec 2007, at 08:13
I disagree with that. I don't know anyone who uses SQL Server unless
they have to (especially with Rails). Installing mySQL is as simple
as downloading the installer and running it.
I think the sqlite default makes sense; I would guess the majority of
Rails developers are probably on some sort
I believe that the ruse project is in use on RubyGarden now (not
positive). It's written in Ruby and offers a lot of the features you
mention.
It seems that all of the web pages related to it or using it are down
at the moment, but maybe they'll get them back up soon. :)
--Jeremy
On Dec 17, 20
For the record, the manuals are being worked on. :)
They are in a sad state, to be sure.
--Jeremy
On Dec 15, 2007 12:02 PM, Scott <[EMAIL PROTECTED]> wrote:
>
> On Dec 14, 11:25 am, Manfred Stienstra <[EMAIL PROTECTED]> wrote:
> > On Dec 14, 2007, at 11:21, Sven Fuchs wrote:
> >
> > > I'd like
+1
Jeremy McAnally changes keywords for this thread to "retrospective verified"
;)
--Jeremy
On Dec 14, 2007 1:08 PM, revans <[EMAIL PROTECTED]> wrote:
>
> +1
>
>
> On Dec 13, 4:06 pm, James Cox <[EMAIL PROTECTED]> wrote:
> > Josh,
> >
> >
The Django book is interesting, but (a) it was written by the creators
of Django and (b) it hasn't been updated in some time because they are
working on the dead tree version or something (which is actually out
of date before it even hit the shelf heh).
I loved the model though; the way they set
Because it's $30-40? I always hated the fact that to really get into
Rails I had to shell out for a book. Every time I looked for
narrative documentation of any sort, I was always pointed to a random
blog or the book (usually the latter). It actually sort of instilled
this weird, totally unfound
Kind of like we've been trying to do over at
http://www.railsdocumentation.org/ to no avail? ;)
It's very hard to get people excited about doing documentation (unless
you're offering $$$). Honestly, it's hard (it's very difficult to
step out your own frame of reference and think about to write d
I typically don't use migrations for "seed" data; instead, I use
something like "rake db:bootstrap" or something like that.
Is there a reason you prefer migrations?
--Jeremy
On Nov 14, 2007 12:29 AM, Michael Koziarski <[EMAIL PROTECTED]> wrote:
>
> > 1 ) What, then, is the preferred mechanism f
I rarely use the same username and password for my production and
development databases, so not only does this obfuscate the file a
little bit it also makes me have to do more work when I get ready to
do production testing and deployment.
--Jeremy
On Nov 4, 2007 2:32 PM, Robert Evans <[EMAIL PRO
Given the chance, I'd work on the manuals site to at least update
what's there. I've contributed a lot to the API docs before, but lost
interest/time capacity (due to a lot of issues that been discussed and
fixed).
Now, I have more time and have been looking at doing some API docs,
but it seems
Could we get a Trac for report unreviewed tickets to make this process
easier? Maybe a keyword or something like that?
--Jeremy
On 7/16/07, Matthew Palmer <[EMAIL PROTECTED]> wrote:
>
> [Let's give this a go, shall we?]
>
> As per http://wiki.rubyonrails.org/rails/pages/PatchRequirements, I'm
>
I feel your pain here...perhaps it would be better if keywords were
used to remove things from the normal report and put them only in the
reports where they belong (e.g., undocumented == the "Undocumented
Patches", same with untested, etc.). That way it's not "closed" but
the submitter is told th
26 matches
Mail list logo
