Probably best not to post this to rails-core - try the engines lists
instead. To answer your question, you might not see the error if
active_rbac is explicitly require-ing it's controllers, which is what
plugins must do with 1.1.6.
- james
On 8/10/06, Adam Fields <[EMAIL PROTECTED]> wrote:
It's
On 7/26/06, Ryan Lowe <[EMAIL PROTECTED]> wrote:
The downside is that it could clutter the test run output at the
console (I don't usually check the test logs for output, so error
messages there would go unnoticed) ... I understand if this suggestion
isn't liked because of that reason, I just tho
Hello all,
I've been doing quite a bit of rooting around the plugin system
recently, and one thing in particularly has me puzzled and bemused. At
the moment, the test:plugins task has a dependency on the :environment
task, thus loading up Rails in all it's resplendent glory. Once it's
done this i
On 7/17/06, zdennis <[EMAIL PROTECTED]> wrote:
> That said, I think providing an 'import' method as a plugin would
> certainly be useful to some people (especially those too lazy to
> connect to a database by hand).
I like to automate tasks, if that makes me lazy, then I am lazy.
Me too - I mu
On 7/17/06, zdennis <[EMAIL PROTECTED]> wrote:
AR is so well thought out and designed, this seems
like a core feature that is just simply missing.
Since you are looking for speed to the point where you are sacrificing
validations, and pretty much anything else vaguely active-record-ish,
beyond
Since the behaviour is different from that of create (i.e. no object
instances are returned), why not just define a new method which
clearly indicates it's aptitude for inserting large amounts of data?
Model.import(hashes) or something...
- james
On 7/17/06, zdennis <[EMAIL PROTECTED]> wrote:
-
Agreed - it doesn't seem harmful to include aliases such that people
*can* call kibibyte and get the correct result, or possibly even move
the actual implementation into those new methods and redefine the
kilo/mega methods as aliases*...
However, changing the default behaviour of kilobyte and meg
You want to speak to Nathaniel Brown @ http://inimit.com/
HTH,
- james
On 4/9/06, Giles Bowkett <[EMAIL PROTECTED]> wrote:
> Quick question. Is the organizer for Canada on Rails on here? I'm
> hoping to organize a tech conference on a different topic so it would
> be massively useful for me to l
The change in revision 3953
(http://dev.rubyonrails.org/changeset/3953) seems to have broken some
AJAX helpers for me. In a test view .rhtml file,
<%= link_to_remote 'blah', :url => { :action => "test", :param1 =>
'A', :param2 => 'B'} %>
produces
blah
(notice the "&" between parameter
I have seen this error recently - have you updated to the latest
version of Engines trunk? It stems from a recursive failure during the
redefinition of require_or_load, because the Rails::VERSION module
wasn't already loaded. It should be fixed in the latest trunk.
- james
On 3/21/06, Francois Be
I just noticed that the assigns() method has been dropped from
action_controller/test_process.rb
(http://dev.rubyonrails.org/changeset/3724). Was this an oversight or
is there a new process for working with controller instance variables?
--
* J *
~
___
I think in your particular case it's perfectly fine to require the
developer to add a special line - after all, this is a piece of code
that will (hopefully) become a part of the core. It's just a fact of
the way the plugin system works at the moment that some aspects of of
the framework cannot be
Rails engines do indeed let you migrate sections of your application
independently. It's pretty simple to achieve; the implementation can
be seen in these files:
http://opensvn.csie.org/rails_engines/engines/trunk/lib/engines/migration_extensions.rb
http://opensvn.csie.org/rails_engines/engines/tr
On 1/29/06, Tom Ward <[EMAIL PROTECTED]> wrote:
> As you can see, you can pass a full connection string as the dsn. I'd
> like to factor the common parameters out of this string (server, db,
> password, user) and use standard yaml
> attributes to specify them, but I need to check how this will aff
I'll take a stab at it this weekend.
On 1/27/06, Duane Johnson <[EMAIL PROTECTED]> wrote:
> > Also, please someone do investigate #3474. I'd really like to declare
> > a death to white screens in 1.1.
>
> Does anyone feel qualified to look at this? I can take a look, and
> see what I can do. Any
At a slight tangent, isolating application sessions won't fully solve
this problem; you can change the name of a Model object and see this
'white screen of death' within the same application. Something needs
to be wrapped around the session loading to let Rails gracefully
handle loading a malignant
How likely d'you thing it is that this plays a significant part in the
oft-discussed 'Rails has problems with modules' issue?
- james
On 1/19/06, Florian Weber <[EMAIL PROTECTED]> wrote:
> I wrote a patch for that a while ago, but then got distracted. Will
> follow up on it and let you guys know.
I would love to be able to do this. The one sticking point that I've
come across at the moment is the way that Rails' dependencies
automatically creates modules for ApplicationController subclasses.
Continuing the WikiEngine example, intuitively you'd want to put your
controllers underneath the Wi
To answer Abdur's question - as I understand it, the core team want to
keep the plugin system very simple, and while there are some
mechanisms to handle plugin 'dependencies' (the private method
'load_plugin', for example - I can't find the Ticket that discusses
this in its comments), there has als
I'm not sure this is what Duane was suggesting - all his patch gives
is some optional control over which table and which class is used to
load a particular fixtures file...
- james
On 12/20/05, Tobias Luetke <[EMAIL PROTECTED]> wrote:
> What is the reason for making fixtures more complicated?
> I
I can second this interest - I've adapted Duanes patch for our
projects and it's a sound piece of code, I can't see any reason why it
shouldn't be a part of Rails proper.
On 12/18/05, Duane Johnson <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I talked with bitsweat about flexible fixtures at RubyConf but
21 matches
Mail list logo
