Yeah, aren't we supposed to be acolytes of Agile, and iterative
improvements?
--~--~-~--~~~---~--~~
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@googlegr
> What's "OP" ?
Original Poster - the person who started the thread.
--~--~-~--~~~---~--~~
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
Do we want to follow MYSQL, or any specific DB provider, practices,
over ruby's, though? And/or the standards? (Don't honestly know what
ANSI SQL has to say about -00-00).
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
On Nov 24, 8:53 pm, Greg Willits <[EMAIL PROTECTED]>
wrote:
> A typical example would be a Date Due field where a valid date = when it
> was done, a NULL value = not done yet that we know of, and a -00-00
> value = it has been declared that it never will be done. Reports for
> this data must b
There are cases where it'd be nice to be able to set the protocol (for
ssl) easily, when you don't have access to the X-FORWARDED-PROTO
header, such as in Jamis' post
http://weblog.jamisbuck.org/2006/10/3/mongrel-ssl-and-apache-1-3
. The current behavior also means ssl_requirement chokes under A
It's not just you (same here).
On Apr 25, 11:23 am, John Wilger <[EMAIL PROTECTED]> wrote:
> I'm getting a connection reset error when trying to access the Rails
> Subversion repository. Is anyone else seeing this, or is there
> something funky going on on my end?
--~--~-~--~~--
http://dev.rubyonrails.org/ticket/8187
This nicely supplements yesterday's changeset adding the .:format to
the default route: http://dev.rubyonrails.org/changeset/6576 as it
allows for leaving the trailing dot off if there is a default format.
Thus both Rails style and .format style URLS work.
I made a tiny patch (with tests of course) that calls to_time before
to_s(:rfc822). This means if pub_date is just a date, not a full
datetime, the feed will still be valid. As a side-effect, you get a
less cryptic nil error.
The patch also fixes a failing test on resource_feeder, at least on m
I wonder if nil.to_s should be extended to accept an optional
parameter and still throw the nil exception, to make errors on
nil.to_s with the Rails extensions less obscure?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google G
Please ignore. I still think it's a cryptic error to throw on a nil,
but there was a mistake in my code/data. to_s(:rfc822) works fine on
a date field, as long as it isn't null/nil.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to th
I guess I'll work around it with a lamda and a to_time, for now, but
to_s(:rfc822) exists in the rails time extensions, but not the date
extensions, so if you try to use a date field for pub_date it chokes.
My uncertainty is if to_s(:rfc822) should be added to Date (do a
to_time, first?) or if res
I wanted to check on this before submitting a patch - see if I am
missing anything. If you have a non resource route (useful, even when
doing REST, for supplying a different limited public access to your
rest controller, say) you have to add the format to the route
yourself, but having "." be in
Thanks, as well, Rich. So between this and drops it seems a favored
way of handling this dichotomy of responsibilities is presenter
classes of some sort. Well I suppose that looking to Martin Fowler
for patterns in Rails should be expected. ;)
Tim
--~--~-~--~~~---~
Hey Courtenay,
I guess I'll have to take a closer look at mephisto, if only for
another perspective in my ruminations. The risk of adding another
layer is, of course, building until you recreate the very thing you
were getting away from, but in someways having it more orthogonally
specified as a
On Apr 11, 2:35 pm, "Mislav Marohnić" <[EMAIL PROTECTED]>
wrote:
> On 4/11/07, Tim Connor <[EMAIL PROTECTED]> wrote:
>
>
>
> > And once you go down that road, that starts
> > looking like the more purely OO approach of just having the model
> &
The core team seems to be all about practicality, rather than theory,
but as I do more and more REST development, it gets me thinking
Mainly about how controllers are just becoming thin proxies for the
true object - models. And then I wonder, how far will this trend go.
Should Resource Feeder
On Mar 3, 7:40 pm, "Josh Peek" <[EMAIL PROTECTED]> wrote:
> The plugin is a direct port, no new enhancements, even though it could
> use some. O, and for the first time, scaffolding tests!
>
I'm not maintaining it anymore, but I did create a full dynamic
resource scaffolding plugin, last year, th
Sorry if this has been mentioned elsewhere, but I couldn't find a post
about it, or an explanation in the code. I double-checked the history
and it seemed to have been that way since it was first added.
I was encountering some oddities in styling my form, and realized that
there is a redundant (
I'll see what I can do ;)
On Mar 15, 2:17 pm, "Michael Koziarski" <[EMAIL PROTECTED]> wrote:
> > If I could track down and modify this behavior, would there be enough
> > interest in it (it may be right at the edge of my ruby-fu) to get it
> > patched in? I know the usual answer is "make a plugi
Looking over the discussions and Trac tickets am I correct in assuming
that the simply_helpful's form_for not respecting the
default_url_options (specifically only_path) is a side-effect of some
other default behavior choices?
Personally, I set only_path to true as my default as I think except
we
Whenever you are doing extremely large set operations, ANY ORM is going
to be slow. And row by row is always orders of magnitude slower than
whole set operations, in SQL. Might this not be a time to optimize
your model with a tiny bit of direct SQL?
I've literally seen improvements in multiple
Project moved to Google Code
http://code.google.com/p/dynamic-scaffold-resource/
Subversion history preserved, but clean checkouts required, as the repo
UID is changed, and the dynamic-scaffold-resource stuff is now in the
root of the repo.
--~--~-~--~~~---~--~~
Y
Dynamic Scaffold Resource is ready to go, pending your feedback:
http://www.timocracy.com/articles/2006/10/25/35-dynamic-scaffold-resource-rails-plugin-at-final-prerelease
Those few that expressed an interest please chime up with any comments
you have. And if any core members would care to tell
Okay stable
(http://svn.infosauce.org/rails/dynamic_scaffold_resource/branches/stable)
is now at 0.2 (tests done) and ready to be ripped to shreds. ;)
Aside from whatever ya'll might suggest it's just documenting it and
figuring out what to do about making the patch a breeze, now. Anyone,
who e
If I do good can I eventually get a biscuit - aka get it into core
(where someone with mad chops might clean it up), somewhere post 1.2?
;)
My only problem with the plugin is it definitely requires the tiny
patches from tickets 6412 and 6413, and I'd rather not have to
overwrite the whole ActiveR
Again I finally managed to answer my own question - by taking a look at
how the simply_resful plguin did it (since they obviously had to handle
this). Basically, I'm just depending on the path all the path all the
way up to the /config/environment.rb file and processing that. That
seems to work,
OK, I definitely need some help, now, getting the tests running. I've
been plundering the ActionPack tests heavily, but can't quite get it
right.
http://pastie.caboo.se/18578
http://pastie.caboo.se/18579
I'm getting the "No url can be generated for this hash" error that
indicates I haven't quite
So Alpha is out. Details at:
http://www.timocracy.com/articles/2006/10/17/8-dynamic-scaffold-resource-rails-plugin-is-officially-alpha
or for those who like to cut to the chase:
http://trac.infosauce.org/wiki/DynamicScaffoldResource (read here for
notes on installing, first)
and http://svn.infos
rator gives us, if it doesn't prove
to tricky. Ideally I'd like to let that function like the scaffold
code - if you manually create a test it doesn't run the default one.
Tim
On 10/17/06, Neil Wilson <[EMAIL PROTECTED]> wrote:
>
>
> Tim Connor wrote:
&
Actually, I answered most of my questions myself. I'll just try and
whip out a plugin for this, at least far enough to have something
showable, and then ask for comments.
Tim
On 10/16/06, Tim Connor <[EMAIL PROTECTED]> wrote:
> I was so excited to get going that I started on a p
ediate questions, where are the tests for the
scaffolding code? If I do a plug-in I'll obviously be doing my own,
but it'd be
Tim
On 10/16/06, Dr. Ernie Prabhakar <[EMAIL PROTECTED]> wrote:
>
> Hi Tim,
>
> On Oct 16, 2006, at 9:16 AM, Tim Connor wrote:
> > Am I compl
So I've RESTified a couple controllers, now, using the latest stuff in
Edge and they don't feel very-DRY. I realize that after they get more
complicated they will need to be able to be stand-alone, but they are
currently pretty wet. I considered working on an abstract REST
controller, but then r
32 matches
Mail list logo
