Complex one-screen page.

I am accustomed to click from author css to my own css (using Opera)
for two reasons: reveal the frequently-concealed links and to see the
table structure of the page. (a non-table page is rare)

Usually nothing remarkable is revealed.
This one-screen page I found amazing.

http://silviahartmann.com/

It is extraordinarily complex in that the images are split
over the tables, perhaps into six parts and borders are
created by images in small table cells.

No credit or editor is evident. Is there a way to do this that
would take less than a month's work per page?

General comments are invited. ( I have no connection to
the page).

MasonC

Mason C <masonc2 (AT) earthlink (DOT) net> wrote:

I am accustomed to click from author css to my own css (using Opera)
for two reasons: reveal the frequently-concealed links and to see the
table structure of the page. (a non-table page is rare)

Usually nothing remarkable is revealed.
This one-screen page I found amazing.

http://silviahartmann.com/

It is extraordinarily complex in that the images are split
over the tables, perhaps into six parts and borders are
created by images in small table cells.

No credit or editor is evident. Is there a way to do this that
would take less than a month's work per page?

General comments are invited. ( I have no connection to
the page).

I hope that you are not planning on emulating this.

The technique is commonly known as "image slicing", and it's frequently
used by presentational coders. It's relatively easy to create, most
graphic editors have a function that does most of the work. You create a
template image, then you overlay the desired grid on top of it, the
editor then chops up the image and generates the HTML including the
table to hold the images.

--
Spartanicus

On 2006-07-01, Mason C wrote:

I am accustomed to click from author css to my own css (using Opera)
for two reasons: reveal the frequently-concealed links and to see the
table structure of the page. (a non-table page is rare)

Usually nothing remarkable is revealed.
This one-screen page I found amazing.

http://silviahartmann.com/

It is extraordinarily complex in that the images are split
over the tables, perhaps into six parts and borders are
created by images in small table cells.

<http://cfaj.freeshell.org/2006_07_01-13_37_15.jpg>

Is that how it's supposed to look?

Is that what you want to emulate?

No credit or editor is evident. Is there a way to do this that
would take less than a month's work per page?

General comments are invited. ( I have no connection to
the page).

--
Chris F.A. Johnson, author <http://cfaj.freeshell.org>
Shell Scripting Recipes: A Problem-Solution Approach (2005, Apress)
===== My code in this post, if any, assumes the POSIX locale
===== and is released under the GNU General Public Licence

On Sat, 01 Jul 2006 08:39:55 GMT, Mason C <masonc2 (AT) earthlink (DOT) net> wrote:

I am accustomed to click from author css to my own css (using Opera)
for two reasons: reveal the frequently-concealed links and to see the
table structure of the page. (a non-table page is rare)

Usually nothing remarkable is revealed.
This one-screen page I found amazing.

http://silviahartmann.com/

It is extraordinarily complex in that the images are split
over the tables, perhaps into six parts and borders are
created by images in small table cells.

No credit or editor is evident. Is there a way to do this that
would take less than a month's work per page?

General comments are invited. ( I have no connection to
the page).

MasonC

No, I do not want to emulate this unscalable page.
Could you build this page with css and make a good page?

Mason C just curious

Mason C <masonc2 (AT) earthlink (DOT) net> wrote:

[...]

http://silviahartmann.com/

[...]

Could you build this page with css and make a good page?

CSS could be used to build something that would look like the original
whilst based on semantic markup.

It would still suffer from the original's fixed width drawback and it
would require putting the links into fixed width & height blocks with
overflow:auto behaviour to deal with client side font size variations.
The usability suffers greatly if such scroll bars are invoked by a
client.

--
Spartanicus