Two more user book attributes: owned and lend

[GoogleCodeExporter]

From email:

"Two more flags:
Owned: yes/no, so I can properly keep books in the database which I read and 
then sold again.
Lend: to keep track of books which I lended to someone else. Possibly with a 
name field :)"

Original issue reported on code.google.com by charlie....@gmail.com on 10 May 2010 at 1:23

[GoogleCodeExporter]

Charlie,
I 've been playing around with your app as a practice dev project and I've 
added this feature in a basic form with the "Have read?" checkbox replaced with 
3 for "Own?", "Lent?" and "Read?" I'm still tweaking it for small screens, but 
if you want I'd be happy to give you my changes. 
A word of warning, this is my 1st android project except for "hello world" and 
I haven't used java in years!

Original comment by JasonLiick@gmail.com on 27 Jun 2010 at 6:35

[GoogleCodeExporter]

Awesome Jason thanks. I'd be happy to check out your changes when I can. Just 
email me if you want (charlie dot collins at gmail). 

As for the owned and lend stuff, that should be pretty easy to add. The hard 
part will be altering existing users databases. Since those attributes will be 
new in the bookuserdata table, new versions of the app will need to 
backup/destroy/create/restore the db. As far as I know I can't use alter table 
with SQLite, so I'll have to write some sort of upgrade/update process. It's 
definitely on the radar, I've just been ultra busy as of late. 

Original comment by charlie....@gmail.com on 28 Jun 2010 at 3:34

[GoogleCodeExporter]

I haven't checked out said changes yet, but just wanted to add a comment here. 
I think the "tag" mechanism I plan to implement might handle this too. 
Attributes of a book like "lent" or "owned" or "my kids" or "lost that one in 
1982" or whatever a user wants could be handled with tags. Then if we make 
robust filter/sort/display capabilities based on tags that might address this 
too. (And while it will be some more work to code initially, we won't run into 
other attributes we haven't thought of later, tags are dynamic -- we'll ship a 
few default tags, but from there users can add what they want). 

Tags are handled in issue 22. 

Original comment by charlie....@gmail.com on 14 Jul 2010 at 3:35

[GoogleCodeExporter]

Set so can handle 2 or more "readers or want to read".  Husband & I both read 
some authors and we each read other authors/books.  Do not want two lists would 
create duplicates both in the list and possibly purchases.

Original comment by morganfa...@gmail.com on 29 Aug 2010 at 6:45

[GoogleCodeExporter]

Set so can handle 2 or more "readers or want to read".  Husband & I both read 
some authors and we each read other authors/books.  Do not want two lists would 
create duplicates both in the list and possibly purchases.

Original comment by morganfa...@gmail.com on 29 Aug 2010 at 6:46