Home : Products : Gossamer Links : Discussions :

Products: Gossamer Links: Discussions: Re: [brewt] glinks template feedback: Edit Log

Here is the list of edits for this post
Re: [brewt] glinks template feedback
Hi.

Question.
If there are too many places to override then:

Remove the core.css path altogether from the header and just operate with custom.css (copied and edited version of core.css). Yes on upgrades, one can compare and see the changes coming in (as i always have the pre-upgrade core.css in form of unedited variables in custom.css). With a copied core-->custom.css i also have the original core.css effectively to compare with the new core.css which comes with the upgrade. if it's a core+custom.css combination, then post upgrade, there is nothing available to see what was their in pre upgrade core.css I could be wrong, but just my opinion as when it's an online upgrade, i wouldn't bother downloading the tgz to local disk (unless it becomes mandatory to do so when versions are changing as i am not clear on what happens with update feature with version change)

Additionally from performance point of view if core+custom = 13+5 =18K
Wouldn't it be better just to have 13K of custom.css and remove core.css from the header altogether. Otherwise everytime one hits ctrl+f5 one would have 18 K of css there as compared to only 13K

Thanks
HyTC
==================================
Mail Me If Contacting Privately Is That Necessary.
==================================

Last edited by:

HyperTherm: Mar 16, 2005, 1:17 PM

Edit Log: