Quote:
Originally Posted by exaltedwombat
Have you ever experienced an eBook that you felt responded particularly slowly?
|
Most definitely...but they were ones that were immense...50mb or so (if I remember correctly) and filled with a ton of junk code (bloat). After I cleaned it up it was a much more manageable size - just under 2mb - and was quite spry.
As far as extra css files slowing it down: Yes. Any extra action that the app has to take will slow it down...be it from opening extra css sheets or wading through bloated inline styles/spans...but we're talking micro-seconds here for opening a css sheet. There would need to be a ton of css's linked to each html to make it noticeable. In this particular case having a few extra css sheets shouldn't slow it down noticeably because they are only referenced on the few pages that need them and would only be accessed by the app when those html files are opened.
Having said all that, I find that having all my css on a single sheet makes it easier for me to keep myself organized. I would get confused if there were multiple sheets, and possibly different sheets using the same names. *shudder*
I keep all of my standard css at the top of the sheet and then book specific styles at the bottom where they would override the standard style higher on the sheet. After I'm done editing, I use the "Delete Unused Stylesheet Classes" tool to...um... delete unused stylesheet classes and leave my CSS sheet as tidy as possible.
note: when using this tool carefully check the list before deleting - it sometimes doesn't pick up on pseudo-elements being used properly.