On Saturday 09 December 2006 00:16, Rich Collins wrote:
> Thanks for the links. I think it would be fair to characterize the
> objects created by my plugin as "Presenters".
I don't think so. Presenters and Presentation Models correspond to a
single view from which they extract as much "intellig
Ticket #4245 has a small patch [1] fixes custom rake tasks and
generators for plugins that are symlinked. It changes Dir.glob from
using /**/ (which doesn't follow symlinks) to use /*/**/, which will
follow one symlink without any adverse effects.
I would appreciate it if someone would app
Thanks for the links. I think it would be fair to characterize the
objects created by my plugin as "Presenters". They generate data
(html markup) related to the presentation of the models without
explicit instructions regarding the layout (css).
I see that people are going to be hung up
I just noticed that the shortcut mentioned in the Rails Edge API
documentation doesn't seem to actually work as specified; the nested
selector doesn't seem to be restricted to one of the returned elements.
Example:
Okay, standard ordered list with four list items, within each item
On Dec 8, 2006, at 3:09 PM, Courtenay wrote:
>
> On 12/8/06, Brad Ediger <[EMAIL PROTECTED]> wrote:
>> On Dec 8, 2006, at 12:34 PM, Francois Beausoleil wrote:
>>> 2006/12/8, Michael Schuerig <[EMAIL PROTECTED]>:
If I understand your suggestion correctly, it amounts to sorting
and
On 12/8/06, Courtenay <[EMAIL PROTECTED]> wrote:
> FWIW, I didn't say to put extra methods in the model. Hell no.
>
> I was suggesting a layer between the model (or models) and the view
> which packages up certain methods, much like Liquid's Drops.
Thats essentially what the presenter pattern i
On 12/8/06, Brad Ediger <[EMAIL PROTECTED]> wrote:
> On Dec 8, 2006, at 12:34 PM, Francois Beausoleil wrote:
> > 2006/12/8, Michael Schuerig <[EMAIL PROTECTED]>:
> >> If I understand your suggestion correctly, it amounts to sorting and
> >> applying migrations based on timestamp. I think real time
On 12/8/06, Michael Schuerig <[EMAIL PROTECTED]> wrote:
>
> On Friday 08 December 2006 19:12, Rich Collins wrote:
> > I kind of pushed it out early as I heard something called presenters
> > were being considered. It was not really ready for external use, but
> > I wanted to put it out there to j
> What is the use case for sending clear text credentials from an html
> page anyway?
(Basing this on the assumption that "sending clear text credentials
from an html page" is required for NTLM, and SSO to work in at least
this intranet scenario that I am currently dealing with).
Use Case:
http:
Josh, I am looking forward to your email. We are picking up momentum
in trying to get other frameworks onboard the FastCGI train, but
unfortunately having some issues with Ruby due to our lack of
experience with it. Your help will be instrumental in getting RoR
running on Windows better - not ev
On Dec 8, 2006, at 12:34 PM, Francois Beausoleil wrote:
> 2006/12/8, Michael Schuerig <[EMAIL PROTECTED]>:
>> If I understand your suggestion correctly, it amounts to sorting and
>> applying migrations based on timestamp. I think real time is not the
>> right dimension for this as progress on dif
On Friday 08 December 2006 19:12, Rich Collins wrote:
> I kind of pushed it out early as I heard something called presenters
> were being considered. It was not really ready for external use, but
> I wanted to put it out there to join the impending conversation about
> OO helpers.
> I think we n
2006/12/8, Michael Schuerig <[EMAIL PROTECTED]>:
> If I understand your suggestion correctly, it amounts to sorting and
> applying migrations based on timestamp. I think real time is not the
> right dimension for this as progress on different branches is not
> coordinated by time. Rather, I suggest
On Friday 08 December 2006 18:53, Francois Beausoleil wrote:
> 2006/12/8, Brad Ediger <[EMAIL PROTECTED]>:
> > On Dec 8, 2006, at 7:04 AM, Courtenay wrote:
> > > Here's the patch :)
> >
> > That looks really neat. It's certainly simpler than my solution,
> > and I can't think of any problems with
I kind of pushed it out early as I heard something called presenters
were being considered. It was not really ready for external use, but
I wanted to put it out there to join the impending conversation about
OO helpers. I extracted it from an a real world application that we
are developi
2006/12/8, Brad Ediger <[EMAIL PROTECTED]>:
> On Dec 8, 2006, at 7:04 AM, Courtenay wrote:
> > Here's the patch :)
>
> That looks really neat. It's certainly simpler than my solution, and
> I can't think of any problems with that off the top of my head.
I don't know. Maybe we should drop version
On Friday 08 December 2006 10:44, [EMAIL PROTECTED] wrote:
> What we were talking about, was, the idea that models and views
> shouldn't really interact; rather, we could define an interface
> between the model and the view, similar to the way Liquid templates
> use a Drop to limit the fields to w
Actually, the model in no way relies on the implementation of the
helper. The reason that you separate the model from the view is that
you don't want your models implementation depending on any view of
the model. In this case, the model is untouched, other than the
forwarding of methods
Awesome! It's good to know you were already working on it! I hope
this topic gets more exposure, because IIS is the standard at the
office, and I want to use Rails at the office.
Peter
--~--~-~--~~~---~--~~
You received this message because you are subscribed
On 12/8/06, pboling <[EMAIL PROTECTED]> wrote:
> Would it be possible for someone on the core team to contact Mike
> Volodarsky:
> http://mvolo.com/2006/11/17/while-you-were-out-.aspx?results=1
> to discuss getting this working on RoR.
>
I have talked to Mike about this previously, and he emailed
The Microsoft webserver, IIS, is finally implementing FastCGI for
versions 5.1, 6, and 7. Zend (the PHP people) are working with MS to
get PHP supported, and PHP5 is supported in the technical preview
release out now:
http://www.iis.net/default.aspx?tabid=151
Would it be possible for someone
-1
Creative idea, but completely messes up the nice separation of
concerns we have going on right now in Rails. I think it would
detrimental in the long run.
On 12/7/06, Rich Collins <[EMAIL PROTECTED]> wrote:
> I heard in #caboose that you are interested in working on OO model
> helpers. I hav
On 08/12/06, Jarkko Laine <[EMAIL PROTECTED]> wrote:
> On 8.12.2006, at 5.23, Richard Vowles wrote:
> > I am having a problem - lots of the code uses (non-ANSI standard)
> > "field = NULL" instead of "field IS NULL". I am of the opinion that
> > the abstract adapter should add in a test for this t
[EMAIL PROTECTED] wrote:
> What we were talking about, was, the idea that models and views
> shouldn't really interact; rather, we could define an interface between
> the model and the view, similar to the way Liquid templates use a Drop
> to limit the fields to which you have access.
>
> The idea
On Dec 8, 2006, at 7:04 AM, Courtenay wrote:
>
> On 12/8/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>> self-reply here, pre-empting questions..
>>>
>>> Why can't we just have a ParallelMigration (IndependentMigration)
>>> subclass that doesn't check for duplicates in the numbering?
>>>
>>>
On 12/8/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> self-reply here, pre-empting questions..
>
> Courtenay wrote:
> > > Is this something that would be a useful addition to Rails core?
> > > I'd appreciate some feedback / criticism.
> > > >>>
> > > >>> Wow, this looks really compl
>
> Is this something that would be a useful addition to Rails core?
> I'd appreciate some feedback / criticism.
> >>>
> >>> Wow, this looks really complicated. I think the solution with all
Why can't we just have a ParallelMigration (IndependentMigration)
subclass that doesn't che
What we were talking about, was, the idea that models and views
shouldn't really interact; rather, we could define an interface between
the model and the view, similar to the way Liquid templates use a Drop
to limit the fields to which you have access.
The idea being, you could turn around the he
self-reply here, pre-empting questions..
Courtenay wrote:
> > Is this something that would be a useful addition to Rails core?
> > I'd appreciate some feedback / criticism.
> > >>>
> > >>> Wow, this looks really complicated. I think the solution with all
>
> Why can't we just have a Par
On 8.12.2006, at 5.23, Richard Vowles wrote:
Having had no response from my ActiveRecord query, is this the
right place to discuss it? Is somewhere else more active?
I am having a problem - lots of the code uses (non-ANSI standard)
"field = NULL" instead of "field IS NULL". I am of the opin
30 matches
Mail list logo
