[FM Discuss] Booki's new features

John Curwood info at lovinglearning.co.nz
Fri Apr 1 16:18:22 PDT 2011


After reading through the blog on booki's new features, I just had to  
give them a go.

They are very very cool.

show/hid manual.  This works really well and can see as a great way  
to flesh out ideas for a new manual before sending "public".  I like  
the way it has been laid out in FM (in a table format) better than  
the layout in booki.cc, it's much tidier and less distracting in the  
FM version.

Importing/duplicating an existing book/manual works beautifully, I  
love the fact that the title can be change at the point of install,  
this is a great way to fork manuals (or any other book for that  
matter).  I do have a question/request: has there been any thought on  
merging two existing books or parts of existing books.  For example  
there is a "Booki User Guide" in both booki.flossmanuals and  
booki.cc. If someone were to make some really cool additions to a  
chapter in the FM Booki User Guide, it would be cool to merge these  
changes with the corresponding Booki User Guide chapter in booki.cc

cloning chapters.  once again this works very well and easily.  Being  
able to rename the chapter at the time of import is nice but the auto  
complete is the icing on the cake.  When i testing this feature I  
love the fact that the auto complete doesn't just pull the letters  
from the start of the title or the middle. for example typing  
"office" into the Book id brought up "openofficeorg" as an auto  
complete option. Then typing "w" into the chapter id brought up  
"writer" "draw" and "windows". This saves so much time compared to  
hunting down a url for a book. Once again with the importing/ 
duplicating manual feature it would be cool for the newly imported  
chapter to be able to receive updates from the original but this is  
just something that can be added to my Christmas wish list for Santa.

Anyway they are some very cool features and and a hugh thanks to  
Sourcefabric for sponsoring their development.

Cheers,

John







More information about the Discuss mailing list