IWeb question and feedback

Question

I've been testing iWeb '08 and putting it through its paces. It really does a good job if you know what you are doing. It is way more capable then the easy templates reveal. But first I have a question.
If I want to include an external javascript file with a page, how do I get iWeb to publish it with all the other data? Right now I have to manually copy it to my publish folder after every time I publish. Not a very elegant solution.
I also have one big request for the next version of iWeb. For some pages, I want to make the browser background transparent. HTML allows this but not iWeb. iWeb only offers a solid color or image. It would be so easy for Apple to include a "none" option for this field like they do the page background. Here's why this little detail is so important.
When I use HTML snippets, I can put one iWeb page within another using iframes. I also overlay iframes for various effect. I need the embedded page browser backgrounds to be transparent so when the inline frame refreshes, the browser background doesn't wipe the iframe clean each time. This is what it does without the transparent option. It makes the whole inline frame look like a refresh instead of keeping the existing objects solid, except for the specific objects I want to change. It may seem a small detail but this goes a long way to making the site look solid and professional. Using transparent iframe overlays allows me to do some pretty nifty looking pages.
Right now I have to post-process my files using a utility that does a multi-file find and replace. It is fast but it still is a hack job - not very Apple-like or elegant. What I end up doing is having every page that I want to be transparent use a certain known color code (ie. #000000) that I then search for and replace with the word "transparent". This does the trick, but again, not the way things should be with Apple software.
This change I'm requesting in iWeb is not anything unreasonable or hard to implement. One Apple tech could do this in about 5 minutes. This opens iWeb up to doing iframes elegantly and enables iWeb to do amazing things without post-processing hacks. I know Apple wants to keep things simple but this one change does not jeopardize this for beginners, yet opens things up to us who are capable. It could make complex pages simple.
Actually, I wish Apple would go even further and add a new option at the bottom next to web widgets. Call it the iFrame, or subpage, option. That way I could do inline frames without even resorting to HTML snippets. Have the details come up in the inspector too. This is more complex to add but even a more elegant solution. Newbies and simple templates could ignore this function but advanced web designers would flock to it.

Answer 1

You are just talking to other users here, so make sure you also put in all your requests to Apple via the Provide iWeb Feedback item in the iWeb menu.