Sitewide constants / variables

Oh really? For example, in Netobjects Fusion, you can define text
variables
which do exactly what I discuss here.

And that is a CMS using that 'variable, search & replaec, then publish'
metaphor.

Again, it's rarely used or needed these days BECAUSE of server side
languages. It's kind of an antiquated model (though it still has its uses,
admittedly). DW simply isn't targetting that particular need. It's really a
text editor for people to write their own HTML with PHP or ASP or the like.

The more you are describing your need, the more it sounds like you are
actually looking for Server Side Includes at the basic level, or, on a
slightly more complex (I stress SLIGHTLY more complex) a wee bit of PHP or
ASP.

-Darrel

You don't have to 'learn PHP'. See my other reply. It's two lines of code.
Cut and paste.

You're going to find that nearly every server can support PHP. If not PHP,
then ASP/ASP.net, both which can be utilized for what you want with a
minimum of actual code. (2 or 3 lines).

I really appreciate your effort to convince me that such a function is not
needed in DW :-). After all, it is only taking care if there is PHP or ASP and
searching + replacing throughout the site. Darell, please, I know it can be
done these ways and now I also know that DW cannot do it by its own means. I
just insist that this function would be good in DW, and this is my firm
opinion.

It is exactly what you are describing...static pages with variables that
then can be post-processed to swap out the variables for actual text and
then published as static HTML files. That is one (of many) models for a CMS.

:-) No, Darell. There is a big distance between CMS and a list of several
variables defined within a webdesign tool. Substitution is what they have in
common, but that's about all. To implement a CMS is a large-scale task, while
to implement simple variable substitutions is a much much smaller duty.

You don't have to 'learn PHP'. See my other reply. It's two lines of code.
Cut and paste.

You're going to find that nearly every server can support PHP. If not PHP,
then ASP/ASP.net, both which can be utilized for what you want with a
minimum of actual code. (2 or 3 lines).

I really appreciate your effort to convince me that such a function is not
needed in DW :-). After all, it is only taking care if there is PHP or ASP and
searching + replacing throughout the site. Darell, please, I know it can be
done these ways and now I also know that DW cannot do it by its own means. I
just insist that this function would be good in DW, and this is my firm
opinion.

It is exactly what you are describing...static pages with variables that
then can be post-processed to swap out the variables for actual text and
then published as static HTML files. That is one (of many) models for a CMS.

:-) No, Darell. There is a big distance between CMS and a list of several
variables defined within a webdesign tool. Substitution is what they have in
common, but that's about all. To implement a CMS is a large-scale task, while
to implement simple variable substitutions is a much much smaller duty.

Oh really? For example, in Netobjects Fusion, you can define text
variables
which do exactly what I discuss here.

And that is a CMS using that 'variable, search & replaec, then publish'
metaphor.

It is a bit weird to call Netobjects Fusion a CMS... I think that for most
people it is a WYSIWYG webdesign tool working on different principle than DW.
Do you call everything what makes substitutions a CMS? :-)

Oh really? For example, in Netobjects Fusion, you can define text
variables
which do exactly what I discuss here.

And that is a CMS using that 'variable, search & replaec, then publish'
metaphor.

It is a bit weird to call Netobjects Fusion a CMS... I think that for most
people it is a WYSIWYG webdesign tool working on different principle than DW.
Do you call everything what makes substitutions a CMS? :-)

I
just insist that this function would be good in DW, and this is my firm
opinion

I understand.

I don't think Adobe would agree, though. It just doesn't make a lot of
business sense to focus on adding that particular feature when it's already
built into the server products most developers are using.

-Darrel

I
just insist that this function would be good in DW, and this is my firm
opinion

I understand.

I don't think Adobe would agree, though. It just doesn't make a lot of
business sense to focus on adding that particular feature when it's already
built into the server products most developers are using.

-Darrel

It is a bit weird to call Netobjects Fusion a CMS... I think that for most
people it is a WYSIWYG webdesign tool working on different principle than
DW.
Do you call everything what makes substitutions a CMS? :-)

CMS is a very generic term. Content Management. NetObjects Fusion is a
primitive CMS. Just as you describe.

DW is not in any way a CMS. It's an HTML, code, and file management system.

The 'variable swap' concept is really a CMS and/or Server Language related
idea...not a text editor related idea.

'Content Management Systems' come in a HUGE range of products that offer
features sets from the most basic to the most complex with prices to match.

Alas, that's the problem with the term 'CMS' nearly everyone has a slightly
different definition of what it is, so it can lead to a lot of confusion
from firm to firm, vendor to vendor, developer to developer.

Some people think CMS means 'I can open a page and pick fonts and colors
myself'. Some thing it means 'a highly structured and relational publishing
platform that lets us single source our content for use globally across
multiple media formats, languages, locales, and technologies'. And then
there's everything in between. ;o)

-Darrel

It is a bit weird to call Netobjects Fusion a CMS... I think that for most
people it is a WYSIWYG webdesign tool working on different principle than
DW.
Do you call everything what makes substitutions a CMS? :-)

CMS is a very generic term. Content Management. NetObjects Fusion is a
primitive CMS. Just as you describe.

DW is not in any way a CMS. It's an HTML, code, and file management system.

The 'variable swap' concept is really a CMS and/or Server Language related
idea...not a text editor related idea.

'Content Management Systems' come in a HUGE range of products that offer
features sets from the most basic to the most complex with prices to match.

Alas, that's the problem with the term 'CMS' nearly everyone has a slightly
different definition of what it is, so it can lead to a lot of confusion
from firm to firm, vendor to vendor, developer to developer.

Some people think CMS means 'I can open a page and pick fonts and colors
myself'. Some thing it means 'a highly structured and relational publishing
platform that lets us single source our content for use globally across
multiple media formats, languages, locales, and technologies'. And then
there's everything in between. ;o)

-Darrel

DW is not in any way a CMS. It's an HTML, code, and file management
system.

....unless we bring Contribute into the equation, and then the definition
starts getting muddy again... ;0)