Forgot your password?
typodupeerror

Comment: The usage is also different (Score 1) 220

by rannala (#29767621) Attached to: The Sad State of the Mobile Web

There a definite gap between the experiences, but use cases are usually a bit different, too. Mobile devices are mostly used to check something up quickly on-the-fly as on PC you also do more planning ahead. So a scaled down experience is not necessarily a bad thing on mobile as that eases the pain of having a small screen, slow text input and possibly moving around in a noisy environment. Scaling down the features also forces the development team to focus on the essentials, which is not a bad thing even on PC.

Then again, it would be nice to get Slashdot css working on small screens, too.

Comment: Re:Job's got it right.... (Score 1) 309

by rannala (#27460829) Attached to: Three Mile Island Memories

I bleme the belief that the goal of an UI is to lower the required understanding (and thus salary) of the operators. How the UI worked is irrelevant. Operators who understood what they were doing would have checked what needed to be checked, and taken the precautions the situation warranted, no matter what kind of warnings were lost because of a bad UI.

In an enviroment like this you really need both, trained personnel and a decent UI. The goal of the UI should not be to reduce understanding and cost, but to support the people making the decisions with the best information available. Even the most talented professionals can only make educated guesses if they have no situational information whatsoever and the only feedback is boom/no boom.

The problem is that Nature is a whole lot better of churning out interface-proof idiots than programmers are at making idiot-proof interfaces.

And that is exactly why you don't use programmers to design a UI.

Image

Using Drupal 122 Screenshot-sm

Posted by samzenpus
from the read-all-about-it dept.
Michael J. Ross writes "After installing and learning the basics of the content management system Drupal, many Web developers do not know how to best proceed from there. They may realize that much of the programming potential of Drupal — and thus the earning potential of Drupal developers — is derived from the use of community-contributed modules that greatly extend Drupal's power. But there are thousands of such modules, with no objective direction as to which ones are best suited for particular tasks, and what bugs and other flaws could trip up the developer. These programmers need a thorough guide as to which modules are the most promising for the development of the most common types of Web sites. A new book, Using Drupal, aims to fill this need." Keep reading for the rest of Michael's review.

Pause for storage relocation.

Working...