empty module in a book makes the workflow simpler for now. otherwise a
bunch of edge cases must be dealt with. we would need a bunch of training
wheels for authors that will need careful ui.


On Thu, Oct 10, 2013 at 3:45 PM, Philip Schatz <notifications@github.com>wrote:

> In scripts/gh-book/opf-file.coffee:
>
> > @@ -108,6 +147,22 @@ define [
> >        @_localAddedItems[model.id] = model
> >
> >      _save: ->
> > +
> > +      # this is a new book, set some default elements
> > +      if not @navModel
> > +        #create the default nav file
> > +        @navModel = new XhtmlFile
> > +        @navModel.set('body', @defaultNav)
> > +
> > +        # add the new navModel to our opf and the allcontent container
> > +        @_addItem(@navModel, {properties: 'nav'})
> > +        allContent.add(@navModel)
> > +
> > +        #create empty module for the book
>
> Why does an empty book have a single module in it?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/oerpub/github-bookeditor/pull/70/files#r6900178>
> .
>



-- 
Katherine Fletcher, kathi.fletcher@gmail.com
<kathi.fletcher@gmail.com>
Twitter: kefletcher <http://www.twitter.com/kefletcher> Blog:
kefletcher.blogspot.com
<kathi.fletcher@gmail.com>