Request list - General20140404/LibrarySystem GitHub Wiki

2014-5-5

  1. Invoke RWD, apply to PC browser, tablet brower and smart mobile browser.
    Done
  2. Remove login part, as this app used for team, no need username/password. When user borrow book, need fill in both Chinese and English name for distinction, the data will be automatic generate from server.
  3. For the app need to use in smart mobile, so it's better not use dialog, so may need modify display pattern. I suggest we use single page to display detail book info, another benefit is in a single page we can show as many items as user selected. For switch interaction from summery list to detail page, we also can invoke CSS3 animation.
    Done
  4. In summery list/Home page, from my point of view, I most care is book name, publish data and image.
    Done
  5. May we can invoke some HTML5 new attributes, like web storage/App cache, of course if we have enough time and energy.
  6. No administrator, erveryone can add/remove/edit/borrow/return book
  7. For delete action, everyone every time only can delete one book, should fill in own Chinese/English name, then will do an verification, fill in book name, if equal to name in database, then can delete, like delete one repository in github
  8. Add new book: database will do validate, if exist, then notice user, user can do a simple hack then add book, like add index.
  9. Need deadline of return one book. Summery list will seperate into two category, colorful one and colorless one, colorfull means able to borrow, colorless means already borrowed out, and will list borrower name/borrowed date/return date.
  10. Add operation log, record user action and book status.
  11. Binding book contributer with book information.
  12. Add get book info from douban feature, just need fill in book name.

2014-4-29

  1. Invoke RWD, apply to PC browser, tablet brower and smart mobile browser.
  2. Remove login part, as this app used for team, no need username/password. When user borrow book, need fill in both Chinese and English name for distinction, the data will be automatic generate from server.
  3. For the app need to use in smart mobile, so it's better not use dialog, so may need modify display pattern. I suggest we use single page to display detail book info, another benefit is in a single page we can show as many items as user selected. For switch interaction from summery list to detail page, we also can invoke CSS3 animation.
  4. In summery list/Home page, from my point of view, I most care is book name, publish data and image.
  5. May we can invoke some HTML5 new attributes, like web storage/App cache, of course if we have enough time and energy.
  6. No administrator, erveryone can add/remove/edit/borrow/return book
  7. For delete action, everyone every time only can delete one book, should fill in own Chinese/English name, then will do an verification, fill in book name, if equal to name in database, then can delete, like delete one repository in github
  8. Add new book: database will do validate, if exist, then notice user, user can do a simple hack then add book, like add index.
  9. Need deadline of return one book. Summery list will seperate into two category, colorful one and colorless one, colorfull means able to borrow, colorless means already borrowed out, and will list borrower name/borrowed date/return date.
  10. Add operation log, record user action and book status.
  11. Binding book contributer with book information.
  12. Add get book info from douban feature, just need fill in book name.