blocks|key|1716489|text|CSS的“框架”完全没有抓住要点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1716490|CSS与JavaScript不同，后者可以包含一个基库/框架，然后调用其中的函数和对象来执行更高级别的工作。CSS框架能给你的就是声明性规则:一些默认的浏览器规则重置的东西，一些强制你的页面创作的类样式，以及使用‘浮动’和‘清除’的布局规则。您可以自己编写几行CSS代码，而不是引入成百上千的框架规则。|1716491|特别是“网格布局”的东西，可以追溯到过去将你的演示混合到你的标记中的糟糕的日子。‘'div+class=“span-24”“并不比一个表好多少，你必须回到那里并更改标记以影响布局。我所见过的所有框架都是基于固定像素的浮动框的，这使得创建一个可以在各种大小的窗口上访问的流畅布局是不可能的。|1716492|它是反向创作，只对那些不敢写CSS规则的人有用。|1716493|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

CSS 'frameworks' are completely missing the point.

CSS is not like JavaScript, where you can include a base library/framework and then call functions and objects from it to do higher-level work. All a CSS framework can give you is declarative rules: some default browser-rule-reset stuff, some class styles to be forced to author your page to, and layout rules using 'float' and 'clear'. You can write that in a few lines of CSS yourself rather than pulling in the bloat of a hundred framework rules.

The 'grid layout' stuff in particular goes back to the bad old days of mixing your presentation into your markup. 'div class="span-24"' is no better than a table, you'll have to go back in there and change the markup to affect the layout. And all the frameworks I've seen are based around fixed-pixel floated boxes, making it impossible to create a liquid layout accessible on a wide range of window sizes.

It's backwards authoring, of use only for someone too scared to write a CSS rule.

blocks|key|1716566|text|AppFuse的Matt+Raible不久前举办了一次CSS框架大赛，为AppFuse开发CSS框架。研究结果发表在here上。有一些变体，我自己也用过一些，因为我使用的是AppFuse，并且发现它们非常好。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1716567|我应该补充说，这些CSS框架工作得很好，因为它们用于主题应用程序。也就是说，如果您坚持使用规则，那么从一个规则切换到另一个规则就像在属性文件中更改一个值一样简单。|1716568|entityMap|0|LINK|mutability|MUTABLE|url|http://css.appfuse.org/themes/^0|1M|4|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

Matt Raible of AppFuse fame had a CSS Framework contest a while back to develop CSS Frameworks for AppFuse. The results are published <a href="http://css.appfuse.org/themes/" rel="nofollow noreferrer">here</a>. There are a few variations and I have used some myself because I use AppFuse and find them very good.

I should add that these CSS Frameworks work well because they are used in themed applications. That is, if you stick to the rules then switching from one to the next is as simple as changing one value in a properties file.

blocks|key|1501538|text|实际上，在过去的24小时里，我花了很大一部分时间自己调查这件事，嘿。我的结论是，一个很好的重置(我使用了YUI+Reset)，也许还有其他东西来设置基线(YUI+fonts在我的例子中很有价值；也许BluePrint的“额外好处”会在你的例子中)是一个好主意。但是，“框架”-它通常类似于YUI+grids-限制太多，迫使你使用它们的类名、ids等，并且很少像手工制作的CSS那样适合你的站点。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1501539|因此，简而言之:重置看起来很不错；消除列表的边距对填充、段落间距等方面的所有变化是很好的。但这就是我所能做的。|1501540|entityMap|0|LINK|mutability|MUTABLE|url|http://developer.yahoo.com/yui/reset/|1|http://developer.yahoo.com/yui/fonts/|2|http://developer.yahoo.com/yui/grids/^0|1G|9|0|25|9|1|40|9|2|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]|$A|V|B|W|1|X]|$A|Y|B|Z|1|10]]|C|$]]|$1|D|3|E|5|6|7|11|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|12|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]|P|$5|I|J|K|C|$L|Q]]]]

I actually spent a good portion of the last 24 hours investigating this on my own, heh. My conclusion was that a nice reset (I used <a href="http://developer.yahoo.com/yui/reset/" rel="nofollow noreferrer">YUI Reset</a>), and maybe something else to set baseline stuff (<a href="http://developer.yahoo.com/yui/fonts/" rel="nofollow noreferrer">YUI fonts</a> was worthwhile in my case; maybe the "extra goodies" of BluePrint would be in yours) is a good idea. But, a "framework"---which is generally something like <a href="http://developer.yahoo.com/yui/grids/" rel="nofollow noreferrer">YUI grids</a>---is too restrictive, forcing you to use their class names, ids, etc. and rarely fitting into your site like hand-made CSS would.

So in short: resets seem pretty nice; it's good to eliminate all the variation in e.g. margin-vs-padding for lists, or paragraph spacing, or whatever. But that's as far as I would take it.

blocks|key|1501630|text|我相信CSS是关于简单性的。目标是当您在HTML和样式表之间引用时，有一个或两个地方可以检查。添加更多的行，特别是您没有编写并且可能不太熟悉的行，将会成倍地增加CSS代码的复杂性，从而增加易变性。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1501631|我建议您在编写布局时使用它们，并从中开发一个通用的模板系统。虽然我喜欢让CSS更模块化，但根据设计的不同，你的CSS可能非常特定于案例，而根本不是模块化的。|1501632|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I believe CSS is about simplicity. The goal is to have one or two places to check when you're referencing between the HTML and your stylesheet. Adding more lines, and especially lines that you did not write and are probably not that familiar with, will exponentially increase the complexity thereby volatility of the CSS code.

I would suggest your layouts as you write them and develop a generic template system from that. While I love making CSS more modular, often and depending on the design, your CSS may be very case-specific and not modular at all.

blocks|key|1501714|text|我在一些一次性的网站上使用过Blueprint，它确实节省了时间，主要是在跨浏览器测试方面。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1501715|将表示代码添加到您的标记中肯定很糟糕，尽管从好的方面来看，它是可读的。虽然我喜欢“你可以在不接触标记的情况下重新设计”的概念，但如果你正在制作一个无论如何都不会发生这种情况的网站，而且你只需要在昨天完成它，那么Blueprint是值得关注的东西。|1501716|不过，在它可以可行地创建哪些类型的布局方面也存在权衡。如果你从一开始就在一个严格的网格上对站点进行线框设计，那么转置到框架中就会容易得多，而不必大惊小怪。|1501717|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I've used Blueprint on a few one-off sites and it definitely saved time, primarily in cross-browser testing. 

It definitely sucks adding presentation code to your markup, although on the bright side it's readable. While I love the concept of "you can redesign without touching the markup", if you're producing a site where that really isn't going to happen anyways and you just need it done yesterday, Blueprint is something to look at.

There are also tradeoffs in what types of layouts it can feasibly create though. If you wireframe the site from the start on a strict grid, it will be much easier to transpose into the framework with a minimum of fuss.

blocks|key|1501795|text|我在一个网站上使用BluePrint取得了很大的成功(我可以在这里提到这个网站，但我肯定这篇文章会被标记为垃圾邮件！)。不过，我不确定将来是否会使用它，因为我认为CSS的一个想法是不对布局逻辑进行硬编码。不应该使用名为span-24和span-12的css元素来定义布局，而应该使用searchBox和mainContent这样的元素来定义布局。至少我是这么看的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1501796|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I have used BluePrint with much success on a site (I could mention the site here but I am sure the post would be marked as spam!). I am not sure if I will use it in the future though because one of the ideas of CSS i thought was to not have layout logic hard coded. You shouldn't have css elements called span-24 and span-12 to define the layout but something like searchBox and mainContent. At least thats how I see it.

blocks|key|1716931|text|花点时间去学习和理解(真正理解！)一些css框架，比如BluePrint和YUI，还有一些css重置，比如Eric+Meyer的重置。然后，根据你的工作方法和你建立的网站类型，花点时间组装你自己的重置和/或框架。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1716932|就我个人而言，我使用Eric+Meyer重置的大部分，以及我自己的一些类和重置，以及来自BluePrint和YUI的一些想法。|1716933|我最近看了Eric+Meyer关于CSS框架的演讲，在演讲中他问了一个问题：“那么哪个框架适合我呢？”然后，他通过展示一张空白幻灯片回答了这个问题。他的观点是，大多数重置和框架中肯定有一些有用的概念，但最适合你的是你自己写的(这是值得努力的)。|1716934|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Take the time to study and understand (really understand!) a few css frameworks such as BluePrint and YUI, and css resets like Eric Meyer's. Then, take the time to put together your own reset and/or framework based on your work methods and the kind of sites you build.

Personally, I use most of the Eric Meyer reset with some classes and resets of my own, plus a few ideas from BluePrint and YUI.

I recently watched Eric Meyer give a presentation on CSS Frameworks in which he asked the question: "so which one is the right one for me?" He then answered the question by showing a blank slide. His point was, that there are certainly some useful concepts built into most resets and frameworks, but the one that will suit you the best is the one that you write for yourself (it's worth the effort).

blocks|key|1501942|text|我使用过BluePrint和YUI，但我总是对他们给自己的id和类的一些名称感到失望。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1501943|每个人都有自己的工作，但我更喜欢从头开始做事情，但过了一段时间，你会开发一个过程，在这个过程中，你将使用以前的工作，并将其应用于新项目，然后进行一些调整，使网站看起来像你希望的那样。|1501944|一定要使用一个好的命名约定，以防其他人进来编辑css，这样他们就能很好地了解每个样式名称是指什么。|1501945|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I have used BluePrint and YUI but I always get frustrated with some of the names they give their id and classes.

To each their own, but I prefer doing things from scratch, but after a while you develop a process in which you will use your previous work and apply it to new projects and just make some tweaks to make the web site look the way you would like it to.

Be sure to use a good naming convention, just in case someone else down the road comes in to edit the css, then they will have a good idea what each style name is referring to.

blocks|key|1501986|text|是的，我还没有用过它，但我认为emastic可能是一个很好的替代品，值得一试。它在作用域上类似于blueprint，但也支持弹性布局(因此而得名)，您可以指定px、em或%25的值，甚至可以混合使用它们。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1501987|entityMap|0|LINK|mutability|MUTABLE|url|http://code.google.com/p/emastic/^0|F|7|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

i haven't used it yes, but i think <a href="http://code.google.com/p/emastic/" rel="nofollow noreferrer">emastic</a> may be a good alternative worth a check. it it is similar to blueprint in scope, but also supports elastic layouts (hence the name) and you can specify values in px, em or %, and even mix them.

blocks|key|1717148|text|Compass是一个实际的CSS框架，因为它不仅提供了模板(+YUI和蓝图)，还提供了可重用的构造和更高级别的声明，同时还提供了熟悉的CSS语法。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1717149|entityMap|0|LINK|mutability|MUTABLE|url|http://acts-as-architect.blogspot.com/2008/11/introducing-compass.html^0|0|7|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

<a href="http://acts-as-architect.blogspot.com/2008/11/introducing-compass.html" rel="nofollow noreferrer">Compass</a> is an actual CSS framework in the sense that it gives you not only templates (both YUI and blueprint), but also reusable constructs and higher-level declarations while still giving you familiar CSS syntax.

blocks|key|1717172|text|我找到了很好的链接：Top+12+CSS+Frameworks+and+How+to+Understand+Them|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1717173|entityMap|0|LINK|mutability|MUTABLE|url|http://speckyboy.com/2008/03/28/top-12-css-frameworks-and-how-to-understand-them/^0|A|1C|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Good link I found : <a href="http://speckyboy.com/2008/03/28/top-12-css-frameworks-and-how-to-understand-them/" rel="nofollow noreferrer">Top 12 CSS Frameworks and How to Understand Them</a>

blocks|key|1717207|text|这是我关于CSS+Frameworks+When+to+use+CSS+framework?的博客文章|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1717208|entityMap|0|LINK|mutability|MUTABLE|url|http://www.vcarrer.com/2008/08/when-to-use-css-framework.html^0|K|Q|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Here is my blog post about CSS Frameworks <a href="http://www.vcarrer.com/2008/08/when-to-use-css-framework.html" rel="nofollow noreferrer">When to use CSS framework?</a>

blocks|key|1717314|text|据我所知，使用CSS框架并保留语义标记的唯一方法是使用更高级别的抽象。目前，Compass是我所知道的唯一一个成熟到可以使用的工具，但Nicole+Sullivan似乎正在用她的“面向对象的CSS”项目做一些有趣的事情。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1717315|我发现Compass巧妙地使用了Sass混入，这是迈向可维护语义标记这一圣杯的一大步。我认为我不想使用像Blueprint或YUI这样的框架，而不使用像Compass这样的抽象来将表示类排除在标记之外。|1717316|顺便说一句，有一个漂亮的CSS框架叫做Elastic，它看起来足够好了，我正在考虑将它添加到Compass中。|1717317|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

The only way I know of to use a CSS framework and retain semantic markup is to use a higher-level abstraction. At the moment, Compass is the only one I'm aware of that's mature enough to use, but Nicole Sullivan seems to be doing some interesting stuff with her "Object-Oriented CSS" project.

I find Compass' clever use of Sass mixins to be brilliant, and a big step toward the Holy Grail of maintainable semantic markup. I don't think I'd want to use a framework like Blueprint or YUI without an abstraction such as Compass to keep presentation classes out of the markup.

BTW, there's a nice-looking CSS framework called Elastic that looks good enough that I'm considering adding it to Compass.

blocks|key|1717352|text|我觉得指南针太棒了。确保您看到了screencast。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1717353|我正在使用960.gs的一些网站，并发现它非常简单和容易，值得努力。节省了我在布局上的大量工作。一定要检查自定义CSS生成器，它的固定宽度为960像素。|1717354|entityMap|0|LINK|mutability|MUTABLE|url|http://wiki.github.com/chriseppstein/compass|1|http://www.960.gs/^0|G|A|0|0|5|6|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

Compass I think is amazing. Make sure you see the <a href="http://wiki.github.com/chriseppstein/compass" rel="nofollow noreferrer">screencast</a>.

I am using <a href="http://www.960.gs" rel="nofollow noreferrer">960.gs</a> for a few websites and find it very simple and easy and worth the effort. Saves me a lot of work on layout. Make sure to check the custom CSS generator which goes away with the fixed width of 960 pixels.

blocks|key|1717399|text|你必须问问你自己，可用的框架在解决你的问题上有多有效。它们是否符合您的要求？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1717400|通过使用框架，您可以在像素级别设置一些规则或细节，并将其余时间用于实现和生产。这是一个巨大的生产力提升。如果你发现自己在项目后期花了一些时间调整东西(微观管理设计)，这是一个迹象，表明框架可以是有用的。|1717401|The+Pragmatic+Programmer中的提示#17说：“接近问题域的程序”。使用抽象层可以让您更接近解决布局的实际问题。例如:您可以集中精力通过额外的时间来增强用户体验，而不是对像素进行细微的调整。|offset|length|1717402|这并不是说你必须为了数量而牺牲质量。这是关于效率的。|1717403|在最近的一个项目中，我制作了自己的框架，因为我们的资源非常有限，而流行的框架并没有做我想要的事情。然后，我将设计团队的PSD设置为捕捉到我部署的同一网格。|1717404|框架不必是CSS的任何特定实现。它不一定是你从互联网上下载的臃肿的东西，也不是实现过时想法的东西。这只是一种完成工作的技巧。如果一些程序员已经有了自己的框架，但却不知道这一点，我不会感到惊讶。实际上，如果您将DOM视为使用CSS扩展的一组默认元素，那么根据定义，这就是一个框架。|1717405|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/The_Pragmatic_Programmer^0|0|0|0|O|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|X|8|@]|9|@$F|Y|G|Z|1|10]]|A|$]]|$1|H|3|I|5|6|7|11|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|12|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|13|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U]]]]

You'd have to ask yourself how effective the available frameworks are at solving your problems. Do they meet your requirements? 

By using a framework, you can set some rules or details at the pixel level and devote the rest of your time to implementing and producing. It's a massive productivity boost. If you find yourself spending time adjusting things by a few pixels late in the project (micro managing the design), it's a sign that a framework can be useful. 

Tip #17 in <a href="http://en.wikipedia.org/wiki/The_Pragmatic_Programmer" rel="noreferrer">The Pragmatic Programmer</a> says: "Program close to the problem domain". Using a layer of abstraction can get you closer to solving the real problems of layout. For example: you might be able to concentrate of enhancing the user experience with the extra time you have rather than minor adjustments of pixels. 

This is not to say you must sacrifice quality for quantity. It's about efficiency.

On a recent project, I made my own framework because we had very limited resources and the popular frameworks didn't do what I wanted. Then, I set up the design team's PSDs to snap to the same grid I deployed. 

A framework doesn't have to be any particular implementation of CSS. It doesn't have to be something bloated you downloaded from the interweb or something implementing outdated ideas. It's just a technique for getting a job done. I wouldn't be surprised if some coders already have their own frameworks and don't even know it. In fact, if you consider the DOM as a set of default elements you extend with CSS, then that's a framework by definition.

blocks|key|1717427|text|我认为this+video+presentation+by+Site+Point首席执行官凯文·扬克会回答你的问题。我真的推荐你去看。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1717428|entityMap|0|LINK|mutability|MUTABLE|url|http://www.sitepoint.com/blogs/2009/11/10/video-css-frameworks-%25E2%2580%2593-make-the-right-choice/^0|3|N|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I think that <a href="http://www.sitepoint.com/blogs/2009/11/10/video-css-frameworks-%E2%80%93-make-the-right-choice/" rel="nofollow noreferrer">this video presentation</a> by Site Point CEO Kevin Yank will answer your question. I really recommend to watch it.

blocks|key|1502310|text|Compass允许您使用自己的语义名称重命名框架的类和it，因此您可能希望检查它。它还提供了对简单的CSS无法获得的东西的访问，比如mixins。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1502311|我对所谓的"CSS专家“感到惊讶，他们在没有真正深入研究和使用这些工具的情况下批评这些工具。它们是必不可少的吗？不是的。如果你喜欢你自己的框架(你也有自己的框架，对吧？CSS框架只是一个精心定义的库--每个人都应该使用它)，然后一定要继续使用它。没有人强迫您使用其他框架，我也没有看到使用框架的人告诉CSS纯粹主义者他们“做错了”。|1502312|从这样的立场批评框架只会暴露出一种不安全感，也是一种无知。例如，一个人会在不了解CSS的情况下使用像Compass这样的工具的想法是可笑的。您是否意识到，框架通常不会为您编写所有CSS？您仍然可以在大多数框架的上下文中突破并编写自己的CSS。事实上，如果你不了解CSS，你可能很快就会感到沮丧。|1502313|对于我自己来说，我很欣赏拥有一个框架，因为它已经被成百上千的其他用户记录和测试，并且我可以通过Compass应用我自己的类和I。如果我需要框架不适合的东西，那么我会编写自己的代码。|1502314|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Compass lets you rename your framework's classes and ids with your own semantic names, so you might want to check it out. It also provides access to stuff you just don't get with plain-vanilla CSS such as mixins. 

I'm astounded by so-called "CSS experts" who criticize these tools without really having digged in and used them. Are they essential? No. If you like your own framework (you do have one of your own, right? A CSS framework is just a carefully defined library--everyone should be using one) then by all means, keep on using it. No one is forcing you to use other frameworks and I don't see people who are using frameworks telling CSS purists that they are "doing it wrong."

Criticizing frameworks from such a standpoint just reveals an insecurity as well as an ignorance. For example, the notion is laughable that a person would use a tool like Compass without knowing CSS. You realize, right, that a framework generally doesn't write all your CSS for you? You can still break out and write your own CSS within the context of most frameworks. In fact, if you don't know CSS you might get frustrated quickly.

For myself, I appreciate having a framework because it is already documented, tested by hundreds of other users, and I can apply my own classes and ids via Compass. If I need something that the framework isn't suitable for, then I'll code my own.

blocks|key|1717481|text|查看http://www.ez-css.org/。最简单、最轻量级的css框架之一。:)|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1717482|entityMap|0|LINK|mutability|MUTABLE|url|http://www.ez-css.org/^0|2|M|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

check out <a href="http://www.ez-css.org/" rel="nofollow">http://www.ez-css.org/</a>. one of easiest and lightest css framework to work on. :)

blocks|key|1717523|text|克雷格|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1717524|Compass就是你要找的:它允许你用你自己的名字重命名你的Blueprint+CSS类，比如"span-24“。它还通过变量和混合扩展了CSS功能。诚然，那些在没有检查Compass的情况下过早地判断框架的人是“没有抓住要点”。这有点像几年前有人告诉我们，我们在布局中使用CSS而不是HTML表格是没有抓住要点的。|1717525|-Matt|1717526|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Craig,

Compass is what you're looking for: it allows you to rename your Blueprint CSS classes like "span-24" with your own names. It also expands CSS functionality with variables and mixins. Truly, those that prematurely judge frameworks without having checked out Compass are "missing the point." It's sort of like those folks who told us years ago that we are missing the point by using CSS instead of HTML tables for our layouts. 

-Matt

blocks|key|1717565|text|看一下这个演示：http://www.richstyle.org/demo-web.php这个框架是基于“超文本标记语言标签就足够了”的想法。我认为可重用性是选择软件组件的最重要因素，包括web框架。对于web框架开发人员来说，你越是致力于标准，你就越能保证可重用性。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1717566|entityMap|0|LINK|mutability|MUTABLE|url|http://www.richstyle.org/demo-web.php^0|8|11|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Take a look to this demo:
<a href="http://www.richstyle.org/demo-web.php" rel="nofollow">http://www.richstyle.org/demo-web.php</a>
This framework is based on idea that "HTML tags should be enough".
I think re-usability is the most important factor for choosing a software component, including a web framework.
For web frameworks developers, the more you commit to standards, the more you guarantee re-usability.

Reading on another forum I've came across the world of CSS Frameworks. The one I've been specifically looking at is <a href="http://www.blueprintcss.org/" rel="nofollow noreferrer">BluePrint</a>. I was wondering if anyone else had come across CSS frameworks, suggest which is the best and if they are worth the effort?

What is the best CSS Framework and are they worth the effort?

我在另一个论坛上读到了CSS框架的世界。我一直在特别关注的是。我想知道是否有其他人遇到过CSS框架，建议哪个是最好的，以及他们是否值得付出努力？

问什么是最好的CSS框架，他们值得努力吗？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问什么是最好的CSS框架，他们值得努力吗？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问什么是最好的CSS框架，他们值得努力吗？
EN