+1 for logging. It took me way too long to figure out how to get everything
working properly using a different (builtin) class. I agree with #19395
that an example (or two) would be great.
Here's what I'm currently using which makes use of a rotating file handler
and a custom date formatter (If it
On Tuesday, January 8, 2013 6:54:41 PM UTC+1, ptone wrote:
>
> You might want to attempt to write a patch for an open issue - reading the
> source code is one thing and you may learn a bit. But dissecting the source
> code when you have the purpose to fix a problem, gives you a much better
> u
You might want to attempt to write a patch for an open issue - reading the
source code is one thing and you may learn a bit. But dissecting the source
code when you have the purpose to fix a problem, gives you a much better
understanding of how things are working - as you NEED to understand them
Looks good overall Tim - I do think that the primary reference should be
kept alphabetical within core - this is most useful when you have a setting
you need to look up. But I do think that a 'by-topic' cross reference
index could also be very useful for discovering or learning about all
setti
Agreed, I'm +1 to keeping deprecated settings inline rather than moving
them to their own section, but I'd defer to whoever made the original
decision.
On Tuesday, January 8, 2013 4:58:17 AM UTC-5, Sam Lai wrote:
>
> Looks good. Adds a bit more structure for browsing but doesn't
> significantly
Looks good. Adds a bit more structure for browsing but doesn't
significantly change how the page is used, which is probably through
CTRL-F.
As mentioned by others in the issue, the distinction current and
deprecated settings seems very arbitrary. I think it'll be better to
sort the deprecated sett
