Suggestions on menu structure

[theducks]

Originally Posted by user_none

How are two editors who's sole purpose is editing documents not a document centric app?

I see his point.

EPUB is the document,

but most of Sigil deals with a Section at a time.

Other than Save and Validate, only S&R in Code view deal in a near document wide mode (S&R excludes the NCX and OPF in all mode, thus not document wide )

[user_none]

I made a sub menu for new. It has new book, new section and new stylesheet as actions. Either way you are creating something new. I'm looking at an EPUB as the equivalent as a programming project. Meaning that we are manipulating a series of related files.

[theducks]

You have the deciding vote

[daubnet]

Originally Posted by user_none

I made a sub menu for new. It has new book, new section and new stylesheet as actions. Either way you are creating something new. I'm looking at an EPUB as the equivalent as a programming project. Meaning that we are manipulating a series of related files.

I believe that is an unfortunate choice. From a user's point of view, neither command creates a file. They create a "section" and a "stylesheet", which are part of the content.

I do understand that they technically are files inside a ZIP. But by the same line of reasoning "Insert Chapter Break" technically is "split HTML file". If it were a programming environment, "File -> Split" would probably be appropriate, but Sigil is an EPUB editor, so the focus should be on the effect it has on the book: a new section is created, and not on technical operations that involves.

Either way, having it in the menu bar *at all* is much better than the way it is currently hidden in context menus.