-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Many things. Still not correct. Subject to change.
- Loading branch information
Cecil
committed
Dec 15, 2016
1 parent
bb4c509
commit 386ad06
Showing
3 changed files
with
143 additions
and
44 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
386ad06
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is ebook.rb asking for a TOC filename? I would imagine ebook.rb is just a reader, not building anything. Why wouldn't we have a publish.rb to do those tasks and then ebook.rb is just the reader?
386ad06
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps ebook.rb should be named ebook-builder or ebook-publisher since it's purpose is to guide the 'author' into to creating and modifying the .yaml . As a GUI, yaml builder, it need to know which documents are 'naviigation' (those [[fun things]] ) and which are Content. Don't view the ebook requirements from the Shoe Manual and your proof on concept. Markdown and kramdown are much broader that what the Shoes Manual uses.
Since the important script is ebook_help.rb using a proper shoes_ebook.yam, l it really doesn't matter what the GUI builder script names are since anyone that gets that deep in the weeds would be writing Ruby code to fix things and we know how many are willing to do that. If you run the ebook code you'd learn you only have to suffer the ask_file dialog once.