Well, I guess it’s no secret I’m addicted to Apple! And I love wallpapers (who doesn’t?). Some time ago I posted 50 Apple desktop wallpapers, and I thought it was time for another post. So I went ahead and collected another 50 wallpapers.
Oh, and let us know which ones are your favorites in the comment section! Enjoy! 
If you’ve been following me on Twitter or this blog in the past couple months I’m sure you’ve noticed that I had a bad case of redesign-itis… I must have redesigned SpyreStudios something like 3 or 4 times in the last 6 months. Maybe more. You see, I can’t even keep track of how many times I did it. Ouch!
Why did I redesign so many times? Why wasn’t I happy with those previous designs? I’m done now, I’m sick of redesigning. I know many designers, like me, suffer (or used to suffer) from redesign-itis!
So what can we do to cure this, or at least treat it? Instead of just talking to myself, I figured my thought process could be of interest to some of you folks
I love inspirational articles and showcases of well-designed sites. The proof is right here on SpyreStudios, we’ve published many showcase and inspiration posts and I see no reason to stop. We can all use some inspiration from time to time to get our creative juices flowing, right?
But when is it too much? Here’s a quick way to help cure redesign-itis: Seek inspiration when you need some to get back on track or cause you don’t feel creative at all, but don’t let those killer designs you see everywhere drive you nuts and make you redesign your site ‘just because’, you probably don’t need to anyway.
Hey, you’ve worked hard to get your initial design up! Of course it’s possible you will get tired of it eventually, but don’t jump the gun and open up Photoshop just yet. Try realigning. Why not just change the color scheme a bit? Maybe realign only a portion of your site, say your sidebar or your comment section if you own a blog?
Try to figure out what works and what doesn’t. Don’t redesign because you want to, redesign because you need to, because you’ll get a better conversion rate, more subscribers or whatever else it is you’re after.
What has changed since your last design? Find the root of the problem and fix it. Seriously, how often in the last 5 years did Google redesign their homepage?
If you absolutely feel the need to redesign, make yourself a huge favor and don’t launch your new design right away. Let it sit for a while, wait a couple days, a week, or even a month.
When you go back to it you will either love it and want to go ahead and code it up or you’ll simply hate it. If that happens you’ll be happy you didn’t spend time coding it and making it all pretty for IE6 users.
Redesigning just to show off your skills is kinda pointless anyway.
Your current design isn’t bad, in fact it’s probably just fine the way it is! Why not just live with it and spend all that energy of redesigning on client’s sites or other more important projects that will earn you money?
Unless you’re not satisfied at all with your site’s results, there’s not need to redesign. And when you do redesign, it’ll make a much bigger bang and people will maybe talk about it more and comment on it.
Have a look around, study other sites, blogs and businesses in the same niche. When did they last redesigned their site? I don’t see big blogs like Smashing Magazine redesigning every couple months. Of course not!
Why not spend a couple hours researching sites in your niche and see how often they redesign, and what changes from month to month?
Many freelance designers work from home, that’s cool. But why not take a minute to ask fellow designers what they think of your layout before you start coding away? This could save you some major headaches down the road. Even better, why not work with another designer? Yes I mean partnering-up or even hiring someone to work with you on your redesign.
Oh and if you work with a team already and you got collective redesign-itis syndrome, maybe it’s time you start asking yourself some serious questions
While building a site for a client I had to figure out the best way to display additional navigation in a horizontal menu (and not make it look like it’s 1999 again), so I went ahead and started looking for some inspiration. I’ve found many sites that had drop-down and sliding menus and I thought you’d be interested in my findings.
Please let me know what you think in the comment section. Know of any really cool drop-down and sliding menus that I missed? Let me know!
Reading blogs and tutorials is pretty good, in fact it’s great! You can learn a lot by doing this, but actually seeing and hearing (video and/or audio format), is a whole different world.
I’ve gathered some resources and sites that produce audio and video content. Of course, most of them offer RSS and also iTunes subscription options. I personally like to download the podcasts and screencasts and play them on my iPod Touch (if download is made available). The sites are listed in no particular order.
Topics: Graphic Design, Photoshop, Tutorials 
Topics: Usability, User Experience 
Topics: Adobe, Photoshop, Illustrator, Tutorials 
Topics: Freelancing, Business, Work 
Topics: Opinion, Tips, Business, WordPress 
Topics: dConstruct, Conference, Web-Design 
Topics: Tutorials, Photoshop, Illustrator 
Topics: Web-Design, Opinion, Interviews 
Topics: Web-Design, Interviews 
Topics: Web-Design, Development, Tutorials 
Topics: Tutorials, CSS, HTML, Tips 
Topics: Web Services, Internet, Interviews 
Topics: Tutorials, jQuery, Javascript 
Topics: Tutorials, Development, WordPress 
Topics: Web-Design, Freelancing, Tips 
Topics: Development, Tips, Tutorials 
Topics: Typography, Interviews, Type Design 
Topics: Zend Framework, Tutorials, UI 
Topics: PHP, Tutorials, Tips 
Topics: Humor, Tutorials, Photoshop 
Topics: Photoshop, Tips, Tutorials 
Topics: Photoshop, Tips & Tricks, Tutorials 
Topics: Photoshop, Tutorials, Design, Tips 
Topics: Tutorials, Photoshop, CSS, HTML 
Topics: Web-Design, Questions & Answers 
Topics: Tutorials, Illustrator, Tips 
Topics: Internet, Blogging, WordPress, Twitter, Tips 
Topics: WordPress, Tips, Tutorials 
The grungy trend as been around for a while now. You can find a lot of pretty nice portfolio or other sites using a mach up of cuted paper, hand drawn element and various other stuff but it hasn’t been embraced by the e-commerce sector as much.
Their is a good reason for that of course. Grungy doesn’t always inspire trust to the eyes of lambda users and also tend better target young audience, less likely to buy.
With that said I found 10 e-commerce sites that use grungy in a very attractive way.
From:http://www.yoursiteisvalid.com/validnews/10-awesome-grungy-e-commerce-sites-1177.html
FROM:http://tech.yahoo.com/news/pcworld/20090721/tc_pcworld/ifchinagetsmicrosoftofficefor29whydontwe
In order to take a bite out of piracy, Microsoft sells copies of its Office Suite in China for just $29 dollars. I wonder how many copies Americans would have to pirate to get the same price? So much for the notion that “crime does not pay!”
I found the pricing information earlier today in a BusinessWeek story about how Microsoft is slashing prices to grab market share and fight off Google and the others that are giving away functionality Microsoft customers are used to paying for.
The magazine said Microsoft estimates 95 percent of all copies of Office used in China are illegal copies. Since the $29 pricing started in September, sales of Office have supposedly increased 800 percent.
This looks like a case of where crime pays big dividends. And, no, I am not suggesting for readers to pirate copies of Office in order to send Redmond a pricing message.
Still, we Westerners have been paying through the nose for Office for almost two decades. If anyone deserves a price break, it’s us–not the thieving Chinese. But, it seems that if you are a fast-growing market, lawlessness aside, Microsoft wants to cut you a deal.
I understand what Microsoft is doing and why. I am happy for anything that reduces software theft, but that doesn’t make me nearly as happy as a $29 copy of Office would.
This pricing is another demonstration of how Microsoft’s business model is under attack, especially in the consumer and small business space. Its enterprise business isn’t as solid as it used to be, either, as big corporate customers are remarkably happy with the software they are already using.
These changes haven’t caught Redmond quite as flat-footed as when Netscape first arrived on the scene, forcing Microsoft to Internet-enable products at warp speed.
The company has doubtless seen the current market turmoil coming for years, but had little reason to tip its hand. Microsoft clearly needs be more responsive with its pricing and find better ways to compete globally. I guess giving the Chinese $29 copies Microsoft Office is a part of this.
This is still more Microsoft angst we will just have to live with.
Industry veteran David Coursey tweets as @techinciter and can be contacted via his Web page.
From:http://ilovetypography.com/2009/07/20/web-fonts-%E2%80%94-where-are-we/
With all the talk about web fonts, I think it’s time I tried to outline the present situation. I’ve not attempted to do so before, owing to the complexity of some of the material, and the speed at which things are moving.
Web designers are generally not interested in technical specifications, TrueType Hinting instructions, and extended OpenType permissions tables. They have one pressing question: when can I use font x in my web pages? Today, in Atlanta, Georgia, at TypeCon 2009, the faithful met to talk about Web Font Embedding: The New State of the Debate. At the foot of this article, I’ve included highlights from the twitter feeds of @typographica (Stephen Coles) and @splorp (Grant Hutchinson). Many thanks to them for the great job they did in reporting.
Web designers want more options, they want more fonts. sIFR, Cufón, and numerous other replacement techniques permit web designers to go beyond the so-called web-safe palette of fonts. However, all those techniques are, fundamentally, hacks. Moreover, their practical use is limited to headlines, or short bursts of text.
Foundries do not want their raw (.ttf and .otf) fonts uploaded to Web sites where they can easily be downloaded (stolen). @font-face permits linking directly to the raw font file. When I say raw, I mean an uncompressed, unprotected font file, just like you’d find in the font folder on your computer. [see also Stephen’s comment below.]
Downloading those font files would be as easy as downloading an image. For obvious reasons, foundries don’t want that. In fact, no-one wants that. Here, the music industry comparison doesn’t work. The type industry is in fact, not an industry; it’s not regulated by any kind of governing body, and the industry comprises thousands of small players — the vast majority of type foundries have a staff of one. Font piracy hurts them.
Way back in 1997, Microsoft developed its proprietary EOT (Embedded OpenType Format — basically a compact version of OpenType, that permits sub-setting), that only supported Internet Explorer. Hoping for widespread adoption, Microsoft opened it up for all, and in 2007 submitted their EOT proposal to the W3C (for inclusion in CSS3). Later that year, the proposal was rejected, for, among other reasons, security. In 2008, the proposal was resubmitted:
The Embedded Font Format (EOT) was developed by Microsoft to enable OpenType fonts to be linked to web pages for download to render the web page with the font the author desired. This appendix specifies the format of the .EOT file so that User Agents can download, extract and temporarily install fonts of the .EOT file suffix that are included in the @font-face definition of a CSS style sheet. Example pages can be found at the Microsoft Typography site on Font Embedding for the Web.
Downloaded fonts are only temporarily installed on the user’s machines for use by the particular web page while the page is actively being used.
— source
I once heard EOT described as DRM icing on an OpenType cake. Once EOT was associated with DRM (and whether it’s strictly DRM is debatable), then EOT was doomed. For all the technical features of EOT, see the W3C’s Embedded OpenType (EOT) File Format. So what happened to EOT? To cut a very long and complicated story short: it didn’t gain the necessary support from foundries. [I was wrong; see Richard Fink’s comment, & Thomas Phinney’s comment.] Remember, the W3C is not mandated to push these formats through, to run around drumming up support. The consensus must come from the foundries, and from distributors.
Recently, two highly respected type designers, Tal Leming & Erik van Blokland (they are programmers too) proposed an alternative to EOT. It’s not proprietary, and its implementation is relatively uncomplicated. Via twitter, H&FJ described the .webfont proposal as:
Smart, compact, open, elegant, forward-thinking, realistic. — source
Basically the .webfont font is a compressed file (perhaps .zip), comprising two files (the actual font data, plus info.xml). The embedded permissions or meta data are then read by supporting browsers, that could determine whether the font should be downloaded and displayed.
With such huge support from type foundries and many in the type community (even TypeKit supports it), the webfont proposal could well be a winner. So, we’ll all be using .webfont by this time next year, right? No. First, the W3C needs to be convinced that the majority of type vendors support the .webfont format. Then, and only then, will its slow wheels begin to turn. Then the browser vendors need to come aboard the .webfont ship, and build support for this new format into their respective browsers. Though the .webfont format is, in my opinion, the best proposed solution, don’t hold your breath. It will be years before we can start to link to .webfont files in our CSS.
If you’re not already confused, then let me introduce you to David Berlow’s (The Font Bureau) Permissions Table for OpenType proposal. (Technical specification here). Without getting too technical, I think Berlow’s proposal can be summed up thus: embed ‘meta data’ in the OpenType font file. These data will be information about the permissions for which the font is licensed. For example, the permissions table (not separate from the font file, but embedded) would include information about permitted use; e.g. whether it can be used on a web site — previewable for web.
The proposal does not require any change in font format; it only requires that more data (about permissions) be stored in the font file. Some have pointed out that its greatest strength — XML to describe the permissions — is also its greatest weakness. What’s to stop users from opening font files and editing the permissions? Another of its obvious strengths is that it does not require any kind of wrapper, and can be used with @font-face, which will soon be supported by most, if not all browsers.
While we’re waiting on .webfont et al., there’s Typekit, a simple solution that involves web-only font linking licenses. Basically, a font file, or a subset of the font is stored on a third-party server.
You pay a subscription to Typekit to rent (not buy) the font. The rest is simple enough. Include a call to a JavaScript file (that handles delivery of the font, I guess), and simply include your ‘subscription font’ in your fontstack, like:
#introduction .one p {
font-family:"skolar-1","skolar-2","Palatino","Georgia","Times","serif";
}
Great to see David Březina’s Skolar on screen. Go to for a beautiful web to see Typekit in action. Typekit is still in beta, but it looks very promising.
One of the most exciting aspects of the Typekit solution is best described by Thomas Phinney:
…the most interesting thing about Typekit & Kernest is they provide a service, a subscription, a brand new model for font licensing. — source
We need consensus. They only way a consensus can be reached is through compromise. There exists no governing body of type, so there can be no democratic vote. The closest thing we have to consensus is the list of Foundries that support the present .webfont proposals.
Despite concerns about the security of the .webfont format, most of the larger and important foundries have come out in favour of the .webfont proposal; and that’s what really matters. See @typegirl’s Most of the important foundries are supporting #webfont list.
If no consensus is reached then .webfont will forever remain a proposal. If there is consensus, then still at the very soonest we’re looking at .webfont in our browsers by 2011-2012 at the earliest. @splorp sums it nicely in <140:
We just need to have one #webfont initiative to start solidifying. That’ll help. Right now, we’re tip-toeing around multiple jars of jelly.
Regardless of which format or proposal actually wins the fight, type designers are going to be very busy indeed. Most fonts are not optimised for on-screen viewing, so, if they are to compete with those that already are (e.g. Verdana), then they have lots of work ahead of them. (Type Designers have the joyous prospect of mastering TrueType hinting instructions).
In my opinion, EOT is as good as dead. [cf. Tiffany’s comment below; and Thomas Phinney’s.]
EOT may be dead, but Ascender Corporation is proposing EOT Lite — think of it as a less restrictive implementation of the original EOT. In what way is it less restrictive? Well, the new EOT Lite does away with URL binding (limiting use to a specific domain or URL), and proprietary compression technology (MTX compression) — the two principal objections to the original EOT specification. Ascender hopes to have it up and running within months. [added July 21, 2009].
Will .webfont ever come to our browsers? Who knows. But with the backing of the majority of influential type foundries, it could. In the meantime, TypeKit appears to be a viable, workable solution. And Typekit is now. I know I’ve omitted mention of other proposals like EOT Lite or Kernest from Ascender Corp., etc., but this article is intended as a non-technical, brief [laughs] overview. If you have questions or comments, then please leave them below.
[Update (July 21): fontdeck joins the fray.]
_______________
Highlights from TypeCon 2009’s Web Font Embedding panel discussion, courtsy of @splorp and @typographica
Eleven font nerds and a microphone. @typographica is live tweeting from the huge #webfont panel discussion this morning.
Audience unrest already. Only one web designer on a panel of 11. Via @nicewebtype — @splorp
Using a service like @typekit or @kernest is similar to buying/selling faces through distributors like @myfonts.… except that you’re not renting the typeface via a modified license. It’s not yours to use perpetually. — @splorp
@opentype They don’t want fonts that users currently have to be used as web fonts. Should be a separate license and product. — @typographica
“… the thinness of the wrapper is disturbing …” — John Hudson on the .webfont format. — @splorp
“Any new font format we come up with … takes years to be implemented.” — Bill Davis, Ascender — @splorp
Dewitt: Foundries, if you don’t have a license that addresses the web, do it. Have a position that allows for some of these things. — @typographica
Bill Davis — “I think we’re on the cusp of something happening very quickly here …” That’s because web designers are frustrated. — @splorp
There’s a big ostentatious EOT Lite petition at the door. Presumably placed there by Bill Davis. Waiting to hear his invitation to sign it. — @typographica
John Hudson of Tiro Typeworks is explaining @typesupply’s .webfont format. “… super easy to implement … ” — @splorp
Mason: The W3C doesn’t lead, it follows. It takes steps once groups find consensus. — @typographica
Hudson explains the problem with a new format: IE is slooooow. IE users are slooooow to update. (Could take years for .webfont to be real.) — @typographica
Bill Davis — “I think we’re on the cusp of something happening very quickly here …” That’s because web designers are frustrated. — @typographica
@_Baylink I don’t think that’s the case. The foundries aren’t terrified, they’re cautious. None of these solutions will ‘eliminate’ misuse. — @splorp
Thomas Phinney: URL binding was a non-starter because vendors don’t want to enforce that. Worse, users might be open to DMCA liability. — [see Thomas Phinney’s comment for clarification.]
Basic Q. What happens when any of these schemes don’t work? A. You’ll get the fallback font. Whatever specified in CSS, what you see today. — @typographica
Verdana is still a pretty good typeface. — John Hudson — @splorp
Gabrowitsch (F[ont]F[ont]): We support .webfont and “EOT Lite, Medium, or whatever”. As long as there’s no chance to use existing fonts on the web. — @typographica
Relevant commentary from Tim Brown @nicewebtype: Type sellers, web fonts, and Typekit. link — @typographica
Typekit is willing and excited to incorporate .webfont proposal in their product. — @typographica
Final question from moderator: how urgent is it?
A. Garrick Van Buren (Kernest): We’re 10 years behind.— @typographica
Hudson: You can say yes to .webfont or EOT. It’s not an either or situation. But foundry weight behind one format will influence browsers.
End. Applause. Matthew Carter first to stand. Maybe wants out of here. — @typographica
Looks like everyone is walking out without batting an eye at the giant petition. Not sure the pen has been touched. — @typographica
From:http://www.sitepoint.com/blogs/2009/07/06/site-accessibility-tools/
When you design any web site, one of your first goals is to make sure you get as many visitors as you can, but have you checked the true accessibility of your site? Can a color blind person read it? Are all of your scripts cooperating? Your colors may look nice together, but is the contrast different enough that it is all legible? Well, those questions are exactly what these 12 tools are designed to help you answer, and it certainly may never be a bad idea to run more than one to make sure they are all telling you the same thing.
One caveat to this list, while these tools are helpful and will help you spot some problems, never trust them to be the ultimate authority, but more of a starting point on your road to the smoothest running site you can build.
ACTF aDesigner: An extension for the open source Eclipse development platform, it is built specifically to test for the accessibility of the visually impaired. Unfortunately, it’s only available for those running Windows XP and above.
Adobe Dreamweaver CS4 accessibility: For designers who use Adobe’s Dreamweaver CS4, you’ll find a validation tool built right in that allows you to choose what to test at any time and get a full report on any errors that it may find.
Contrast Analyser: Not only is it difficult to choose which colors you want to use with a site, but then you have to make sure they work together when it comes to readability. Colour Contrast Analyser will let you know the difference between two colors, and it can also be set to help you determine if people with visual impairments, such as color blindness, will be able to read it.
Cynthia Says: Cynthia Says is a product from HiSoftware that allows you to enter your web site address in to the sight and get a report on how it complies with Section 508 and WCAG-Priority 1, 2 and 3.
Firefox Accessibility Extension: Created by the Illinois Center for Information Technology and Web Accessibility (iCITA), this Firefox toolbar includes a large suite of tools to test numerous aspects of your site for accessibility by those with disabilities. Includes testing for text, scripting, styles and a whole lot more.
Functional Accessibility Evaluator: The Functional Accessibility Evaluator gives you a report on many aspects of your site and then gives you a color coded results page with a nice overview of everything you need to know. If you want more information you simply need to click on the category to see the detailed comments.
Fujitsu Web Accessibility Inspector: The Fujitsu Web Accessibility Inspector focuses on checking the build of your page as it may appear to elderly and visually disabled people. The software has to be downloaded to your system, Max OS X or Windows, and then you can point it to a local file or a web site and it will then generate a report that is almost too long, noting every aspect of your file. When we attempted a full screenshot it came out to over 924 MB in size, so it is a bit lengthy.
IBM’s Rational Policy Tester Accessibility Edition: A Windows-only solution for testing your site for accessibility by those with disabilities. This is a paid solution and there was no easy link to the cost, but it is likely not cheap with the IBM brand name attached to it.
Truwex Online 2.0: The Truwex Online 2.0 tool checks a range of accessibility options such as section 508, WCAG levels, privacy, broken links and so on. Simply go to the page, enter your URL, check the boxes for the items you want checked and it generates reports shortly after that.
Vision Australia: Vision Australia is a coalition of people working to make sure people with all forms of vision problems have equal access to life as anyone else. They offer two toolbars for Internet Explorer and Opera to test how your site will work for someone with impaired vision.
WAVE: WAVE is produced by WebAIM which is dedicated to making sure sites are accessible in as many languages as possible. Simple enter the address of the site, upload a file or enter a code snippet and see all of the elements identified. Plus, you receive feedback on the placement and identification of each element. There is also an option for using a Firefox toolbar or installing WAVE in browsers and web pages.
Web Accessibility Toolbar For Opera: A method for quick access for Opera users to some of the most used web accessibility tools from the Paciello Group. Not all items will be functional while you are offline as they need to access scripts and tools located on the WAT-C servers, but if you have Internet access you’ll have everything at your fingertips.
From:http://www.webdesignbooth.com/9-useful-javascript-syntax-highlighting-scripts/
Syntax highlighting is very important especially when we want to show our code example on the blog. By enabling the syntax highlighting on the blog, readers can read the code blocks easier.
There are a lot of free and useful syntax highlighting scripts around us. Most of the scripts are written using Javascripts, though some of them are powered by other programming languages such as Phyton or Ruby.
Today, we are going to look into 9 Syntax Highlighting Scripts that powered by Javascript.
I believe this is the most common syntax highlighting script used by most of us. It supports a lot of different languages and you can easily create new “brush” for your language if it is not supported by default.
SHJS stands for Syntax Highlighting in Javascript. It uses language definations from GNU Source-highlight and support a lot of different programming languages. SHJS has been tested and support major browsers sych as Firefox 2 and 3, IE 6 and 7, Opera 9.6, Safari 3.2 and Chrome 1.0.
beautyOfCode is a jQuery plugin for syntax highlighting. It uses the SyntaxHighlighter scripts by Alex Gorbatchev and makes it more XHTML-compliant.
Chili is a jQuery code syntax highlighting plugin. It comes bundled with recipes for a lot of languages and supports many configuration options.
Lighter.js is a free syntax highlighting plugin for MooTools. Using lighter.cs is as simple as adding a single script to your webpage.
highlight.js is easy to use and supports a lot of programming languages. It has some plugins for easily integrations to other CMS, forum or blog.
DlHighlight is a simple syntax highlighting scripts that supports only 4 programming languages: JavaScript, CSS, XML, HTML.
Google Code Prettify a Javascript module and CSS file that allows syntax highlighting of source code snippets in an html page. It is the scripts wich powers code.google.com.
JUSH is yet another jQuery syntax highlighting plugin which supports different programming languages such as HTML, CSS, PHP, PY and SQL.
Come usare oggi i CSS3 con la sicurezza di creare effetti visibili su tutti i browser? Semplice! Nascondendoli in jQuery! In questo modo il vostro problema sarà solo sapere se i browser supportano jQuery. Oggi vi mostriamo una lista utile per imparare ad usare i CSS3 tramite jQuery ma prima iniziamo con qualche esempio per capire come usare i CSS3 in jQuery dopo.
How to use CSS3 today with safety to create visible effects in all browsers? Simple! Hiding it in jQuery! In this way your problem is just to know if the browser supports jQuery. Today we show yuo a useful list to learn to use CSS3 via jQuery but let’s start with some info and examples about the CSS3 code to understand how to use it after with jQuery.
#backgrounds-box {
background: url(top-backgroundg.png) top left no-repeat,
url(bottom-backgroundg.png) bottombottom left no-repeat,
url(middle -backgroundg.png) left repeat-y;
padding: 35px;
}
b { text-shadow: 5px 5px 5px #666666; }
#rounded-corners-box {
-moz-border-radius-topleft: 8px;
-moz-border-radius-topright: 8px;
-moz-border-radius-bottomright: 8px;
-moz-border-radius-bottomleft: 8px;
-webkit-border-top-left-radius: 8px;
-webkit-border-top-rightright-radius: 8px;
-webkit-border-bottom-left-radius: 8px;
-webkit-border-bottom-rightright-radius: 8px;
}
.div-name { background: #333333; opacity:0.8; width: 380px; height:70px; }
opacity: 0.8 is equivalent to 80% value.
This jQuery plugin will easily create beautifully rounded corners. No images or obtrusive markup necessary.
Works with iPhone. Chrome, Firefox, Safari 2+, Opera 9.0+, Internet Explorer 6+
jQuery Plug-in to make rounded corners on your DOM objects using canvas element. Tested in IE7 and FF3.
CSS3 draft introduces, amongst many properties that will change a Web designer’s life, one that could be terribly powerful: border-image.
Discover what it can do today.
The Background Layers plugin reduces the amount XHTML you need to write simply by adding a few lines of JavaScript, making your code much less cumbersome. The concept is similar to the use of layers in Photoshop, one background image on top of another.
This plugin creates soft drop shadows behind page elements, including text and transparent images.
With this tutorial you can add text-shadow effects to Internet Explorer in simple way.
It allows you to define a gradient fill and have an element filled with a gradient. You can set the direction of the gradient (right-left or up-down) and the opacity of the gradient easily.
An easy jQuery tutorial about the tecnique to realize rounded corners with jQuery.
The project aims at providing web designers with a way to use the W3’s CSS Template Layout Module today. As a jQuery plug-in, the script parses a given set of CSS rules and displays the content as indicated in the specification.
Options include the ability to select the CSS parsed, as well as an optional prefix to use for the CSS rules. Specifying a prefix allows style rules that are interoperable with a possible future browser implementations.
By combining the CSS3 Box Shadow and Rotate properties, this effect is relatively easy to create. When dragging a polaroid around, you’ll see the shadow. When it’s placed down, it’s rotated to the left or the right (random).
The plugin called jSlickmenu, creates, well, slick menus with jQuery. Combined with some great CSS3 features likes rotation and shadows, this plugin can really lift up your design. It’s fairly easy to use, highly customizable and pretty cool (and fun!) to see.
Links
Introduction to CSS3 (W3C)
From:http://www.webair.it/blog/2009/07/09/mixing-css3-and-jquery-how-to-css3-effects-via-jquery/
about author ..read more ?
Subscribe to our feed and get all the latest news from pdf search engine in your newsreader.
Please look for a later launch.
