Sunday, December 15, 2002

CSS-D Finds New Home at evolt.org

The incredibly popular, active, and valuable mailing list devoted to Cascading Style Sheets, CSS-Discuss (css-d), has moved its hosting to evolt.org. After some brief list overlap, and a lot of server tweaking, the list opened its doors to its new home Monday, December 9.

Started and moderated by Eric Meyer, author of four books on CSS, css-d quickly grew to 2,500+ members and more than 50 messages a day. This load began to tax the hosting resources Eric had in place in the beginning, and so he began a search in early November to look for a new home.

The evolt.org UK branch, evolt.org.uk was kind enough to offer server space and bandwidth, thanks to the efforts of Lachlan Cannon and John Handelaar. In particular, John had to wrestle with a particularly ornery Cobalt Raq configuration in the time-honored tradition of trying random stuff until it worked.

Advantages of the move include more control over mailing list features for the administrator, the ability to have a css-discuss domain as the list address, and, ideally, resolution of problems with members getting multiples of multiple messages. Bringing the old list archive over is just a matter of time.

The css-d mailing list is devoted to the discussion of CSS and its real-world applications. Theory is sometimes discussed, but for the most part, it's a list for practical and daily use of CSS in projects. Find out more about css-d and sign up for the mailing list at its new home, css-discuss.org.

Thursday, June 20, 2002

Book Review: Usable Web Menus

From the Publisher

Title: Usable Web Menus Authors: Andy Beaumont, Dave Gibbons, Jody Kerr, Jon Stephens ISBN: 1904151027 Publisher: glasshaus Price: US$ 13.99 at Amazon.com Page Count: 200 Publication Date: March 2002

When developing a web site, one of the most important things to consider is the navigation menu, to allow your users to find their way around it. It needs to usable, informative, and well implemented, but this can take time. This book will take all the hassle out of implementing web menus, in whatever style and technology you wish, by providing full code samples, along with walkthrough tutorials on how they work to allow easy customisation for your own needs.
This book covers the design and implementation of navigation menus using JavaScript and CSS (DHTML), and Flash on the client-side. Later chapters look at dynamically populating these menus from server-side data sources (databases and XML) using middleware (such as ASP and PHP).

Chapter 1: Rules for Good Menu Design

This first chapter is written by Dave Gibbons, and attempts to frame usability issues for web-based menus. While the book tries to avoid overly-technical, or even preachy, explanations of usability rules, this chapter glosses over some key rules of interface design. Since this topic is only afforded the space of one chapter, however, there's not a lot of room to go into great detail.

Instead, the author presents 12 rules of menu design and goes into some detail on each, often with examples. The bad examples aren't given enough detail to explain why they are bad, however, and the author makes some assertions that would be more valuable with supporting evidence of any kind. I'm also not sure the author understands all the factors behind building accessible sites, primarily because he implies XML/XSL(T) sites will enjoy greater accessibility, which isn't necessarily true. He does, however, provide links to the WAI and a page on Section 508.

Overall, this chapter is good, if a bit generalized.

Chapter 2: Information Architecture for Menus

Also written by Dave Gibbons, this chapter addresses information architecture, as well determining and testing your audience. There is a good series of questions for identifying the users by their needs, goals, and available technology. Given what you've learned about your users, it further addresses how best to present the information to those users so it makes sense and speeds their access to the information they want. User testing is only allotted one page, but it is at least addressed in here.

And this is where the handy introduction to usability and information architecture abruptly ends.

Chapter 3: Basic JavaScript Menus

Authored by John Stephens, this is the one chapter that I would actually like to see removed from the book. It starts off simply enough, but starts to quickly gather momentum as it tumbles away from all the usability and accessibility suggestions presented up until now.

Starting off with a brief introduction to CSS and JavaScript, simple image rollovers are presented, followed by the use of the :hover pseudo-class. This is even a JavaScript powered menu that disables the navigation for the page the user is currently viewing, a potentially handy script for developers who don't have access to a server-side scripting language and don't want to customize the navigation for every page on the site.

After this, the author presents navigation menus based on form elements. The first example uses buttons, although instead of using <input type="submit">, the author chooses to use <input type="button"> and fires each using an onclick event handler. The <form> tag has no action attribute. Users without JavaScript enabled are thus penalized since the navigation menu will completely fail to work. In addition, there is no discussion about the implications of form elements acting as navigation elements.

Continuing the descent, the author provides samples of navigation menus based on checkboxes and then radio buttons, both of which introduce a host of usability concerns (smaller hit states, checkboxes imply more than one option, JavaScript-only, etc.). In fact, the only interface issue the author points out is how Netscape Navigator 4.x displays incorrect background colors on radio buttons in tables. Hell, even using a <label> element on the options would have at least indicated that the author cared somewhat about the user instead of flexing his simplified JavaScript muscles.

Following up to these two examples is a select-menu based navigation. This might not be so bad only because so many people use them, if not for the known usability issues, and the author suggesting that the current page be hidden from the options, preventing any type of user memory on the location of options in the menu (what he refers to as a "jump menu with intelligence"). He closes the chapter with a double-jump menu, allowing users to select an option in one select box, only to have to then select an option in a second select box.

Given that the title of this book is Usable Web Menus, there's really no reason this chapter should have been included, at least not without caveats every page.

Chapter 4: Menus with Advanced Scripting and DHTML

John Stephens continues with a slightly more practical chapter, only because it has a useful JavaScript cookie functions, in case you don't already have one in your library. The chapter continues to make gratuitous use of JavaScript to create a style switcher powered with a pop-up window (a pop-up window killer might kill it, though). In its defense, it does present the code necessary to allow Netscape 6 to natively allow the user to switch between style sheets.

The chapter then spends an inordinate amount of time working with image maps, something which was generally unnecessary in the context provided, and didn't do a remarkable job of showing advanced scripting, as the chapter title promises. Eventually, an image map displayed in a <div> that can be hidden by the user was presented, although its usability benefits, if any, were not addressed.

The last pair of examples showed a menu loosely based on the Windows95 Explorer folder pane interface, and offered some useful blocks of code to hide and show menu elements.

Chapter 5: Flash Menus

Penned by Andy Beaumont, this chapter offers a refreshing break. This author knows about the stigma Flash has for usability and accessibility, and creates examples that don't suffer as most Flash-based navigation does. Although the author doesn't specify the version used to create the examples, Flash 5 appears to be the culprit.

The chapter starts off showing how to create, via movie clips and ActionScript, basic menus from a hard-coded list. The example is built upon to show how to feed the menus with XML, and then how to feed the XML from a PHP/MySQL setup. The code downloads on the glasshaus site also offer an ASP/MSSQL version, even though the book doesn't go into it at all.

For some reason, though, the author modifies his XML from the second example to the third, forcing a minor re-write to the XML-parsing ActionScript. Otherwise, the chapter has a number of useful tips. It does not, however, delve any deeper into usability issues beyond the token page at the beginning of the chapter, let alone those related to the specific menu sample.

Chapter 6: Dynamic Server-Side Menus

This final chapter, authored by Jon Stephens and Jody Kerr, finally addresses a menu other than a basic navigation menu by giving an example of a breadcrumb trail. While the trail may be unnecessarily encased in a multi-cell table, it's shown with a PHP/MySQL, ASP/MSSQL, and ASP/XML implementation, allowing many readers to benefit from it. The chapter goes into some detail on PHP and MySQL, while deferring to Microsoft on ASP and SQL Server.

After the breadcrumb trail example, the final menu example from chapter 4 (the Explorer-style menu) is brought back, and the reader is shown how to populate the JavaScript with some of the server-side language presented earlier in the chapter.

Resources

There were as many references for ASP, PHP, or JavaScript as there were for usability at the end of the book. If anything this is evidence that the book is far more code-oriented than anything else, and that usability isn't given the priority its title implies.

Recommendation

All the code samples in the book are targeted for Microsoft Internet Explorer 4.x+, Netscape Navigator 4.x, Netscape 6.x, and Opera 5.x+ for Windows, and Internet Explorer 4.x+, Netscape 6.x+, and Opera 5.x+ for the Mac.

For a book on menus that are supposed to be usable, I was disappointed at how usability factors were discussed only at the beginning, as opposed to within each example as an exploration of the value of each suggested menu. Chapter 3 really brought this to an extreme by presenting menus that younger developers, assuming books know best, might blindly use without regard to their impact simply because they are in a book on usable menus.

The code examples are generally good, and handy references for younger developers. It's nice to see Flash represented, even if only in passing. For the price, it's not a bad book to have on the shelves for reference, but it's not one I would run out and buy.

And one minor peeve — alt is an attribute, not a tag.

Wednesday, June 5, 2002

Mozilla 1.0, Right on Time

Mozilla.org has officially released the 1.0 version of Mozilla, which, of course, includes the Gecko rendering engine.

Since 1998, when Netscape opened up the source code to allow development of a new browser, through the aquisition of Netscape by AOL in 1999, followed by the release of Netscape 6.0 (built on beta versions of Mozilla) two and a half years after the Mozilla project was launched, the entire project has been alternately assaulted for taking way too long and being too buggy and praised for holding up standards and open source as an ideal.

Most recently, AOL released the first Netscape 7 Preview Release (no telling how many more there may be), although that happened before the release of Mozilla 1.0. Most likely, the final 7.0 release will be based on Mozilla 1.0.

Of course, with AOL now testing Netscape in CompuServe, threatening to deploy it to the AOL service, and given that Mozilla is open source, it will be interesting to see how this release impacts the suit AOL Time Warner has filed against Microsoft for strong-arm browser practices. While this release itself isn't going to change the state of the browser wars overnight, it's an awfully big symbol to be held up in court.

Check out some of the articles on Mozilla here at evolt.org.

Features

The following is pulled from a release over on MozillaZine.org that trumpets the arrival of Mozilla 1.0. After all, they say it better than I.

Mozilla 1.0 features full support for HTML 4.0, XML 1.0, Resource Description Framework (RDF), Cascading Style Sheets level 1 (CSS1), and the W3C Document Object Model level 1 (DOM1). Mozilla 1.0 also has the industry's best support for Cascading Style Sheets Level 2 (CSS2), the Document Object Model Level 2 (DOM2), and XHTML. Standards support also includes XML data exchange and manipulation of XML documents with SOAP 1.1, XSLT, XPath 1.0, and FIXptr, as well as support for display of mathematical equations using MathML. Finally, it features a solid foundation of support for data transport protocols (HTTP, FTP, and SSL/TLS), multilingual character data (Unicode), graphics (GIF, JPEG, PNG and MNG) and the latest version of the world's most popular scripting language, JavaScript 1.5.
Further, Mozilla has been designed for easy localization into languages other than English, and localized versions of Mozilla 1.0 will be available in the following languages (with more to follow): Asturian, Chinese, Dutch, Estonian, Galician, German, Georgian, Greek, Hungarian, Italian, Japanese, Malay, Polish, Slovak, Serbian and Ukrainian.

Platforms

Mozilla 1.0 is available for the following platforms, so go try to download it over there:

  • Win32
  • MacOS 8.5, 8.6, 9.x
  • MacOS X
  • Linux
  • BSD/OS (bsdi)
  • FreeBSD
  • OpenVMS
  • OS/2
  • Tru64 Unix

Ports are in the works for the following platforms:

  • MacOS X using Carbon instad of Cocoa
  • BeOS
  • Irix
  • The Qt toolkit, a Unix front-end
  • A pure Java version
  • Amiga DE (Digital Environment)
  • Acorn RISC OS

Future

I'm taking bets on when the 1.1 release comes out...

Tuesday, June 4, 2002

Nielsen Snipes E-comm Sites, Teams with Macromedia

Jakob Nielsen, in a busy week, releases a report criticizing e-commerce sites, and teams up with Macromedia to help them make Flash 99% less bad.

E-commerce Is 51% Bad

The first report, from News.com, describes a study released by the Nielsen Norman Group. The study claims that, from a field of 15 e-commerce sites, in total they met 49 percent of the usability guidelines developed by Nielsen's consulting company.

The L.L. Bean web site scored highest by meeting 66 percent of the guidelines, while Home & Garden had the lowest score, meeting only 38 percent of the guidelines. Amazon.com was left out of the survey, for reasons unknown, even though it ranked in first place two years ago.

Flash May Become 99% Somewhat Bad

Also this week, as covered at News.com, Macromedia and Nielsen announced that they would team up to create usability guidelines that can take advantage of the UI improvements offered in Flash MX. Of course, these are just guidelines, and there's no guarantee they'll be followed by anyone, but there is at least acknowledgment from Macromedia that improvements can be made in Flash.

Some of us here should be familiar with Nielsen's article, Flash: 99% Bad, written way back in October of 2000. Well, as of June 3, it's been updated with a sub-heading, Flash Now Improved, even though NNGroup hasn't actually started working on Flash yet.

Macromedia also has a press release on their site.

Other Reading

Sunday, April 7, 2002

Overture Sues Google

Overture (formerly Goto.com) filed suit against Google late Thursday in U.S. District Court in Los Angeles. The lawsuit only applies to the paid listings portion of the Google search engine, not its general search engine.

Google has no press releases related to this case, but a Google spokesman claims that they have analyzed the patent Overture cites in its lawsuit, and there is no infringement. Overture says the following about the lawsuit in a press release posted to its site:

The lawsuit charges Google with infringement of Overture's U.S. Patent No. 6,269,361. The '361 Patent protects various features and innovations relating to bid-for-placement products and Overture's Pay-For-Performance search technologies including its DirecTraffic Center account management system and tools.

Google took Overture's spot as the paid search service for Earthlink in February, and Overture is still trying to hammer out an overdue contract to continue services with AOL while AOL's sibling, CompuServe, started using Google in conjunction with Overture. Overture's paid listings appear on several search engines, including Yahoo! and AltaVista.

Overture filed a similar lawsuit against FindWhat.com in January (not that I can find any more about it). Also in January, a diet product manufacturer filed suit against AltaVista, Kanoodle, FindWhat.com, and Overture for alleged bait-and-switch tactics.

More information:

Saturday, March 23, 2002

Say Goodbye to Free Email

Both Hotmail and Yahoo have announced this week that people who want to continue to use some of their services will have to pay.

Yahoo announced on Thursday that it will begin charging for POP3 mail forwarding services. Yahoo originally started charging for some services back in February of 1999, and has continued over the past year to charge for services that are expensive to run. Beginning April 24, the mail forwarding service will cost users $29.99 per year, but those who subscribe before then will pay $19.99 for the first year.

Users who pay the fee will be able to use their Yahoo account as a POP3 mailbox, will be able to send attachments of up to 5 megabytes (instead of the current 1.5MB limit), and will not have the Yahoo text advertisement attached to the foot of every message. There will also be extra storage fees of $24.95 per year for 50MB, and $34.95 per year for 100MB, although users can pay monthly at $2.95 or $4.95, respectively.

Microsoft's Hotmail has taken a slightly different approach. Users who approach the 2MB limit, or don't regularly use the account, may find their inboxes cleared and their account bounces messages. Users are being pushed to upgrade to ensure their mail won't be wiped for inactivity or due to larger file sizes, while they are also being marketed the benefits of the Passport service and other internet services, such as MSN.

Last fall, Hotmail started closing accounts if inactive for 30 days, down from its 45 day policy. Over the summer, Hotmail offered storage space over the free 2MB at a price of $12.95, but raised it to $19.95 by December. Hotmail claims that first trash, then junk mail, then sent folders are cleaned before inboxes, although some users have reported the opposite has occurred. Some users argue that Hotmail has caused people to reach their file size limits by selling their information to spammers.

Recent news pieces:

Monday, March 18, 2002

End of the Free Content Ride?

With the boon of the web a few years ago, sites competed with one another by acting like portals, trying to see who could post the most news and otherwise free content possible to keep people coming back. As the portal model has fallen away, and the 'net economy has tightened up, it seems some formerly free sources of information are starting to expect something in return.

Jupiter Media Metrix claims that 42% of online adults are willing to pay for content, down from 45% in August of 2000. However, there are some murmurings that the industry might be moving away from free content regardless.

CNN's decision to phase out free video clips on its new, sports, and financial sites is just one example, following ABC News' example. RealNetworks is selling a SuperPass with a monthly price tag that allows access to multimedia from ABC News, Fox Sports, NASCAR, and even pro baseball and basketball, and they've already garnered some 500,000 subscribers. Salon magazine made that move last year, moving much of its content to a premium service.

Jupiter's report suggests that paid online content will grow to a $5.8 billion industry by 2006, up from $1.4 billion in 2002. They attribute the expected growth to widespread access to broadband, as well as people just buying into the model of paying for much of their content online.

Of course, free doesn't always mean money. More and more sites are requiring registration to access content, making users decide if their personal information is a fair trade. This customer information is a form of currency you can see in places like download.com, where they now require registration to download software.

Recent news pieces:

Sunday, March 17, 2002

Is Netscape the Browser for the Next AOL?

There have been many rumors on developer forums over the last week or so that AOL is testing Netscape in the AOL software. They've all been just rumors until recently, when some news sites have posted quotes from real, live AOL representatives.

AOL spokesman Jim Whitney confirmed on Thursday that a beta version of CompuServe has shipped with Netscape as the browser, and that they've been testing it since the fall. He also stated that they'll be testing Netscape with the AOL service as well, which has a worldwide customer base of 34 million users. AOL 8.0, due to ship in the fall, is likely the earliest version of the AOL service that could integrate Netscape.

With AOL's purchase of Netscape in 1999, and with AOL letting its agreement with Microsoft to use Internet Explorer as the browser of choice expire in January of 2001, some feel it's just been a matter of time before AOL would start to roll Netscape out as the default browser for the AOL service. Microsoft isn't so convinced AOL will move its user-base away from Internet Explorer given that AOL has been threatening it for years but hasn't yet moved. This, of course, ignores the January lawsuit AOL filed against Microsoft. Microsoft spokesman Jim Cullinan said, "AOL has had the ability to change browsers since they purchased Netscape back in 1998, so it's not surprising that they might make that decision. But Internet Explorer is by far the best technology because it provides users the best experience on the Internet. But the decision remains AOL's."

Jupiter Media Metrix analyst David Card walks away with the best quote to date, when commenting on whether or not AOL would really make the shift to Netscape from Internet Explorer: "Serious software companies don't ship open source. They may start with it but they build products on it. You just have to be serious about the business and I don't think they are serious (about Netscape)."

Some news bits:

Track new links in the comments below, I think we'd all like to see the progression of this story.

Tuesday, January 22, 2002

Amazon Out of the Woods?

Back on January 21, Amazon had expected to report its first profit — a pro forma profit that would exclude many costs included in regular accounting and is often seen as a controversial method of creating good news where there may be none. Amazon has maintained that pro forma accounting is more appropriate for its business model.

However, Amazon posted a $5 million (1 cent per share) profit the very next day using standard accounting methods. Amazon used GAAP (Generally Accepted Accounting Principles), which is considered quite an accomplishment for a company often viewed as the poster boy for creative accounting.

Wall Street tracking firm Thomson Financial/First Call had expected Amazon to post a pro forma net loss of between 4 and 8 cents a share, compared to a loss of 25 cents a share ($90 million, pro forma) a year ago. Amazon's GAAP losses last year were $545 million, or $1.53 per share.

Amazon was able to cut its operating costs in half this past quarter, which allowed for lower prices on core products, resulting in higher sales volume. Free shipping on orders over $99 (originally a holiday special, but permanent as of today) as well as bundled products are credited with some of that volume, according to Bezos. Licensing its e-commerce package to Target and Toys R Us probably hasn't hurt, either. International sales were up 81% from last year, with the Germany and United Kingdom offices breaking even.

Amazon is still in debt to the tune of $2.2 billion ($120 million a year in interest alone), although that debt does not come due until 2008. Amazon is projecting first quarter sales between $775 million and $825 million, with $810 million in liabilities in the fourth quarter, meaning that profit is already earmarked and unable to pay down its debt.

Related Links