I can understand that. But in my architecture, I build some basic classes and functions that sit at the bottom of my library and are used by ALL other implementations.
My core library (which sits on top of jQuery) has about 50 core methods and every single one of those are tested, tweaked and tested again on my 5 main browsers, practically line-by-line. It took me about a month to dial it in. The remainder is all built on top of it and while I do test on other browsers, it's nowhere near as extensive (as it doesn't need to be). JK -----Original Message----- From: jquery-en@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of McLars Sent: Thursday, January 03, 2008 2:04 PM To: jQuery (English) Subject: [jQuery] Re: Debug Tools - Charles, DebugBar, Firebug Lite Benjamin, I think (hope) we all test occasionally on all the browsers, while we're developing. But, frankly, I'm not going to test every single line, or block, or function, or whatever, on every browser. The reality is that I have one browser I write the bulk of my code with and all the others are just used for testing and tweaking. As for the "standards" part, that is flame bait for me. Standards don't mean poop to me. They're for idealists. I live in the real world, and I don't have religeon or an agenda. :) Larry On Jan 3, 2:29 pm, "Benjamin Sterling" <[EMAIL PROTECTED]> wrote: > Not trying to flame bait here, but I really don't see what so hard about > dealing with ALL browsers at once. I hear all the time how hard it is to > code for IE and, although I dot come across issues that I need to adjust > for, I never feel that I can't do something with IE. I guess if you know > the limitations going into a development of a site it is easier to deal > with. I just don't get the "Build for IE and every other browsers will just > have to deal." > > I say grab a copy of each browser you want to support, open each up and test > in each as you go. Stick to "basic" standards and everything should be > fine. > > Just my two cents. > > On 1/3/08, Andy Matthews <[EMAIL PROTECTED]> wrote: > > > > > > > > > Larry... > > > I'm RIGHT there with you. Better to develop in IE, then move forward into > > other browsers. Better than getting cool code working with a "fringe" > > browser, then finding out it doesn't work correctly in the primary > > browser. > > > -----Original Message----- > > From: jquery-en@googlegroups.com [mailto:[EMAIL PROTECTED] On > > Behalf Of McLars > > Sent: Thursday, January 03, 2008 1:59 PM > > To: jQuery (English) > > Subject: [jQuery] Re: Debug Tools - Charles, DebugBar, Firebug Lite > > > IEDeveloperToolbar is somewhat helpful, but kinda flaky. Honestly, though, > > 99% of the time I just use alert(). I have Firebug, but never use it since > > I > > develop on IE. As you said, that's what the vast majority of (and all of > > our > > intranet) users are on. > > > I know that is contrary to how many develop, but I feel it's better to > > develop on the weaker and more popular platform. If it works on IE, FF, > > Opera, and Safari are usually pretty close. It's better to find the bugs > > while you work, rather than build a lot of stuff only to find it fail in > > IE--where the debugging is limited. > > > That's just my personal choice, but I don't have very many bugs. ;) > > > Larry > > > Jeffrey Kretz wrote: > > > There's a bit more overhead, but the free Visual Studio Web Express > > > Edition has a very good debugger: > > > >http://www.microsoft.com/express/vwd/Default.aspx > > > > I use Firebug as well, but I feel that this is the best IE debugger > > > available. > > > > JK > > > > _____ > > > > From: jquery-en@googlegroups.com [mailto:[EMAIL PROTECTED] > > > On Behalf Of Benjamin Sterling > > > Sent: Thursday, January 03, 2008 10:19 AM > > > To: jquery-en@googlegroups.com > > > Subject: [jQuery] Re: Debug Tools - Charles, DebugBar, Firebug Lite > > > > In IE I use a combination of DebugBar, IEDevelopemnt toolbar and Opera > > > (IE and Opera use more or less that same javascript engine and Opera > > > has a nice Error console). I also us the iLogger plugin[1] > > > >http://trac.asterisk2billing.org/cgi-bin/trac.cgi/browser/tags/1.3.1/A > > > 2BCust > > > omer_UI/javascript/jquery/ilogger.js?rev=462 > > > > On 1/3/08, Christof Donat < [EMAIL PROTECTED]> wrote: > > > > Hi, > > > > > What debug tools do you all use? [...] How about tools for IE? > > > > Is there anything you'd reccomend? > > > > alert() > > > > Christof > > > > -- > > > Benjamin Sterling > > >http://www.KenzoMedia.com > > >http://www.KenzoHosting.com > > >http://www.benjaminsterling.com > > -- > Benjamin Sterlinghttp://www.KenzoMedia.comhttp://www.KenzoHosting.comhttp://www.benja minsterling.com- Hide quoted text - > > - Show quoted text -
