Blaze Blog

Archive For: Browsers

Mar28

Adobe Device Central

Despite the fact even the “Design Standard” version of CS3 is going to give my wallet a considerable beating, I’m intrigued by one particular part of the package.

Device Central Screen

Adobe Device Central looks cool, very cool. I’ve not tried it in the public beta of Photoshop, which I now read has a beta version of it included.

I’ve had a bunch of clients recently ask for handheld stylesheets and thankfully I’ve had a Windows Mobile device on hand to test them out. I’m about to sell it though, and even with an actual device, I’m still limiting myself to one platform.

Has anyone spent time using this tool? If so, how have you found it so far? It looks great, but who knows how it will actually work until I get a *final* copy of it.

Come to think of it, maybe this is just for flash mobile… I really hope not, but I suppose that would make sense.

Aug3

Multiple Backgrounds in Safari

By Andy in Apple, Browsers, News

Chief Safari developer David Hyatt revealed this week that both Safari 1.3 and 2.0 have the capacity to support multiple background images for a single element.

This comes after this post from the CSS working group, asking for input into the CSS3 ‘Borders and Backgrounds’ module.

Dave goes onto say that this gives developers a chance to play with the syntax for multiple backgrounds, and then give better more constructive feedback on the working group’s request.

If you’re using Safari 1.3 or 2.0 then check out this test site for a demo of multiple backgrounds in use.

Great work David.

May11

W3C’s Mobile Web Initiative

The W3C has announced that they are starting the Mobile Web Initiative, which aims at “concentrating on the application of existing recommendations for mobile content”.

This is good news, no doubt this new initiative will move the mobile web forward, something that’s needed to be done for some time now. Not only that, they have some solid support from current cell providers like Vodafone and France Telecom. Not to mention Hewlett Packard.

I can see this moving forward very fast, I guess it’s in everyones interest. Due to the big financial backing, and huge practical implications, there’s obviously some money to be made through the mobile web.

Jan15

The Wrong Approach To Handhelds?

Last week I received my brand new PDA/Cell phone hybrid and have been playing with it non-stop since.

Along with it I bought a SD memory and Wi-Fi combo card, so that I could walk around my house surfing at broadband speeds.

Anyway, the screen is small. Smaller in fact than any other fully-fledged PDA on the market (320×240) but this is something that attracted me, I didn’t want to carry a phone the size of a house around with me all day.

One of the first things I did once I had everything set up was to check this website to see how it rendered on the small screen. The answer? Surprisingly well in fact, using the built in slim line Internet Explorer, I could barely see any faults with the site below the navigation area, which was the one part that didn’t seem to sit in the right place.

Even though it rendered well, reading any of the articles on such a thin screen was tedious, even when Internet Explorer’s ‘one column’ mode was turned on.

So the obvious answer was a simple handheld stylesheet, I’ll add the line of code into the header, turn all the background images off, as well unset heights and widths and finally make the text a little smaller. Easy stuff.

How wrong I was. I should have been clever and remembered the excellent article by Doug Bowman on this subject a few weeks back.

Most Pocket PC browsers at the current stage render your screen stylesheet as well as your handheld one. Now of course this is ridiculous – it means if you want to slim everything down for a PDA, you need to copy all of your screen stylesheet into your handheld one, then go through and over-ride all the key properties one by one.

Another View

Why would they do this? Well, I have one pretty good idea. Companies want to make your PDA as much like your computer as they can.

Lots of PDA’s have Wi-Fi, feeding them broadband connection speeds. Who wants to browse black and white text based sites with minimal images? Can you imagine the average user booting up their PDA, then surfing their favorite sites to find they are all slimmed down and only have the basic functionality?

I can see this as a valid point. Perhaps it may be too early for developers to adopt the handheld stylesheet. Right now most designers would just reduce their site down as simple as it will go.

However, maybe we are taking the wrong approach? What if designers were to come up with some beautiful handheld designs for their site, to see the small screen as benefit not a burden?

Most of the arguments against this idea have been lifted in the past couple of years. Screens on PDA’s and new cell phones have become as crisp and vibrant as your average TFT monitor. The support for standards on PDA browsers is surprisingly good. Browsers on cell phones can still be shaky, but these are improving very rapidly due to the speed at which the cell phone market moves forward. Bandwidth is also a major issue, but the take up of Wi-Fi has helped improve this, and most cell phone operators offer GPRS which gives slightly faster than dialup speeds. Dare I mention 3G?

This doesn’t of course give the creators of handheld browsers the right to render your screen stylesheet. By doing this they are going against standards and are causing many headaches in the short term.

However, in my view the only way that we are going to get this to change is to adopt the small screen as a challenge, to move forward and create, rather than stepping back and giving handheld browsers the web of ‘94.

Oct12

CSS for the Mobile World

I have been the proud owner of a brand spanking new Orange SPV C500 cell phone for about 3 weeks now, and I have been very impressed by its mobile internet capabilities.

Orange SPV C500The C500 is a mobile smart phone. It comes installed with Windows Mobile 2003, which includes programs like Windows Media Player, MSN Messenger, Internet Explorer, but most importantly lets you install third party applications just like any other version of the Windows software.

After researching mobile browser applications I found that a small browser called ThunderHawk was by far the best. It had an impressive list of standards support and was fully compatible with CSS1 and most of CSS2.

I installed the browser onto my phone and decided to test a well known CSS based website, that of Dave Shea’s Mezzoblue.

Mezzoblue on ThunderHawk full screen viewMezzoblue on ThunderHawk split screen view

I was amazed by the results. Apart from some minor element sizing problems, the site’’s CSS was rendered almost perfectly by ThunderHawk, which by default includes a ‘split-screen’ feature that allows you to see how the site would look on a regular desktop monitor, but also save a section of the screen for you to zoom in and actually read the content. This can be turned off if required, leaving you with the whole screen to scroll around in, just as though you were viewing it on a regular sized screen.

ThunderHawk also overrides your style sheet’s font settings. Instead it uses its own built in font which renders well at a very small size – allowing for more information to fit onto the screen, minimizing the need to scroll.

Cell phone browsers are obviously still in their infant stages, but with new browser releases on the horizon, things are only going to improve. Soon it may be far easier that you ever thought to catch up on your daily visits.