Donna Jones wrote:
can someone direct me to a good article(s)/resource(s) that discuss
various ways of importing, linking css files and talks about
advantages/disadvantages.
This is ususally covered in the first chapter of any good CSS book. One
of the most important reasons that people use one or the other is
because the earlier browsers (R4 and earlier) don't understand @import.
This makes @import a natural filter for R5 and later browsers. Put the
styles for R4 browsers in a linked style sheet, then override them for
later browsers in @imported stylesheets.
Thanks Bob. The reason I asked is because I'm taking a class and the first
week we used the method you described above and which I'd recently started
using anyway. The second week we used a different method. We linked to
one file, say called basic.css, but at the top of that file we used the
@import statement to "read" the more extensive styles. I couldn't, and I
guess I still can't, figure out any reason for learning both methods. If
I'm understanding they reverse the order in which the cascade is "read" and
, in my mind, just makes it confusing. I was trying to find out if there
was a more substantial reason to use the second week's method. The teacher
just says, "well, its another method". and, I'm too polite to say, "well,
what's the point?" and maybe thinking there is a "point" that I just don't
get.
any other thoughts on this would be appreciated.
Cheers All!
Donna
--
Donna Jones
West End Webs <http://www.westendwebs.com/> 772-0266
______________________________________________________________________
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
