Yahoo! Widget Engine for Mac 4.5.2

Yahoo! Widget Engine for Mac is a JavaScript runtime engine for Windows and Mac OS X that lets you run little files called Widgets that can do pretty much whatever you want them to.

Widgets can be alarm clocks, calculators, can tell you your WiFi signal strength, will fetch the latest stock quotes for your preferred symbols, and even give your current local weather.

What sets Yahoo! Widget Engine for Mac apart from other scripting applications is that it takes full advantage of today's advanced graphics. This allows Widgets to blend fluidly into your desktop without the constraints of traditional window borders.

Toss in some sliding and fading, and these little guys are right at home in Mac OS X and Windows.

The format for these Widgets is completely open and easy to learn so creating your own Widgets is an extremely easy task.

For the "skinning" crowd, Yahoo! Widget Engine is a dream come true. You can easily change the look, feel, layout, even functionality of a Widget so that it matches your lifestyle, your desktop, or the pants or skirt you have on that day.

Requirements:

· A connection to the Internet.
· 512 megabytes of RAM

What's New in This Release: [ read full changelog ]

Fixes:
· Implemented text speedup for Mac.
· Fixed event.key
· Added support for numlock modifier on keyboard, mouse, and drag events
· map the window levels correctly (mac only)
· Added timeout property to XHR.
· Added JSON object (from json.org).
· Leopard support
· Fix issue with unlocalized "Preferences" submenu in system tray.
· Allow CSS to affect text alignment even in non-wrapped text objects. Only works with a minimum version of 4.5 or later.
· Fix issue where saveImageToFile() couldn't deal with scrolled frames.
· Fix localization of preferences dialog title.
· Fix localization of dialog title when iTunes is not installed.
· FINALLY support ctrl-a and ctrl-e in the evaluation field in the debug window on Windows.
· Always set system.event when minVersion >= 4.5. system.event is, however, considered deprecated. You should always use the event passed to your handlers.
· Implement URL properties to expose a URL 'cracking' API, i.e. you can access the components of a URL.
· Get Drag/Drop worki...