The 'theory' has some merit. The webclip demonstrations, AFAIK, have hitherto only been shown using live, online webpages, not locally stored html files, which I think is the simple point Rob (and the OP) is endeavoring to make.

So, to reiterate the value of this theory/hint; In addition to creating webclip widgets from an online website, as demonstrated many times since Leopard's unveiling, you can also create or acquire scripts & code snippets, wrap them in html tags, store them locally, load them up in Safari, then quickly & easily create widgets from them using webclip - all without having to delve into Dashcode to create a widget from scratch.

Certainly, this is probably pretty obvious to some people, yet it's not something that ever really crossed my mind.

Back to the actual hint, it is worth noting that you must retain the source files for your widget to function. That is, you cannot make your source file, create a webclip widget from it, then trash the source. Webclip does not embed the source code into a newly created widget, it merely acts as a miniature browser window. Again, probably obvious, but a worthy disclaimer.

[ Reply to This | # ]