Skip to Content

iWeb code not so pretty

I put out a call for your iWeb produced pages and you answered in droves. Now, I'm no HTML/XHTML/CSS expert, but Todd Dominey is, and he isn't pleased with the code that he sees. The code is standards compliant, but it is doing some odd things that just aren't needed, or wanted.

If you want the full scoop check out Todd's post.

Categories

Macworld Software

I put out a call for your iWeb produced pages and you answered in droves. Now, I'm no HTML/XHTML/CSS expert, but Todd Dominey is, and he...
 

Add a Comment

*0 / 3000 Character Maximum

10 Comments

Filter by:
Axel

on word ; RAPIDWEAWER

January 13 2006 at 9:37 AM Report abuse rate up rate down Reply
B Crandall

"Does it work like advertised?"

Yes, it absolutely does. The code isn't pretty but... let's face it -- it's a perfect product given its purpose. The mere fact that my mom can now EASILY publish to the Web is HUGE.

Let's remember, Apple is targetting people who don't already know how to put up a website. Those of us who already know this stuff won't find iWeb nearly as attractive.

January 12 2006 at 11:40 PM Report abuse rate up rate down Reply
Lloyd Wagoner

Does it work like advertised.

January 12 2006 at 10:51 PM Report abuse rate up rate down Reply
Don Wilson

Indeed, I saw all of those style="" on the div's, and I figured they could have made smart classes quite easily.

January 12 2006 at 10:40 PM Report abuse rate up rate down Reply
Darryl

Of course, the code is not as clean as doing it yourself. Does anyone think the users who make up the target demo for WYSIWYG HTML editors really care? They simply don't want to mess with HTML -- period.

January 12 2006 at 10:40 PM Report abuse rate up rate down Reply
Rob Knight

Addendum to comment #2:

Removing the Flip4Mac Quicktime plugin, solved all of my problems with the iLife 06 apps crashing.

Phew!

January 12 2006 at 9:45 PM Report abuse rate up rate down Reply
Tom

Yeah, it's bloat code. But I like the first comment: think of this as a super-easy to use WSYWYG editor for only $15. With full integration to iPhoto, plenty of people would pay at least $25 for this app as Shareware.

I think the real question is: who's beating down Apples door for a Web editor? This isn't 1996. But hey, his Steveness sounded excited so lets get excited!

January 12 2006 at 9:28 PM Report abuse rate up rate down Reply
computerdude33

Until iWeb can publish directly to FTP, I'm sticking to RapidWeaver (http://www.realmacsoftware.com/rapidweaver/).

January 12 2006 at 8:58 PM Report abuse rate up rate down Reply
Rob Knight

Not to mention it saves many images as pngs which are FREAKING HUGE!!
There certainly needs to be more image optimization before this product hits the big time.

The overshadowing problem I've had so far is the integrated media browser. In each iLife 06 app, the media browser has crashed the app at least once. The exception is iPhoto, which has worked fine so far. This feels like a beta and I've sent more error reports than I've created exciting things. Bummer.
Be sure to send your error reports. I have a feeling its going to be a long weekend at Apple.

January 12 2006 at 8:20 PM Report abuse rate up rate down Reply
jbelkin

DON'T CARE. It's easy to use. Rest of web design software either high end or just plain inept (one of the main competitors offered WYSIWYG ... when I asked why the fonts were low res - they said, we're working on that ... this was not a shareware app).

iWEB is exactly what PAGES is - like a mini desktop publisher. Everything is an element - drag, drop, click, link - publish to .mac. That's all it is.

If you count the apps in ilife as "equal" (even the free itunes) then you're talking about $15 for iWeb. Your expectations are just too freakin' high!

January 12 2006 at 8:14 PM Report abuse rate up rate down Reply
Buy an ad here

Hot Apps on TUAW

Tweets

© 2012 AOL Inc. All Rights Reserved.