07-22-2014, 06:09 AM
narmani,
The way MobileSheets is currently designed, I really can't treat a bookmark as a song, because a bookmark doesn't tell you how many pages the song should be. I'm adding in version 5.0.0 a "snippet" feature which lets you cut out a portion of a song to create another song really quickly. So if you added a song with a 500 page pdf, you could open the song, and then use the snippet feature to just type in a name and a page range, and it would create a new song using that. You could repeat this multiple times to split up the PDF quickly. This is really just a more convenient way to use the copy/paste method that currently exists.
I have not yet added support for importing PDF bookmarks, but this begs the question - if I just import PDF bookmarks as bookmarks in MobileSheets, this may not really meet everyone's needs. If I import PDF bookmarks to try and create songs out of them, how long do I make each song? Do I just assume that the pages between each bookmark is how many pages that song should be?
There is another option that I haven't really thought too much about yet. The current model for a bookmark is just a named link to a page in a song. If I did away with this model, and instead treated a bookmark as an independent song with all the properties of its parent, but a different title, and a different page range (I would have to enforce page ranges for bookmarks), then I could support what you are describing. The only difference between a bookmark and a regular song would be that there is a flag in the database that specifies that the bookmark is a child song of another song. From a user interface perspective, there would a lot of little things I would have to add code for all over the place though... Because of this, I would prefer just finding a way to make the current architecture work by creating songs out of PDF bookmarks if that works for you. I'm definitely open to thoughts and suggestions about this issue, and how people would like things to work.
Mike
The way MobileSheets is currently designed, I really can't treat a bookmark as a song, because a bookmark doesn't tell you how many pages the song should be. I'm adding in version 5.0.0 a "snippet" feature which lets you cut out a portion of a song to create another song really quickly. So if you added a song with a 500 page pdf, you could open the song, and then use the snippet feature to just type in a name and a page range, and it would create a new song using that. You could repeat this multiple times to split up the PDF quickly. This is really just a more convenient way to use the copy/paste method that currently exists.
I have not yet added support for importing PDF bookmarks, but this begs the question - if I just import PDF bookmarks as bookmarks in MobileSheets, this may not really meet everyone's needs. If I import PDF bookmarks to try and create songs out of them, how long do I make each song? Do I just assume that the pages between each bookmark is how many pages that song should be?
There is another option that I haven't really thought too much about yet. The current model for a bookmark is just a named link to a page in a song. If I did away with this model, and instead treated a bookmark as an independent song with all the properties of its parent, but a different title, and a different page range (I would have to enforce page ranges for bookmarks), then I could support what you are describing. The only difference between a bookmark and a regular song would be that there is a flag in the database that specifies that the bookmark is a child song of another song. From a user interface perspective, there would a lot of little things I would have to add code for all over the place though... Because of this, I would prefer just finding a way to make the current architecture work by creating songs out of PDF bookmarks if that works for you. I'm definitely open to thoughts and suggestions about this issue, and how people would like things to work.
Mike