HomeBlogCategory: “web design”

Showing only posts in category “web design”.

Show all


Google Browser

Google launched yesterday “Google Chrome”, their revolutionary (no bullshit) Web browser.  I played with it a little.  It's amazing how well they did it!

It's incredibly fast, it has a nice and clean user interface, it knows most keybindings (which I couldn't live without) from Firefox.  It has a wonderful start page which shows thumbnails to the 9 most visited sites in your history.  But if you want to view pages that you don't want to show up there, you can turn on the “incognito” mode.  It runs one separate process per tab (I'll never understand why other browser makers didn't think about this) which means that even if a tab crashes, the others will stay up.  It also means that you can run some computationally intensive stuff in a tab without affecting the whole browser.  And did I say it's fast?

[ read more ]


DynarchLIB release

I finally released probably the biggest projects that I've independently worked on.  DynarchLIB is a fully-fledged user interface toolkit for development of Web applications.  It contains a rich set of widgets, a consistent object/event system, browser-server communication helpers, various JavaScript extensions, etc.  Worths checking it out. ;-)

Also see the Dynarch online chess, currently the first public application based on this toolkit.

PS: the administration frontend of this very site is based on DynarchLIB as well. ;-)


Firefox slowness identified

I talked previously about the Firefox problems on Linux, however, I now identified a case that can reproduce the slowdowns.  It happens when you have a lot of text in some element.  Even if that element is displayed with overflow: auto, or overflow: hidden, it'll be slow as hell to drag'n'drop it.  Additionally, all operations seem to be a lot slower in the whole page (that is, even if they don't directly affect that element).

Here is a demo that shows the problems.  If you're running Firefox on Linux the poor performance should be easy to see; if you're on Windows, use more lorem ipsum. ;-)

If you have any idea how to work around this issue, I would love to know it—please share your thoughts by commenting in this page.

The fastest browser on Earth

I never thought I'd say this, but here I go: Safari is the damn fastest (modern) browser on the planet.  Nope, it's not Opera, not Firefox and definitely not IE.

I'm playing with Safari 3.0.4 on Windows and it simply rocks.  The rendering engine is quite good as well—I'm doing pretty heavy AJAX stuff and there was no special hack I had to do for Safari.  So let me congratulate the WebKit team for this fine product! (I still can't forgive Apple for using KHTML instead of Gecko; Gecko is better, it just needs to catch up with performance and it looks like this is going to happen in the next release).

Filed in: browsers, firefox, safari, web designNo comments

ExternalInterface is unreliable

“What are you supposed to do if you're the chef at Les Halles
and your fishmonger is giving you smelly fish?”

Joel Spolsky

So while playing with ExternalInterface I found quite a big problem with it.  It's serious enough to call it “unreliable” because it mangles your data in strange and undocumented ways.  Here's a quick Flash applet to demonstrate that:

( read more... )

Filed in: flash, javascript, programming, web design7 comments

Apple Safari for Windows

So, Apple released a few days ago Safari 3.0 Beta, which is available both for Windows and Mac OS X.  They say the Windows requirements are “Windows XP or Vista”, but a friend of mine has it running on Windows 2000 with no problems.

First impressions: crash, crash, crash

I installed it on my Windows XP machine, which has IE7 and it's pretty much up-to-date, because, well, it's a genuine Windows, and since I paid for it—against my will, I only wanted the laptop—I run M$ software update from time to time.

Safari installation went fine, though it asked me one bizarre question: “Do you want to install Bonjour...?”.  The description of this thing looked cool, so I let it on, but I'm still wondering why do they have to distribute this with a browser.  Anyway.  I start Safari.  By default it goes to apple.com/startpage, or something.  It loads it fine.  I then enter “mihai.bazon.net/blog” in the URL bar and press ENTER to see an instant crash.  Tried a few more websites with the same result.  It was that point when I thought that this beta is only good so we see the new texture of the Apple UI, because they seem to change it every month or so.

Well, talked to my friend again, and he told me that he didn't install Bonjour.  So I uninstall Safari and reinstall it again, this time without selecting Bonjour and Apple Software Update.  Same results.

System requirements

Isn't it strange that they distribute Safari for Windows and it works even on Windows 2000, and in the same time it seems to require the very latest Mac OS X version for running on their own system?

I have a Mac, but it's running Panther.  There's no way I'm gonna have Safari there, because they want me to purchase Tiger.  I don't.

Another strange thing is, they basically took the KHTML rendering engine from Konqueror (which is a decision I won't, ever, understand), called it WebKit, then wrapped their cool interface around it, and called the result “Safari”.  Though Konqueror was initially developed in Linux, WebKit doesn't even compile there (ok, last time I tried, compilation was finally successfull, after reading howto-s for half a day, but the binary instantly crashes).

Final thoughts

I managed to have it working by installing it on a different machine and deselecting Bonjour and Apple Software Updates from the start.  It runs fine there.  The UI is very cool too, but I think it's nothing they couldn't have done (probably with even less work) by wrapping around Gecko, rather than KHTML.

The rendering engine is good, probably as good as Gecko was 3 years ago.  I care less about speed (but yes in fact I do think Firefox is faster) — but I just wish they would have used Gecko from the start...  Everything sucks compared to it.

Filed in: browsers, safari, web design, windowsNo comments

Using the Right Fonts in your Website

There's something interesting about the Web lately.  More and more websites I get to seem to use tiny unreadable fonts.  Well, unreadable for me—the monitor I spend most of my time on has 1600×1200 pixels in only 15″.  That's a huge resolution (something like 120 dpi).  Give me an website that's using an “11px” font size and I'm going blind soon.

I always wondered “why”?  I think one important reason is Google AdSense.  A notorious trick to increase your click-through rate is to make users confuse AdSense with your own links—which is best achieved if they use the same fonts.  Since it's not possible to customize (enlarge) fonts in AdSense, publishers have chosen to reduce the fonts in their pages.

(read more…)

Filed in: javascript, web design13 comments
See also