CSS的严重缺点 [英] A serious drawback of CSS
问题描述
我从2001年开始尝试使用CSS。当我从基于框架的网站转移到
CSS网站时，我意识到CSS的主要缺点是你不能
你的标题，manu，页脚和内容窗格在不同的文件中都有，
但是你必须在*每个*页面中重复*它们。如果我必须更改任何
公共部分，我必须同时在
的许多不同文件中应用更改。维护现在真是一团糟。
当然，当我可以利用PHP或其他服务器语言时，我可以使用他们的导入语句来获取
来自
单个文件的常见部分（作为版权），但我不能总是依赖PHP可用性。通常我必须使用基于客户端的页面来代替
，在这种情况下我必须复制很多
的东西。太疯狂了。 XHTML没有import语句，
CSS也没有办法从另一个文件中指定分区内容。
我该怎么办？请不要告诉我？使用PHP，ASP还是ColdFusion？我不能
总是这么做。
~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~
Dario de Judicibus博士 - 意大利（欧盟）
网站： http://www.dejudicibus.it/
博客： http://lindipendente.splinder.com
~~~~~~~~~ 〜div~~~~ >Dario de Judicibus <无**** @ nowhere.com>写道：
我从2001年开始尝试CSS。当我从基于框架的网站转移到CSS网站时，我意识到CSS的主要缺点是你不能<不再有你的标题，manu，页脚和内容窗格在不同的文件中，
但你必须在*每个*页面中重复*它们。
框架是一个非常破碎的概念，其中一个主要*原因*是一个
单页包含几个单独的文件。
如果我必须更改任何
公共部分，我必须同时在许多不同的文件中应用更改。维护现在真是一团糟。
当然，当我可以利用PHP或其他服务器语言时，我可以使用他们的import语句来获取一个共同的部分（作为版权）
单个文件，但我不能总是依赖PHP的可用性。
如果你在本地安装它并使用它来构建静态页面，你可以使用它来生成静态页面，虽然使用预处理器是一种更常用的方法。
通常我必须编写基于客户端的页面，在这种情况下我必须复制很多
的东西。太疯狂了。 XHTML没有import语句，也没有一种方法可以在CSS中指定另一个文件的分区内容。
这是一件好事，通过（X）HTML或CSS导入代码片段
将导致所有现有的UA无法处理内容
会使用这样的功能。当然还有原则问题
CSS用于申请*演示*。
我该怎么办？请不要告诉我？使用PHP，ASP还是ColdFusion？我不能一直这样做。
您可以使用预处理器，基于模板的创作系统通常
允许包含代码片段
a优质的S& R功能，以及上述本地
安装的脚本解决方案，交换代码块很容易。
-
Spartanicus
2006年1月23日星期一16:48:00 GMT，
comp.infosystems。 www.authoring.stylesheets ，Spartanicus
< ;在***** @ invalid.invalid>在
< nf ******************************** @ news.spartanic我们。 utvinternet.ie>
写道：
" Dario de Judicibus" <无**** @ nowhere.com>写道：
我从2001年开始尝试CSS。当我从基于框架的网站转移到CSS网站时，我意识到CSS的主要缺点是你不能<不再有你的标题，manu，页脚和内容窗格在不同的文件中，
但是你必须在*每个*页面中重复*它们。
框架是一个可怕的破碎概念，其中一个主要原因*是单页由几个单独的文件组成。
我的第一个，错误的，以为单独的文件是件好事。但是，如果你暗示你的帖子的其余部分，那么
，它作为一个创作工具很好，
不适用于客户端交付。图书馆很棒。我们大多使用
它们用于脚本等，但从概念上来说它适用于HTML（你可以使用
已经有多个css文件）。就像你说的那样，只需用预处理器或其他东西就可以实现
。
我觉得这个概念是WYSIWYG的最大问题
编辑。并不是说它们会产生错误的代码，而是它们会阻止你从b
看到代码然后被处理。当你看到你正在为显示过程编写
代码时，在中间进行处理
步骤制作显示文件没什么大不了的。
[snip]
-
Matt Silberstein
今天做一些关于达尔富尔种族灭绝的事情
http://www.beawitness.org http://www.darfurgenocide.org
http://www.savedarfur.org
达尔富尔：A种族灭绝我们可以停止
Matt Silberstein写道：
我觉得这个概念是WYSIWYG的最大问题<编辑。并不是说它们产生了错误的代码，而是它们阻止你看到代码然后被处理。当你看到你正在为显示过程编写代码时，在中间进行处理步骤制作显示文件没什么大不了的。
一个好的图形化HTML生成器可以理解
处理工具使用的语言并动态执行这样的处理，当光标进入时自动切换文件
页面的不同部分。
-
David Dorward< http://blog.dorward.me.uk/> < http://dorward.me.uk/>
首页是〜/ .bashrc的位置
I am experimenting with CSS since 2001. As I moved from frame based sites to
CSS sites, I realized that the major drawback of CSS is that you cannot
anymore have your header, manu, footer and content panes in different files,
but you have to *repeat* them in *each* page you do. If I have to change any
common section, I have to apply the change in many different files at the
same time. Maintenance is now a real mess.
Of course, when I can take advantage of PHP or other server languages, I can
use their import statements to get common sections (as copyright) from a
single file, but I cannot always rely on PHP availability. Often I have to
code client-based pages, and in such a case I have to duplicate a lot of
stuff. That''s crazy. XHTML has no import statement, nor there is a way in
CSS to specify division content from another file.
What can I do? Please, do NOT tell me ?use PHP, ASP or ColdFusion?. I cannot
always do that.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Dr. Dario de Judicibus - Italy (EU)
Site: http://www.dejudicibus.it/
Blog: http://lindipendente.splinder.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Dario de Judicibus" <no****@nowhere.com> wrote:
I am experimenting with CSS since 2001. As I moved from frame based sites to
CSS sites, I realized that the major drawback of CSS is that you cannot
anymore have your header, manu, footer and content panes in different files,
but you have to *repeat* them in *each* page you do.
Frames are a horribly broken concept, one of the main *causes* is that a
single page consists of several separate files.
If I have to change any
common section, I have to apply the change in many different files at the
same time. Maintenance is now a real mess.
Of course, when I can take advantage of PHP or other server languages, I can
use their import statements to get common sections (as copyright) from a
single file, but I cannot always rely on PHP availability.
You can if you install it locally and use it to build static pages,
although using a preprocessor is a more common approach.
Often I have to
code client-based pages, and in such a case I have to duplicate a lot of
stuff. That''s crazy. XHTML has no import statement, nor there is a way in
CSS to specify division content from another file.
And that''s a good thing, importing code fragments via (X)HTML or CSS
would result in all existing UAs not being able to handle content that
would use such a feature. There is off course also the principle issue
that CSS is for applying *presentation*.
What can I do? Please, do NOT tell me ?use PHP, ASP or ColdFusion?. I cannot
always do that.
You can use a preprocessor, template based authoring systems usually
allow inclusion of code fragments, swapping out code blocks is easy with
a good quality S&R function, and lastly the aforementioned locally
installed scripting solution.
--
Spartanicus
On Mon, 23 Jan 2006 16:48:00 GMT, in
comp.infosystems.www.authoring.stylesheets , Spartanicus
<in*****@invalid.invalid> in
<nf********************************@news.spartanic us.utvinternet.ie>
wrote:
"Dario de Judicibus" <no****@nowhere.com> wrote:I am experimenting with CSS since 2001. As I moved from frame based sites to
CSS sites, I realized that the major drawback of CSS is that you cannot
anymore have your header, manu, footer and content panes in different files,
but you have to *repeat* them in *each* page you do.
Frames are a horribly broken concept, one of the main *causes* is that a
single page consists of several separate files.
My first, wrong, thought was that separate files was a good thing. But
as you imply in the rest of your post, it is good as a creation tool,
not for client side delivery. Libraries are great stuff. We mostly use
them for scripts and such, but in concept it would work for HTML (you
can already have multiple css files) as well. Just, as you say, do it
with a pre-processor or something.
It occurs to me that that concept is the biggest problem with WYSIWYG
editors. Not that they produce bad code but that they stop you from
seeing that is code to then be processed. When you see you are writing
code to the process for display it is no big deal to have a processing
step in the middle make the display file.
[snip]
--
Matt Silberstein
Do something today about the Darfur Genocide
http://www.beawitness.org
http://www.darfurgenocide.org
http://www.savedarfur.org
"Darfur: A Genocide We can Stop"
Matt Silberstein wrote:
It occurs to me that that concept is the biggest problem with WYSIWYG
editors. Not that they produce bad code but that they stop you from
seeing that is code to then be processed. When you see you are writing
code to the process for display it is no big deal to have a processing
step in the middle make the display file.
A good graphical HTML generator could understand the language used by the
processing tool and perform such processing on the fly, automatically
switching files as the cursor moves into different sections of the page.
--
David Dorward <http://blog.dorward.me.uk/> <http://dorward.me.uk/>
Home is where the ~/.bashrc is
这篇关于CSS的严重缺点的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
