> I've got quite a few bits and pieces that I will take a good long look
> at - some of them may be useful patches. I also have a couple of
> suggestions that I'll mail to the developer list - they are mostly to
> do with breaking up some of the existing code into smaller chunks to
> make inheritance easier.
As long as it doesn't break existing applications...
>
> I don't have a great deal of time at the moment but I'll try to get
> you a couple of patches within a couple of weeks (for some reason
> selling house + buying house + 1 month old son + finally getting
> divorced from ex so I can marry my partner + full time job + part time
> job seems to be filling my days, dunno why).
And you managed to write this message, wow! :)
>> * put POST and GET data in $r->{params} and deprecate $r->query
>
>
> Yes! I think that this needs to be examined rather carefully - I'm
> not sure that it handles
> situations where multiple parameters have the same name correctly (nor
> am I sure what
> 'correctly' means in this situation).
There i am also not sure, would it be enough to put both in an array?
Or use query param only if POST param is not available?
> I guess that this could be handled by simply supplying a new
> Maypole::View::XXX rather than replacing Maypole::View::TT.
Agreed.
>
> So... the question is... does that all sound sane?
Everything that makes us more flexible is sane in my eyes. ;)
Cheers,
Sebastian
_______________________________________________
maypole mailing list
maypole at lists.netthink.co.uk
http://lists.netthink.co.uk/listinfo/maypole
This archive was generated by hypermail 2.1.3 : Thu Feb 24 2005 - 22:25:56 GMT