I'd like to know if I can modify the back end code that FP
uses to generate the shared border code - to get rid of
that ridiculous 24 pixel wide table cell that FP designers
decided should be part of the page.
Any ideas on how to do this - or which file it is that
generates the code?

Thanks - Jon.

[ Post a follow-up to this message ]

Hi,

Unfortunately, they plumped for the safe option of "using tables"
instead of CSS to implement this. It's actually astounding just how many
big-name sites out there are still using tables as the primary means of
formatting pages. You can control the border width by just adding a one
cell table with the width you want and then put everything inside it. I
hate nested tables, but all the modern browsers can handle them.

What's more annoying is if you want to put dynamic code into the shared
border (e.g. ASP.NET), it won't work properly unless the parent page is
also ASP.NET, but then you can't edit it in Frontpage properly!

Of course those of us "in the know", just use frames and all this
nonsense goes away.

Jonathon Archer wrote:

> I'd like to know if I can modify the back end code that FP
> uses to generate the shared border code - to get rid of
> that ridiculous 24 pixel wide table cell that FP designers
> decided should be part of the page.
> Any ideas on how to do this - or which file it is that
> generates the code?
>
> Thanks - Jon.


--
Gerry Hickman (London UK)

[ Post a follow-up to this message ]

I appreciate the reply - but adding a table will not
remove the problem.

I was hoping there was someway to alter the SE code that
gets generated in the first place.

>-----Original Message-----
>Hi,
>
>Unfortunately, they plumped for the safe option of "using
tables"
>instead of CSS to implement this. It's actually
astounding just how many
>big-name sites out there are still using tables as the
primary means of
>formatting pages. You can control the border width by
just adding a one
>cell table with the width you want and then put
everything inside it. I
>hate nested tables, but all the modern browsers can
handle them.
>
>What's more annoying is if you want to put dynamic code
into the shared
>border (e.g. ASP.NET), it won't work properly unless the
parent page is
>also ASP.NET, but then you can't edit it in Frontpage
properly!
>
>Of course those of us "in the know", just use frames and
all this
>nonsense goes away.
>
>Jonathon Archer wrote:
> 
FP 
designers 
>
>
>--
>Gerry Hickman (London UK)
>
>.
>

[ Post a follow-up to this message ]

anonymous@discussions.microsoft.com wrote:
> I appreciate the reply - but adding a table will not
> remove the problem.
>
> I was hoping there was someway to alter the SE code that
> gets generated in the first place.

I'm not aware of a way to do this, but can you explain why adding a
nested table will not solve the problem.

--
Gerry Hickman (London UK)

[ Post a follow-up to this message ]