You're right of course - telling anyone to go work at Microsoft is hitting
below the belt. Brice's posts lean towards the abrasive and this one just
set me off. My apologies.
Most of the "new person" questions on this list involve issues that could be
resolved easily if they could just see what is going on inside the code.
Firebug helps, but having a simple debug function available to people who
don't understand why they need a plugin just to get a "simple" jquery
function working would be very useful. How many times have you seen
questions about broken code that turns out to be a selector problem? Most
of those folks are just reading the documentation on the site and aren't
even thinking about extending the core package yet.
It doesn't matter in the end. pasting my debug function into the jquery.js
script solves my problem for the moment. I had just hoped to help the new
folks not hit the same walls I did when I was getting started.
Karl Rudd wrote:
>
> Daemach I think you may have read a little too much harshness into
> Brice's reply. Brice may have needed to use a little clearer, not so
> open to being interperated as harsh.
>
> Brice is quite helpful usually so it would be out of character for him
> to beat someone down.
>
> We're all learning here, so let's try to keep things calm and civil.
>
> Your debug console idea is definately something that is useful and it
> would work quite well as a plugin (which is also what I believe Brice
> is saying).
>
> Karl Rudd
>
> On 3/13/07, Daemach <[EMAIL PROTECTED]> wrote:
>>
>> Thanks for the beatdown Brice! I'm glad you're the only jerk I've seen
>> on
>> this list!
>>
>> And don't be an elitist prick - some people reviewing this framework are
>> new
>> to jQuery and some even to javascript programming itself. If you can't
>> say
>> something nice, go work at Microsoft.
>>
>>
>> Brice Burgess wrote:
>> >
>> > Daemach wrote:
>> >> I would like to be able to dump the contents of the current selector
>> to
>> >> the
>> >> console using $"#myselector").debug() without loading a plugin.
>> >> Something
>> >> as simple as the following would work, though if you devs have some
>> ideas
>> >> on
>> >> how to make it more useful I'm sure it would be welcomed, especially
>> by
>> >> new
>> >> users:
>> >>
>> >> jQuery.fn.debug = function() {
>> >> console.log(this);
>> >> return this;
>> >> }
>> >>
>> >> Long chains that include callbacks with anonymous functions make it
>> >> difficult to use console.log($()). Can this be added to the jQ
>> codebase
>> >> so
>> >> it's always available?
>> >>
>> > This is a ridiculous, not well thought out, and highly
>> > individual/personalized request. Of course this should be a plugin! All
>> > debuggers are "plugins" AFAIK -- or, at least compile time flags.
>> Please
>> > keep the core lean, mean, and clean, and think thrice before bloating.
>> >
>> > ~ Brice
>> >
>> > ~ Brice
>> >
>> > _______________________________________________
>> > jQuery mailing list
>> > [email protected]
>> > http://jquery.com/discuss/
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Please-add-a-basic-debug-function-to-the-jQuery-core...-tf3392275.html#a9446525
>> Sent from the JQuery mailing list archive at Nabble.com.
>>
>>
>> _______________________________________________
>> jQuery mailing list
>> [email protected]
>> http://jquery.com/discuss/
>>
>
> _______________________________________________
> jQuery mailing list
> [email protected]
> http://jquery.com/discuss/
>
>
--
View this message in context:
http://www.nabble.com/Please-add-a-basic-debug-function-to-the-jQuery-core...-tf3392275.html#a9446792
Sent from the JQuery mailing list archive at Nabble.com.
_______________________________________________
jQuery mailing list
[email protected]
http://jquery.com/discuss/
