Quote:
Originally Posted by Freeshadow
Tex, the day Jon will accept that other people may have tastes and opinions differing from his own and thus stops shoving down his personal preferences down other peoples throats disguised as absolute truths is also the day when pigs 'll fly, crossing the frozen pits of hell.
|
Well it reminds me a lot like debates. You have both sides, who won't really convince the other side that they are correct, but the main purpose is to have the discussion so that the AUDIENCE can see/read/hear both sides and then make an informed decision.
In the case of a forum, I always like to talk about the Lurkers, and those who DON'T post, but still absorb/learn a lot of information from what is said.
This is one of the reasons why the ereaders all those override settings on devices. So everyone can, with the click of a button, change the line-spacing, paragraph spacing, alignment, font sizes, colors, margins, etc. etc.... to whatever THEY prefer (or maybe NEED, in the case of someone with a reading impairment/disability).
And this is one of the reasons why I LOVE ebooks over physical books.
I would just say, probably THE MOST important thing though, is to have CLEAN and CONSISTENT code, so then it is easy for someone to go in there and tweak it if needed... for example, don't have an insane amount of spaghetti code + overlapping CSS + a ton of classes overriding the same stuff + a ton of worthless class names (calibre##, block##, p##, no-style-override-#, ...).
For example, I showed off some InDesign code Before/After cleaning here:
https://www.mobileread.com/forums/sho...20&postcount=6
Sure, having tons of hideous code in the backend might still LOOK ok on the surface, but the problems really start to come when you want to do anything else with it.
Spaghetti code will come to haunt you in the NEXT ebook format, when you want to convert these spaghetti code EPUBs into format X..... and things will go wrong, and you will spend a lot of time/money trying to fix the problems that arose because of previous horrible code. Make it clean/consistent NOW, and save yourself the future headaches.
Side Note: Also, clean/consistent code means easy to transfer to other formats as well... for example, here is some images of one of my EPUB->LaTeX->PDF conversions (comparison of Archive.org scan + LaTeX PDF):
https://www.mobileread.com/forums/sho...6&postcount=58
Easy peasy, lemon squeezy!
