DW8 forces title and DTD ?

Hi,

I have created default templates for new documents but DW8 forces document
titles and DTD headers (for HTML, PHP, ASP etc documents). I set up in
preferences 'none' in DTD section but DW8 adds then XML header. Titles are
replaced to 'untitled document' instead copy it from templates of new
documents. How to solve these problems?

Thanks for help,
Marek

preferences 'none' in DTD section

Why on earth would you do that?

but DW8 adds then XML header.

Not for me.

Titles are replaced to 'untitled document' instead copy it from templates
of new documents.

A properly made template will have an editable region around the title tag
so that it can be changed in each child page. Do you have that?

--
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
==================


"Marek" <marek1967 (AT) spam (DOT) interia.pl> wrote

Hi,

I have created default templates for new documents but DW8 forces document
titles and DTD headers (for HTML, PHP, ASP etc documents). I set up in
preferences 'none' in DTD section but DW8 adds then XML header. Titles are
replaced to 'untitled document' instead copy it from templates of new
documents. How to solve these problems?

Thanks for help,
Marek

Hi,

DTD definition forces changes in DOM model. Some properties of HTML elements
disappeared after adding DTD. For example I couldn't dynamicaly change
position of layers. That was the problem which I faced directly. Generally
JS can't be reliable becouse depends on user browser and it is not a
compilable language. That's obvious fact. On the other hand it's hard to
say to customers that layer animations are impossible when he saw them
somewhere in the web. Conclusion is that designers must be flexible and
sometimes instead solving problems just work around them. Removing DTD
section is good example such a "work around":

Regards,
Marek

For example I couldn't dynamicaly change position of layers.

Again, this is a problem with your javascript coding - by accessing the DOM
properly, you would be able to do this on a page rendered in standards mode.

Generally JS can't be reliable becouse depends on user browser

Pardon me, but this is nonsense.

Removing DTD section is good example such a "work around":

No, it's not.

--
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
==================


"Marek" <marek1967 (AT) spam (DOT) interia.pl> wrote

Hi,

DTD definition forces changes in DOM model. Some properties of HTML
elements disappeared after adding DTD. For example I couldn't dynamicaly
change position of layers. That was the problem which I faced directly.
Generally JS can't be reliable becouse depends on user browser and it is
not a compilable language. That's obvious fact. On the other hand it's
hard to say to customers that layer animations are impossible when he saw
them somewhere in the web. Conclusion is that designers must be flexible
and sometimes instead solving problems just work around them. Removing DTD
section is good example such a "work around":

Regards,
Marek

I would never do that. As Micha said, by having to revert to bugwards
mode (i.e., removing the doctype) to make your dHTML work, you are
demonstrating that the dHTML itself is broken.

yes yes, I'm conscious of this. I have written a lot regarding to this in
the reply to Michael. Please refere to my opinion placed there.

With regard to the title question, I simply cannot imagine doing what you
are describing. The title is one of the most important parts of the page,
and you would force every page to have the same title?

Yes. I would like keep Polish version of start-up templates, clear for other
developers. It was possible in DW7 and any changes could be a reason of
their confusion.

Well, anyhow, sorry - I can't help you with this....

Ok, thanks a lot for your time :-)

..oO(Marek)

DTD definition forces changes in DOM model. Some properties of HTML elements
disappeared after adding DTD.

Then they don't belong to the written standard.

For example I couldn't dynamicaly change
position of layers.

Should work in valid code, so it's probably just a bug in the script.

That was the problem which I faced directly. Generally
JS can't be reliable becouse depends on user browser and it is not a
compilable language.

Compilable or not doesn't matter (BTW: even scripting languages can be
compiled, see PHP for example). HTML is a standard, JS is a standard.
The only way to get reliable and predictable results and portability
across different platforms/browsers is to write according to these
standards and only add hacks or workarounds if absolutely necessary.

That's obvious fact. On the other hand it's hard to
say to customers that layer animations are impossible when he saw them
somewhere in the web. Conclusion is that designers must be flexible and
sometimes instead solving problems just work around them. Removing DTD
section is good example such a "work around":

It's no workaround, but opens Pandora's Box. Broken code might not work
in future browsers anymore, valid code will.

Micha

On 01 Nov 2005 in macromedia.dreamweaver, Michael Fesser wrote:

Compilable or not doesn't matter (BTW: even scripting languages can be
compiled, see PHP for example).

Do you have a reference for compiling PHP scripts? I did a web search
(including at php.net), but all I could find was stuff on compiling PHP
itself.

--
Joe Makowiec
http://makowiec.net/
Email: http://makowiec.net/email.php

..oO(Joe Makowiec)

On 01 Nov 2005 in macromedia.dreamweaver, Michael Fesser wrote:

Compilable or not doesn't matter (BTW: even scripting languages can be
compiled, see PHP for example).

Do you have a reference for compiling PHP scripts? I did a web search
(including at php.net), but all I could find was stuff on compiling PHP
itself.

PHP code is compiled to bytecode before the Zend engine executes it.

This bytecode can be cached, which saves some time when the script runs
the next time. This is the way the Zend Encoder goes:

http://www.zend.com/store/products/zend-encoder.php

Then there's the Roadsend Compiler, which creates native standalone
binary executables:

http://www.roadsend.com/home/index.php?SMC=1

Some other projects can be found on Google:

http://www.google.com/search?q=php+bytecode+compiler

But I haven't yet tested one of them.

Micha

On 01 Nov 2005 in macromedia.dreamweaver, Michael Fesser wrote:

PHP code is compiled to bytecode before the Zend engine executes it.
snip

Thanks for the references. Looks like I have some reading to do.

--
Joe Makowiec
http://makowiec.net/
Email: http://makowiec.net/email.php

Again, this is a problem with your javascript coding - by accessing the
DOM properly, you would be able to do this on a page rendered in standards
mode.

Microsoft's documentation describes how DTD influences on CSS attributes
etc. I tried to find article in knowlegde base which helped me to solve some
DHTML issues but I gave up. It is hard to me go back to already solved
problem with JS dependence on DTD (I mean changes and limitations when
accessing DOM elements attributes).

Pardon me, but this is nonsense.

Now, I feel a little surprised. Do you claim that JS is identical for all
browsers versions? Do you think that it is possible to create JS code which
will work under e.g. Netscepe and IE on current and future versions? Sorry,
but I spend a lot of time programming dynamic websites and faced a lot of
differences between browsers. I can firmly claim than client side
programming in scripting languages can't be reliable. What is working now
can't stop working in next versions of browsers. Notice that access to
layers in Netscape 4 was totally different then under IE (in the same time)
and changed in next versions. Now... got obsolete. That's the reason why I
feel surprised your opinion that script programming may be reliable.

Removing DTD section is good example such a "work around":

No, it's not.

I spent 1 hour searching for Microsoft's technical article with that advice
which I found beeing in trouble.