Big Updates today…
Today I have released several new items..
First, I have updated my Effects widget (0.6) to include 8 new effects designed to be plugged into a YUI Panel/Overlay/Container. You can see them here.
Second, I would like to introduce YAHOO.Tools. This batch of tools has the following built in functions:
- makeTextObject
- makeChildren
- styleToCamel
- removeQuotes
- trim
- stripTags
- printf
- hasBRs
- convertBRs2NLs
- stringRepeat
- stringReverse
- setStyleString
- getSelection
- removeElement
- setCookie
- getCookie
- deleteCookie
- getBrowserEngine
- getBrowserAgent
- checkFlash
- setAttr
- create
- insertAfter
- inArray
- checkBoolean
- checkNumber
And lastly, I would like to introduce YAHOO.DHTMLForms, these you just have to see…
Enjoy 
November 2nd, 2006 at 12:35 pm
Thanks!
November 10th, 2006 at 9:58 am
Hi,
Unfortunately, the “delete” links of your DHTML forms are broken in IE7. They all give the error “Line 363 this.config.container is null or not an object”.
Some of your tools seem useful although if you frequent comp.lang.javascript you would soon see that most of the programmers there believe it is unwise to depend on the browser or agent. They encourage programmers to check for functionality, not browsers or browser versions. The reason I mention this is that I came to your blog from a question about browser checking on the YUI mailing list. Your tools certainly gave the questioner “an” answer but perhaps the wrong direction.
Sincerely,
Bob Gulian
November 10th, 2006 at 10:29 am
Bob–
The DHTMLForms code has been updated to catch that error.
As for the Browser detection, what is wrong with the 2 options I have created for detecting browsers?
The first option “getBrowserAgent” checks the browser based on the UserAgent string. This however is not “my” preferred way of doing it, but there are others that would say “That if they user changes their UserAgent string on purpose, then it is reasonable to assume that they expect pages to act incorrectly”. I provided that code, for that reason.
The second option “getBrowserEngine” uses object detection to determine the browser Engine that you are using, so you may code safely for that engine. My choice for that came from my work building a Rich Text Editor. There I would constantly be querying for, is this supported, is that supported. When it all boiled down to the Browser Engine that I was needing to take action against. Also, I tried to “bucket” the engines into the Grade-A browser chart & nothing more.
Hope that answers your question.
November 12th, 2006 at 11:16 am
These are great ! I don’t like the image for the radio buttons .. but we’re not designers !
It would be nice to see keypresses for tab/space etc added to the components so that they behave exactly like their standard counterparts.
Is any of the great stuff yourself, Dustin Diaz or Jack Slocum have created with YUI and extensions going to be incorporated into YUI ? I’m aware that you work in a different department but there hasn’t been a major release for a while and there is certainly a lot of interest in the content you’re creating.
November 12th, 2006 at 12:05 pm
I ganked the radio button icons from somewhere online
I really need some new ones..
I haven’t added anything to them since they where released, I am waiting on more feedback before I add new functionality. I’ll keep that in mind for the next release..
I think there is a new release for the YUI libs coming next month, but don’t quote me