Dreamweaver - Re: templates are worthless

Author

Re: templates are worthless

itinko

2006-02-24, 10:15 pm

In the template make the body tag onload event use a parameter to assign the event handler function, then set the onload event parameter to what you need in the instance pages if it is used.

Murray *TMM*

2006-02-24, 10:15 pm

What DW are you using?

> Is there a good way to get around Dreamweaver making life
> difficult for me or am I going to have to write my own preload code?

Start by reading the F1 help on DW's Templates. Then you may find some help
here -

http://www.dreamweavermx-templates.com

--
Murray --- ICQ 71997575
Team Macromedia Volunteer for Dreamweaver
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com - Template Triage!
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes
==================

"s_mccoy" <webforumsuser@macromedia.com> wrote in message
news:dtn9uk$fvi$1@forums.macromedia.com...
> Please tell me there is a reasonable way around this problem. I created a
> template page and made a couple areas in the head tag editable such as
> title
> and a stub for adding my own scripts and page specific css. I then made a
> few
> areas within the body tag editable, locking common items such as the main
> menu
> and page footer because I want any changes made to propagate across any
> pages
> built on this template.
>
> So far so good. Now I want to build some page specific navigation and
> image
> swapping functionality but Dreamweaver won't let me preload the images
> because
> the body tag is locked in the template and won't allow enev Dreamweaver to
> add
> images to the onload event in the body (which makes one wonder why does
> Dreameaver insist on writing this code in teh body tag and not within a
> script
> tag in the head). Is there a good way to get around Dreamweaver making
> life
> difficult for me or am I going to have to write my own preload code?
>

s_mccoy

2006-02-24, 10:15 pm

I get that but Dreamweaver won't know where to write the onload parameters when
I use the behaviors and I have a lot of images, not per page but hroughout the
portfolio section, for whch I'll have to now hand code my javascript. It seems
to defeat the purpose of templates and behaviors when something as simple as
this is not possible.

s_mccoy

2006-02-24, 10:15 pm

Murray *TMM*

2006-02-24, 10:15 pm

To tell you the truth, if you need to preload lots of images on every page,
then there is something fundamentally wrong with your layout methodology,
don't you think?

--
Murray --- ICQ 71997575
Team Macromedia Volunteer for Dreamweaver
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com - Template Triage!
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes
==================

"s_mccoy" <webforumsuser@macromedia.com> wrote in message
news:dtnakg$gtb$1@forums.macromedia.com...
>I get that but Dreamweaver won't know where to write the onload parameters
>when
> I use the behaviors and I have a lot of images, not per page but hroughout
> the
> portfolio section, for whch I'll have to now hand code my javascript. It
> seems
> to defeat the purpose of templates and behaviors when something as simple
> as
> this is not possible.
>

Murray *TMM*

2006-02-24, 10:16 pm

> No, there isn't. The design has different bacgrounds for each portfolio
> page
> and the menus reside on top of this background. To make the design work
> across
> browsers propeerly I can't use PNG's.

Sure you can. PNGs are well supported as long as they are 8 or 24bit. It's
the 32bit PNGs that aren't supported by IE, and you can fix that.

> Therefore I need to load menu items and
> preload the rollover states for each page so they are responsive.

But you only need to load them once, not on each page. And your menu
buttons must be very small, no? So a preload is really unnecessary.

> I also
> preload the portfolio images so when you click the dot they load
> immediately.
> This can be anywhere from 9-12 images per page.

Ahh - but this is a design flaw. You should not load those images when the
page loads. You should only load those images when the visitor requests
them.

> The larger point here is the W3C and Dreamweaver shoudln't be telling me
> how
> to design, they should be developing tool sthat allow me to be creative
> without
> limits.

They do that. So far I have seen nothing that interferes with your
creativity.

--
Murray --- ICQ 71997575
Team Macromedia Volunteer for Dreamweaver
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com - Template Triage!
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes
==================

"s_mccoy" <webforumsuser@macromedia.com> wrote in message
news:dtnrjh$agu$1@forums.macromedia.com...
> Originally posted by: Newsgroup User
> To tell you the truth, if you need to preload lots of images on every
> page,
> then there is something fundamentally wrong with your layout methodology,
> don't you think?
>
> No, there isn't. The design has different bacgrounds for each portfolio
> page
> and the menus reside on top of this background. To make the design work
> across
> browsers propeerly I can't use PNG's. Therefore I need to load menu items
> and
> preload the rollover states for each page so they are responsive. I also
> preload the portfolio images so when you click the dot they load
> immediately.
> This can be anywhere from 9-12 images per page.
>
> The larger point here is the W3C and Dreamweaver shoudln't be telling me
> how
> to design, they should be developing tool sthat allow me to be creative
> without
> limits.
>

s_mccoy

2006-02-24, 10:16 pm

Originally posted by: Newsgroup User
To tell you the truth, if you need to preload lots of images on every page,
then there is something fundamentally wrong with your layout methodology,
don't you think?

No, there isn't. The design has different bacgrounds for each portfolio page
and the menus reside on top of this background. To make the design work across
browsers propeerly I can't use PNG's. Therefore I need to load menu items and
preload the rollover states for each page so they are responsive. I also
preload the portfolio images so when you click the dot they load immediately.
This can be anywhere from 9-12 images per page.

The larger point here is the W3C and Dreamweaver shoudln't be telling me how
to design, they should be developing tool sthat allow me to be creative without
limits.