Hi everyone,
This year my company (https://subvisual.co/) will have a student doing his
master thesis with us, and need to come up with a topic. I was wondering if
there was anything on Rails tangentially related to his areas of expertise
that could benefit from a person working on it essential
onality into ActiveRecord, is it
>> something that core might entertain merging?
>>
>> Thank you,
>>
>> Caleb Thompson
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Ruby on Rails:
ing emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
> For more options, visit https://groups.google.com
eiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
> For more options, visit https://groups.google.com/gro
this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
> For more options, visit https://
Rails: Core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-core+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> Visit this group at http://groups.google.com/gro
s message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/rubyonrails-core/-/w9m1BdhJ-Y8J.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> To unsub
o
> rubyonrails-core+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/rubyonrails-core?hl=en.
Cumprimentos,
Luís Ferreira
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core"
com/d/msg/rubyonrails-core/-/u1PNgYmkABUJ.
> To post to this group, send email to rubyonrails-core@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/r
ils-core+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/rubyonrails-core?hl=en.
>
Cumprimentos,
Luís Ferreira
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To p
send email to
> rubyonrails-core+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/rubyonrails-core?hl=en.
Cumprimentos,
Luís Ferreira
--
You received this message because you are subscribed to the Google Groups "Ruby
on Ra
es you should wait for the engine's
> developers to accept or implement required changes.
>
> The decorator pattern provides a handy, direct and neat mechanism to achieve
> the stuff.
>
>
> El 01/10/12 12:08, Luís Ferreira escribió:
>>
>> What if the engine&#x
Groups
>>>>> "Ruby on Rails: Core" group.
>>>>> To post to this group, send email to rubyonrails-core@googlegroups.com.
>>>>> To unsubscribe from this group, send email to
>>>>> rubyonrails-core+unsubscr...@googlegroups.com.
Yes, seems obvious. Just pointing that out. But the changes seem really nice
and makes the placing of test files more obvious and semantic.
On Sep 30, 2012, at 12:36 AM, Mike Moore wrote:
> On Sep 29, 2012, at 5:17 PM, "Luís Ferreira" wrote:
>
>> One question though, whe
>
>
> --
> 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 from this group, send email to
> rubyonrails-core+unsubscr...@
e, :main_app, :all ]
>>
>> Then your monkey patching should work.
>>
>> If you are on older versions of Rails you can monkey patch AS::Dependencies
>> like http://www.slideshare.net/AndyMaleh/rails-engine-patterns (Slide 17).
>> You probably want to watch the
;
> On Fri, Sep 28, 2012 at 12:59 PM, Luís Ferreira wrote:
> Hey guys,
>
> I've been working on engines lately and I can't understand why a class in an
> engine can't be monkey patched. Here's an example:
>
> In the engine:
>
> class MyEngin
it does not read the file from engine at all, and just reads the
> file from your app.
>
> Robert Pankowecki
> http://robert.pankowecki.pl
>
> On Fri, Sep 28, 2012 at 12:59 PM, Luís Ferreira wrote:
> Hey guys,
>
> I've been working on engines lately and I can't
aviour?
Is this a feature or a bug?
Regards,
Luís Ferreira
--
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 from this group, send
e Google Groups
>>>>> "Ruby on Rails: Core" group.
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msg/rubyonrails-core/-/a9Xaa3XtugcJ.
>>>>> To post to this group, send email to rubyonrails-cor
Sep 5, 2012, at 8:47 AM, Luís Ferreira wrote:
>
>> Hi,
>>
>> Is there any reason why helpers cannot render partials?
>>
>> I would like to do something like this in the layout:
>>
>>
>> <%= magic_header %>
>>
>> <%= yield
end
Why is this wrong?
Cumprimentos,
Luís Ferreira
--
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 from this group, send email to
rubyonrails-c
Hk98ctgQJ.
> To post to this group, send email to rubyonrails-core@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/rubyonrails-core?hl=en.
Cu
bscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/rubyonrails-core?hl=en.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Core" group.
> To post to this g
://groups.google.com/group/rubyonrails-core?hl=en.
>
>
> --
> 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 fro
"Ruby on Rails: Core" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/rubyonrails-core/-/MNYYrHc3b_gJ.
> To post to this group, send email to rubyonrails-core@googlegroups.com.
> To unsubscribe from this group, send email to
> rubyonrails-core
You are right, I can probably achieve my goals with a unique index and a
validates_uniqueness_of with :scope.
Thanks for the tip
On Jun 14, 2012, at 10:05 PM, Michael Koziarski wrote:
> On Friday, 15 June 2012 at 4:54 AM, Luís Ferreira wrote:
>> Hi,
>>
>> Is there any par
Hi,
Is there any particular reason why AR does not support composite primary keys?
This looks like a pretty nice feature to add.
Regards,
Luís Ferreira
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this g
ready implemented in master, then great, I hope it to be
> backported to 3.2.6 when it gets released...
>
> Thanks,
> Rodrigo.
>
> Em 05-06-2012 10:22, Luís Ferreira escreveu:
>> It creates the lib/some-example/engine.rb file which is just as you
>> described and t
ooglegroups.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/rubyonrails-core?hl=en.
>
Cumprimentos,
Luís Ferreira
--
You received this message because y
nrails-core?hl=en.
>>
>>>>> --
>>>>> 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@google
cationController
> # do your monkey patching here
> end
>
> Just make sure this is in a file that gets loaded when your engine loads -- I
> would suggest an initializer, but ...
>
> Sent from my iPhone
>
> On May 24, 2012, at 9:06 AM, Luís Ferreira wrote:
>
>&
way you main application stays unaltered and each engine can access this code
> and change its behavior without affecting the main app or other engines.
>
> Sent from my iPhone
>
> On May 24, 2012, at 8:31 AM, Luís Ferreira wrote:
>
>> Ok. This will solve the problem
amed file in the engine. The same goes for
> anything else in the app directory, too.
>
> This is why you namespace your engine: to avoid collisions such as these.
> On Thursday, 24 May 2012 at 4:46 AM, Luís Ferreira wrote:
>
>> Hi,
>>
>> I've been us
amed file in the engine. The same goes for
> anything else in the app directory, too.
>
> This is why you namespace your engine: to avoid collisions such as these.
> On Thursday, 24 May 2012 at 4:46 AM, Luís Ferreira wrote:
>
>> Hi,
>>
>> I've been using rails
controller has methods or anything else
that does not collide with the stuff defined with the app, couldn't it be used?
Isn't this the default behaviour of ruby, that you can just reopen a class and
add methods to it possibly overriding them but not deleting the rest of the
class?
36 matches
Mail list logo
