Thread: Robustness
View Single Post
Old 04-09-2012, 02:54 PM   #81
JimLL
Cynic
JimLL can understand the language of future parallel dimensionsJimLL can understand the language of future parallel dimensionsJimLL can understand the language of future parallel dimensionsJimLL can understand the language of future parallel dimensionsJimLL can understand the language of future parallel dimensionsJimLL can understand the language of future parallel dimensionsJimLL can understand the language of future parallel dimensionsJimLL can understand the language of future parallel dimensionsJimLL can understand the language of future parallel dimensionsJimLL can understand the language of future parallel dimensionsJimLL can understand the language of future parallel dimensions
 
Posts: 75
Karma: 51078
Join Date: Feb 2012
Device: Kindle
Quote:
Originally Posted by Toxaris View Post
I fully disagree. People who are making books commercially should stay far away from programs like Jutoh. The quality of those programs is not just up to par for commerce.

Again, the programming you suggest is NOT trivial as various people, including me, have told you time and time again.

I really recommend reading up on the ePUB format and learn at least basic HTML/CSS. If you don't want to, fine. However, then Sigil is not for you and you should stick to Atlantis Word Processor or Jutoh.
OK, fine. Disagree. Jutoh is not for commercial operations. But it still costs too much for us fixed income folks. (Hmm. You got something against fixed income folks?)

As for reading up and learning, it's not a matter of wanting to, altho folks always seem to assume a poster they disagree with is lazy. I passed all chance of reading up and learning when the stroke hit 25 years ago. My short term memory is all but gone. Reading up sticks for about 2 minutes. Learning a new system is just not in the cards.

As for trivial coding, I've coded saves and it IS trivial unless you want to tie it in with all sorts of other stuff. I suggested auto saves. That would be trivial. You put the HTML filename in a variable (that's probably already done). You put on a timer. You save file by name. Trivial.

Even if you save it on keyboard input all the IF code about whether something has gone wrong or not isn't needed. Just tie the routine to a toolbar, watch for the keypress and do the save. My memory may be short, but I'm not stupid. It's still trivial, and it wouldn't damage ANY of the people who declare it would be an awful, horrible, terrible thing to do. It's just a button on a toolbar, for crying out loud. How is that going to damage a user?

Of course if you WANT it to be complicated so you can argue against it...
JimLL is offline   Reply With Quote