Sitewide constants / variables

Its would have to be performed in a separate language

I dont see a reason why to force people to PHP because of such a simple
thing
like substitution of text strings.

I don't see a reason to force Adobe to add a feature that readily exists
already in all the web scripting languages it already supports. ;0)

Remember, DW is an HTML editor at its core.

-Darrel

I dont see a reason why to force people to PHP because of such a simple
thing
like substitution of text strings.

I don't see a reason to force Adobe to add a feature that readily exists
already in all the web scripting languages it already supports. ;0)

Remember, DW is an HTML editor at its core.

-Darrel

Let me say it slowly. HTML has no such capability. You are not grasping
the scope of the solution.

Let me say it slowly to you:
The only person talking about HTML here is you. The webdesign tool could allow
for inserting variables in pseudo-code, which would be replaced by defined
strings at the moment of publishing/previewing the page/site. Is it so
difficult to comprehend??

Let me say it slowly. HTML has no such capability. You are not grasping
the scope of the solution.

Let me say it slowly to you:
The only person talking about HTML here is you. The webdesign tool could allow
for inserting variables in pseudo-code, which would be replaced by defined
strings at the moment of publishing/previewing the page/site. Is it so
difficult to comprehend??

Is it so
difficult to comprehend??

It's simple to comprehend. But more difficult to imagine how.

Why don't you make this suggestion to the dev team?

http://www.adobe.com/cfusion/mmform/...?name=wishform


--
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
==================


"Powermonger" <webforumsuser (AT) macromedia (DOT) com> wrote

Let me say it slowly. HTML has no such capability. You are not grasping
the scope of the solution.

Let me say it slowly to you:
The only person talking about HTML here is you. The webdesign tool could
allow
for inserting variables in pseudo-code, which would be replaced by defined
strings at the moment of publishing/previewing the page/site. Is it so
difficult to comprehend??

Is it so
difficult to comprehend??

It's simple to comprehend. But more difficult to imagine how.

Why don't you make this suggestion to the dev team?

http://www.adobe.com/cfusion/mmform/...?name=wishform


--
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
==================


"Powermonger" <webforumsuser (AT) macromedia (DOT) com> wrote

Let me say it slowly. HTML has no such capability. You are not grasping
the scope of the solution.

Let me say it slowly to you:
The only person talking about HTML here is you. The webdesign tool could
allow
for inserting variables in pseudo-code, which would be replaced by defined
strings at the moment of publishing/previewing the page/site. Is it so
difficult to comprehend??

The only person talking about HTML here is you. The webdesign tool could
allow
for inserting variables in pseudo-code, which would be replaced by defined
strings at the moment of publishing/previewing the page/site. Is it so
difficult to comprehend??

Why use pseudo code when you can use real scripting languages?

I'm not sure why you're being so argumentative about it. These are all
opinions. You think it should do this. No one else does. That's OK.

What you are describing is a content management system that, in turn,
scripts out flat/static HTML files. These aren't teriibly common, but they
do exist. They specific products for spsecific needs and DW has no intention
of being one of those.

Besides, this really easy to do with a server side include and a bare
minimum of PHP or similar scripting language:

<?php include("mySiteVariables.php"); ?>

<title><?php echo $companyName ?></title>

But, in the end, is the Search And Replace functionality in DW not capable
of doing this for you?

-Darrel

The only person talking about HTML here is you. The webdesign tool could
allow
for inserting variables in pseudo-code, which would be replaced by defined
strings at the moment of publishing/previewing the page/site. Is it so
difficult to comprehend??

Why use pseudo code when you can use real scripting languages?

I'm not sure why you're being so argumentative about it. These are all
opinions. You think it should do this. No one else does. That's OK.

What you are describing is a content management system that, in turn,
scripts out flat/static HTML files. These aren't teriibly common, but they
do exist. They specific products for spsecific needs and DW has no intention
of being one of those.

Besides, this really easy to do with a server side include and a bare
minimum of PHP or similar scripting language:

<?php include("mySiteVariables.php"); ?>

<title><?php echo $companyName ?></title>

But, in the end, is the Search And Replace functionality in DW not capable
of doing this for you?

-Darrel

Are you saying you want to define something like Macros in Dreamweaver?

Or looking at this further, if you need to change something you could use the
Find and Replace function. That would search through the source code of your
pages to change references. This is basically the same function you would use
in Word.

What Murray is trying to say is that it doesn't matter what tool you use when
it comes to things like variables in pages. HTML is the same in Expression Web
as it is in Dreamweaver, and as it was in Frontpage and GoLive. HTML is a
static language that cannot produce dynamic content like that on its on. The
example of PHP was given because it is a common language. There is also ASP.