Tivo To Go
Margret Sloan writes in her blog that TivoToGo is up and running and allows Tivo users to use the service for free and its available for both Mac and Windows computers and works with several portable devices including the PSP. To get your Tivoed programs on your mobile do the following:
First, transfer recordings to your desktop or laptop.
Consider it in-flight entertainment. After you have downloaded and installed the TiVo Desktop software, you can begin sending shows to a networked computer in another room of the house or any wireless laptop. Then, transfer a selection of your TiVo favorites and you are off.
Then, save recordings to your mobile device
Once the programs are transferred to a computer, the TiVoToGo software can encode them for a compatible handheld device. You can even schedule recordings and instruct the TiVoToGo software to automatically transfer new shows when they become available.
Yahoo Gallery Beta
“Your invited to join Yahoo Gallery it allows developers to discover and share applications that use Yahoo technology this is just in Beta but you can get your own developers page and anyone familiar with Yahoo services or products should have no problem making all sorts of programs for gadgets and widgets. It also allows you the rate other peoples apps. And if you know of any other developers out there let them know would yea it is totally free”
A BIG thanks to Selena Jackson for the invite
Widgetbox is a directory and syndication platform for web widgets for blogs and other web pages. Thier widgets work with TypePad, WordPress, Blogger, MySpace as well as most other blogs, sidebars or websites. No plug-ins are needed, and they’re free! A great way syndicate your blog to the masses and then ofcourse you can submit your widget to places like Yahoo Widgets and because it is a widget it’s a great way to keep up with any feed on your mobile device and other people can keep up with your feed on thiers.
From the W3 QA Blog
Nothing is perfect (and that is why we have QA) by Olivier
“The way a bug was found and fixed in the Feed Validator is not disturbing, I actually think it was an inspiring proof that all the aspects of its QA process worked:
- There is a public feedback channel (several, indeed) for a problem to be reported to: Brian sent a message to the W3C QA mailing-list, asking whether someone could make sense of the problem he was facing
- The tool is implementing public specifications: I was able to look at the RSS taxonomy module spec, and compare its prose with the implementation in the Feed validator
- The validator is open source: 10 minutes of browsing around clear code was enough to find the issue, and create a patch, which was promptly reviewed and applied by Sam Ruby, one of the maintainers of the validator.
- There is a test suite, to which I submitted a revised test case: now that the bug is fixed, we know that it will never appear again without being spotted automatically.
Time between original feedback and applied patch: about 24 hours.
There is nothing shocking about this bug, but the speed at which it was processed and fixed. Maybe that was lucky, I just happened to have a bit of time to look at the issue and the bug was easy to fix. Other, more complex bugs in tools that we (W3C’s QA Tools development effort) maintain are not so lucky, and indeed Brian is right in pointing out that we could use more help and resources to make our tools better. But I can not agree with his slightly provocative title that
Validators Donâ€™t Always Work. The Feed validator works, and so does its Quality Assurance process, as demonstrated in the prompt fixing of a small bug in its implementation of a faulty, not widely used specification.
Validators are extremely important tools for the adoption of technologies, and it is perfectly normal to be concerned about their quality. This is why finding bugs is good news, and the best use of one’s energy is not to worry about them, but to help find them, report them, patch them and build regression test cases for them.
Nothing and noone is perfect, that’s why we have QA.”
This was a great example of how things have changed for the better and evolved over time at the W3C when handling issues and bugs but I would also like to stress that there was nothing wrong with the way otherÂbugs and issues were handled in the past.
Widgets 1.0 Requirements: Working Draft
From the W3C News
“The Web Application Formats Working Group has released an updated Working Draft of Widgets 1.0 Requirements. These design goals are the requirements for device-independent standards for scripting, digitally signing, securing, packaging and deploying client-side Web applications (widgets). Also known as gadgets or modules, widgets are small programs like clocks, stock tickers, news casters, games and weather forecasters that display and update remote data and run on the Web browser environment. Read about Rich Web Clients.”
They have a really great graphic on the W3C web site showing the inner workings of a widget, which is really cool.