thinkback
Save some hard drive space (~300MB!) by deleting languages you don’t use. Find the application icon in the Finder, pick info, select the languages you don’t use in the Languages box, then click Delete. Empty the trash.
I’ve been using Home Page, but worry about its age and dependance on Classic mode.
But I can drop a spreadsaheet onto it to create a table.
I haven’t seen any comment about iWeb’s ability (or inability) to do that.
I agree. 630 is insane. I’m getting a bit peeved at Apple making its applications bloatware—iWeb is probably the best example of that yet. So definitely remove those language files and check out this neat little tool: DesInstaller.
Although it won’t make a bit of difference to the general user, the ~/Library/Application Support/iWeb/Domain.sites file is actually a package.
By control/right clicking on Domain.sites and selecting ‘Show package contents’, one can see the files that were copied and saved into it during its creation.
Has nobody but me looked at the file size that iWeb spits out. In some designs, they’re downright criminal. In all cases they are way, way beyond anything you’d want for any but the absolutely fastest connection, which over 75% of Americans don’t have. It’s like putting a lawnmower engine in a Ferrari. Great looks, nice user interface, verrrrrrry slow download speeds for the finished pages.
Tracked: glaucousnesses
Deep Thought: iLife 06 Review Part 3: iWeb
Tracked on: glaucousnesses at 22-Feb-13 22:25 PM
1.
iWeb does share the same idea as RapidWeaver - make attractive website creation simple for everyone. But the two programs have different methods of accomplishing that goal. iLife does indeed borrow a great deal from the Pages interface. Website design with iWeb truly is WYSIWYG. RapidWeaver lets the user toggle between edit and preview modes which isn’t quite as friendly for the beginner. But the payoff is the ability to enter HTML code where that type of control is beneficial.
Check out my blog for a comparison and my thoughts on the two programs.