Ok, guys....your disscusion are very fair and I need to accept your opinions.
But truthy be told, old things were always used to cache in memery, just like the feeling to Mootools 1.3. Even its code is more beautiful than Mootools 1.2.X. I always try to tell myself to accept the new code, even now I can not understand what the New code's meaning. Sometimes, when you got in customed to an old style, now, you need change, it is just like a pain..... As a gredute student in 2011-09, I now do not which way I will go. I can write some beautiful code by Javascript or by Python, I am always sorry to my fuking life..... OK....sorry to say so much..... All will gone....and I still like Mootools too..... HAHA.......... 2010/10/13 Olivier El Mekki <[email protected]> > Fair enough. In my experience, the only place where I used > Browser.Engine was for fixing ie6 css issues in dynamicly modified > content, but I always try to put most of the css in css files. I guess > including some .js in conditionnal comments may be a good way to go, > too. > > Maybe it would worth it to drop a note on mootools.net/docs/core/Browser > to warn mootools users that user agent detection should be avoided as > much as possible. > > On 15:03 Wed 13 Oct , אריה גלזר wrote: > > The thing is - for almost all scenarios - using browser detection is > already > > the wrong thing to do. You shouldn't be doing: > > > > if (Browser.ie) var xhr = new ObjectX(...) > > > > but rather - > > > > if (!(XMLHttpRequest in document)) .... > > > > And so the only scenario when you will be using Browser is when feature > > detection won't cut it - thus user-agent is a good and valid choice > > > > -- > Olivier El Mekki. > -- -------------------------------------------------------------------- HengZhou --------------------------------------------------------------------- --
