Separate ShelfView into Another Project?

[GoogleCodeExporter]

Upon a closer examination of Shelves, I realized that Shelves is kinda the
inverse of what I had in mind for a BookMooch client.

BookMooch has multiple lists of books that may be relevant for somebody:

-- the books in their wishlist, that they are hoping to be able to get from
others

-- the books in their moochable inventory, that they are offering to others

-- the books in the pending transaction roster (books sent out or en route
to the user)

While these lists could use the Shelves UI, they aren't locally-stored
lists of titles. Instead, these lists need to be pulled from the BookMooch
API and probably cached.

It could be that Shelves is extended to support both your personal library
and rosters held in third-party services. Or, it could be that Shelves is
split into two projects, one for the UI presentation (book icons on virtual
shelves, with nice scrolling/flinging) as a reusable widget and one that
merges that widget with the existing list+search code. In that case, a
BookMooch app might reuse the ShelfView but otherwise go its own way on the
back-end logic.

Thoughts?

BTW, is there a better place for these sorts of things than issues, such as
a Google Group you'd like to use?

Original issue reported on code.google.com by CommonsG...@gmail.com on 2 Mar 2009 at 9:01

[GoogleCodeExporter]

It seems to me that there are a lot of interesting ideas looking to be combined 
into
a book management app somehow - I like the idea of BookMooch, and it certainly 
makes
sense to keep the library/collection/book-list view as a separate activity 
available
for multiple apps.

Original comment by kwr.eala...@gmail.com on 11 Apr 2010 at 11:30