"krishnananda" <k@[EMAIL PROTECTED]
> wrote in message
news:4810d64b$0$4110$4c368faf@[EMAIL PROTECTED]
> In article <6P3Qj.11862$GE1.9306@[EMAIL PROTECTED]
>,
> Paul Furman <paul-@[EMAIL PROTECTED]
> wrote:
>
>> Dudley Hanks wrote:
>> >>
>> >>>> http://www.geocities.com/hanks.dudley/index.html
>> >>>
>> >
>> > Regarding the sound, it's not a musical sound-track; rather, I just
>> > recorded a few introductory words that play when the page is loaded.
>>
>> Better to have a link or button that says:
>> <a href...>listen to introductory narrative</a>
>> because automatic sound on a web page is disturbing to many people.
>> Although this may be an exception as it's pointed at people who might
>> rather have sound.
>>
>> > A musical sound-track may come later.
>> >
>> > Take Care,
>> > Dudley
>> >
>> >
>
> As the best part of a big Flash animation is usually the "Skip Intro"
> button, the best part of an <onload> mp3 or wav is the "Mute" button.
>
> A suggestion for your coding: using tables is a good way to divide up
> the page; however, the table definition should contain specific cell
> widths based on percentage of total width, or absolute pixel size. With
> no specific instruction from the page, your tables rely on the browser
> to assign widths. This can run into problems because the picture of Dima
> is so big. You will probably have more luck with the title in one cell
> spanning the whole table, the photo of Dima in one cell directly below
> also full span, then start your text below divided into however many
> columns you want.
>
> Also acquaint yourself with the table-compositor's best friend, the
> non-breaking space, HTML entity: or Hex:   . Put one in each
> empty cell to maintain the widths.
>
> Or you can explore the possibility of using Flash. That gives you much
> more control but some people will find it painful, and possibly your
> screen reader may not be able to read it. Also, mobile web devices like
> BlackBerry can't render Flash, but you can't please everyone.
>
> Also, the Macintosh rendering engine assigns font sizes based on 72dpi
> while Windows assigns based on 96dpi. Current practice advocated by the
> W3 Consortium is to use cascading style sheets, which overcome these
> built-in differences.
>
> An excellent Windows HTML editor is UltraEdit
> <http://www.ultraedit.com/>
actually a general purpose programmer's
> editor with libraries built in for web design and programming. They have
> a free trial you can download. If you use a Mac then BBEdit
> <http://www.barebones.com>
is my personal favorite editor.
>
> Hope this helps,
>
> --k
Thanks for all the suggestions.
As a newbie to the field of html tables (pun intended), I'm trying to
figure
out all of the uses they are good for. Having only used tables for data
tables in word-processors, the concept of laying out a whole page with a
table is a bit foreign to me, but I'm starting to see the logic behind the
concept.
My next version will incor****ate many of your suggestions.
Thanks for taking the time to clue me in,
Dudley


|