Quantifi Logo

[symbo]

Hi all,

I'd very interested in hearing what other people have to say about our logo design.



You can check it out at www.quantifi.com.au.

[tikanet]

A lot of folks here have viewed your post, so I'm wondering why no one has stepped up and offered an opinion. Your logo is certainly well conceived and rendered. It's easy to read, even for an all upper-case word that exceeds six characters. It wasn't until I visited your site that the significance of the outstanding "A" revealed itself through your tag-words. Looks as though it'll translate nicely to print. All-in-all, it's really quite nice.

Now, I know you didn't request a site review, but because I was compelled to pull it up in order to better understand the context of your logo, I'm unable to resist telling you that the following JavaScript error was encountered by Opera (7.2) on your http://www.quantifi.com.au/products/calendar/calendar.jsp page:
Event thread: onclick
Error:
name: ReferenceError
message: Statement on line 1: Reference to undefined variable: No such variable '?'
Backtrace:
In unknown script
qfCalendarFactory.getCalendar(1).incMonth(?);
At unknown location
{event handler trampoline}
Replace the question mark (?) with an umlauted 'u.'

So, when I saw "cross-browser compatible," a quizzical look came over my face and an audible "HUH!" stabbed the air. I loaded the page in Mozilla and Netscape. They didn't choke on the onClick function call. Now, I'm very partial to Opera -- think it's the best tab browser on the market -- but am always amazed at how many JavaScripts that were created on and for Microsoft browsers fail on Opera. Yes, admittedly, many also fail on Mozilla, so it's not just Opera. What a tricky business it is to assure that a client-side script is going to be parsed the same on any given browser, huh? Guess that's way providing such features from the client side is so popular.

[symbo]

Thanks for the reply. I was starting to wonder whether it was something that I said or didn't say that had caused so many views with no reply.

The logo is probably the 5th or 6th generation. It is never easy coming up with something that you like and will look good on a web site, print and other media.

You commented on the uppercase text. We originally had our logo in lowercase, but only recently transitioned it to the one you see here.

As for the JavaScript error, at the moment, our control doesn't support Opera. Unfortunately, Opera has a little way to go with "standards compliance" (sic) and support for CSS and DHTML. We would like nothing better than to support Opera, as we too think that it has great potential as a leading browser and we certainly do not want to alienate the Opera community. Hopefully in a few more versions it will have enough features available so we can add Opera support to our controls.

That said, I take your point about our cross-browser compatibility claim. We'll take a look at updating the wording.

Once again, I really apprecaite your comments. They are invaluable in understanding how other people percieve your projected business image.

Thanks :)

[tikanet]

Just noticed that I mis-spoke (wrote). I meant to suggest that features such as calendars are often best handled on the server side of the equation, leaving the client to handle mundane considerations such as formatting. That I typed client was my bad.

I know that this isn't the place to discuss standards compliance, but I am under the distinct impression that it is Microsoft that lags, and was even balkish in the past about getting on the standards bandwagon. From what I can glean, Opera has been at the forefront of standards compliance; see http://www.brainstormsandraves.com/a...02/macromedia/, as only one of many citations that can be offered, and was the first to adopt CSS1 in its entirety. Oh well, this really is a topic for a different forum, as is, I suppose, any debate about doing the calendar thing from the server side.