Category: Web Standards

Private Messages

Does anyone remember the evolution of private messages? When computers first came out, the internet was not something intended for home and personal use. It was for businesses. When we started bringing computers home and using them to communicate with friends and family, the demand for private messages began. I remember when Yahoo introduced their “Yahoo Instant Messenger” as part of their platform. I used it extensively during competitive gaming and forums. I liked the way you could get a response to your question quickly, plus you could find out quickly if someone was even online at the time or not. Come to think of it, I still use the Facebook private messaging system for the same thing.

Google Developer Day May 31 2007

Google Developer Day: Building blocks for better web applications

From Googles website

At Google, we want to help developers build better web applications. That’s why we have created APIs and tools to quickly enhance those applications, integrate with Google products and reach millions of users.

That is also why we are holding Google Developer Day.

Google Developer Day is a chance for programmers around the world to meet Googles developer product teams and learn something new be it an introduction to GData or a deep dive into KML. Its also an opportunity for us to listen to you and hear about what youre doing today, what you would like to do in the future and how we can help make that happen.

Whether you are writing an AJAX application with the Google Web Toolkit, integrating Google services through GData or using Google Maps to create geo applications, we hope you will leave Google Developer Day with a new set of building blocks to use in your next project.

Nothing is perfect (and that is why we have QA)

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:

  1. 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
  2. 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
  3. 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.
  4. 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.”

From Alice

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

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.

Studio 8

Studio 8

Have been using Macromedia software to make my websites since as long as I can remember. Was a little tiffed when I read the headline stating they had sold out to Adobe. I had hoped Google would have bought them and gave away the software for free, not that I do no think it is not worth every penny if not double it’s going rate, but I wanted the world to be able to use the best web authoring software in the universe so the web would be a better place. One of the programs I love in the Studio 8 package is Flash Professional 8 it has so many features and works well with other programs like Swishmax. For making mobile web applications like games websites and animations and a ton of other great things but that is what I use it mostly for and reccommend anyone looking to start amking mobile content to check out this software first before buying or even trying another program.

WordPress Themes