Group items tagged

"FILES screen.css - CSS for screen print.css - CSS for printing ie.css - some corrections for IE "

According to Yahoo!'s Exceptional Performance Team, 40% to 60% of Yahoo!'s users have an empty cache experience and about 20% of all page views are done with an empty cache (see this article by Tenni Theurer on the YUIBlog for more information on browser cache usage). This fact outlines the importance of keeping web pages as lightweight as possible. Improving the engineering design of a page or a web application usually yields the biggest savings and that should always be a primary strategy. With the right design in place, there are many secondary strategies for improving performance such as minification of the code, HTTP compression, using CSS sprites, etc. In terms of code minification, the most widely used tools to minify JavaScript code are Douglas Crockford's JSMIN, the Dojo compressor and Dean Edwards' Packer. Each of these tools, however, has drawbacks. JSMIN, for example, does not yield optimal savings (due to its simple algorithm, it must leave many line feed characters in the code in order not to introduce any new bugs). The goal of JavaScript and CSS minification is always to preserve the operational qualities of the code while reducing its overall byte footprint (both in raw terms and after gzipping, as most JavaScript and CSS served from production web servers is gzipped as part of the HTTP protocol). The YUI Compressor is JavaScript minifier designed to be 100% safe and yield a higher compression ratio than most other tools. Tests on the YUI Library have shown savings of over 20% compared to JSMin (becoming 10% after HTTP compression). Starting with version 2.0, the YUI Compressor is also able to compress CSS files by using a port of Isaac Schlueter's regular-expression-based CSS minifier.

In simple terms, CSS preprocessing is a method of extending the feature set of CSS by first writing the style sheets in a new extended language, then compiling the code to vanilla CSS so that it can be read by Web browsers. Several CSS preprocessors are available today, most notably Sass2 and LESS3.

I have revisited adding Yui compressor into my work's ant build script to minify JS and CSS scripts. The current jar was yuicompressor-2.3.5.jar . It took a lot of playing around but I finally stumbled on how to get it to work. Here is the snippet for the yuicompressor. I had to jump through a couple hoops like overriding the current js/css scripts with the optimized js/css scripts. I'll release a full working copy in a zip, you can run against your webroot. We achieved an average 18% compression rate for all our js/css files.

Did you know Twitter provides you with a list of CSS classes that you can use to change how your tweets look on your website? In this tutorial, I show you how to dynamically style a listing of your Twitter Tweets using custom CSS.

OM2 Core DOM2 Events DOM2 HTML DOM2 Range DOM2 Style (getComputedStyle, …) DOM2 Traversal (NodeIterator, TreeWalker) DOM2 Views (defaultView) ECMAScript HTML4 (, , …) HTTP (Content-Type, 404, …) Media Queries Selectors (:lang, :nth-child(), combinators, dynamic changes, …) XHTML 1.0 CSS2 (@font-face) CSS2.1 ('inline-block', 'pre-wrap', parsing…) CSS3 Color (rgba(), hsla(), …) CSS3 UI ('cursor') data: URIs SVG (SVG Animation, SVG Fonts, …) When taking the test, you should use the default settings of the browser you are testing. Changing the zoom level, minimum font size, applying a fit-to-width algorithm, or making other changes may alter the rendition of the test page without this constituting a failure in compliance. The Acid3 test measures some performance characteristics. The test does not attempt to make any comparisons or judgments as to the performance of any hardware used, and should not be used as a hardware benchmark. If the test is run on a slow computer or device, it may run slowly or not smoothly and this does not imply non-conformance.

This is a nice collection I've put together of both online CSS web applications and desktop applications to assist the web developer with his/her project. Both the CSS veterans and beginners should find these tools useful and at least worth a bookmark or quick download.

Compare Ninja | HTML & CSS Comparison tables tables html css comparison tool table compare

Very clear CSS tutorial with good examples

120 Excellent Examples of CSS Horizantal Menu

TweetDeck v0.25 Integrates Facebook & Twitpic Previews - TweetDeck is a personal browser used to stay in touch with the latest happening around us and connect you with your contacts across Twitter, Facebook and more. TweetDeck v0.25 recently released..." />

Disable YouTube's related videos With a Simple Hack Code - YouTube added the feature "related videos" wayback in 2007. Iam sure every YouTube user come across with this feature. Once the video completes playing, will displays a list of related videos..." />

What is font stack in css Font stack is creating a list of font......

"animate.css is a bunch of cool, fun, and cross-browser animations for you to use in your projects. Great for emphasis, home pages, sliders, and general just-add-water-awesomeness"

"A year ago we wrote a number of articles devoted to the PSD-to-HTML/CSS conversion market (which afterwards were collected in the e-book "Introduction to PSD-to-XHTML Services: Consumer Guide"). It's a good time now to analyze changes in the Design-to-HTML field: what's new, what tendencies have a positive or negative impact on customers."

Response to marbux comments.

# See also my comment on the same web page that explains why HTML 5 is NOT it for document exchange between web editing applications. . - comment by marbux # Response to marbux supporting the WebKit layout/document model. Marbux argues that HTML5 is not interoperable, and CSS2 near useless. HTML5 fails regarding the the interop web appplications need. I respond by arguing that the only way to look at web applications is to consider that the browser layout engine is the web application layout engine! Web applications are actually written to the browser layout/document model, OR, to take advantage of browser plug-in capabilities. The interoperability marbux seeks is tied directly to the browser layout engine. In this context, the web format is simply a reflection of that layout engine. If there's an interop problem, it comes from browser madness differentials. The good news is that there are all kinds of efforts to close the browser gap: including WHATWG - HTML5, CSS3, W3C DOM, JavaScript Libraries, Google GWT (Java to JavaScript), Yahoo GUI, and the my favorite; WebKit. The bad news is that the clock is ticking. Microsoft has pulled the trigger and the great migration of MSOffice client/server systems to the MS WebSTack-Mesh architecture has begun. Key to this transition are the WPF-.NET proprietary formats, protocols and interfaces such as XAML, Silverlight, LINQ, and Smart Tags. New business processes are being written, and old legacy desktop bound processes are being transitioned to this emerging platform. The fight for the Open Web is on, with Microsoft threatening to transtion their entire business desktop monopoly to a Web platform they own. The Web is going to be broken. There is no way of stopping Microsoft at this point. What we can do though is focus on Open Web solutions that are worthy alternatives to Microsoft's proprietary push. For me, this means the WebKit layout/document model supported by Apple, Adobe and Google. ~ge~

A CMS expert argues for HTML over XHTML, explaining his reasons for switching. Excellent read! He nails the basics. for similar reasons, we moved from ODF to ePUB and then to CDf and finally to the advanced WebKit document model, where wikiWORD will make it's stand.

"A full featured and beautiful CSS framework which originally combined the best of Blueprint, Tripoli (hence the name), Hartija, 960.gs, and Elements, but has now found a life of its own."

Best Css Loader For Front-end Developers- Gscode