Difference between revisions of "User:Ryan52/old todo"

From FreekiWiki
Jump to navigation Jump to search
(clean a bit)
 
(17 intermediate revisions by the same user not shown)
Line 1: Line 1:
==kill this page==
+
* some changes to the gizmo_events (using a hash, edit buttons, add on submit, etc) should be ported to the contact methods (and other line item types, if not already), if they aren't already
I need to move all of this page into RT tickets. I've started cleaning it up a little bit.
 
 
 
==features wanted==
 
list of features wanted, most from a discussion with kc8pxy (some will be taken care of by him/his coders), others need my help.
 
 
 
* settings page (admin password, everything in the defaults table, metadata too..)
 
* 01:17 <kc8pxy> volunteer certification trancking
 
** 01:17 <Ryan52> aka contact_types? :)
 
** 01:18 <kc8pxy> btu i don't  want unilateral  designation.
 
** 01:18 <kc8pxy> i want to have 2 or 3 people to "vote" them competent.
 
 
 
==TODOs==
 
* some changes to the gizmo_events (using a hash, edit buttons, add on submit, etc) should be ported to the contact methods, if they aren't already
 
 
** add the onsubmit thing for contact_methods as well
 
** add the onsubmit thing for contact_methods as well
 
** add the line items edit link for payments and contact methods as well,  
 
** add the line items edit link for payments and contact methods as well,  
 +
** check the new line item type(s) I've added since then (it was just gizmoes, payments, and contact_methods)
 
* get tests sane again
 
* get tests sane again
 
** continuous integration is set up and working, but disabled until the tests work
 
** continuous integration is set up and working, but disabled until the tests work
* add onblur for the automatic line item completion thing
+
* add onblur for the automatic line item completion thing (in addition to <TAB>, but only on the last element, I think)
 
* skedjulnator
 
* skedjulnator
** make it integrate with the "normal" contacts table and merging the customizations and defaults
+
** merging the customizations and defaults
* when editing a return it should link to the sale/disbursement and show a bit of info about that transaction
 
 
* cleanup with the prefix in the line item js
 
* cleanup with the prefix in the line item js
* get ticgit ready, and start adding stuff to it
 
** port remaining 5 skedjulnator tickets to ticgit (I hope Richard won't mind..)
 
*** http://dev.freegeek.org/projects/skedjulnator/report/3
 
* finish sorting trac tickets, and move them to RT or ticgit
 
** http://dev.freegeek.org/projects/fgdb.rb/report/3
 
 
==blah==
 
 
* fix our plugins stuff
 
* fix our plugins stuff
 
** move them to their own git repos
 
** move them to their own git repos
Line 34: Line 14:
 
** upgrade to the latest versions
 
** upgrade to the latest versions
 
** forward patches upstream, and hope that they apply the changes
 
** forward patches upstream, and hope that they apply the changes
 +
** monkey patch wherever possible
 
* reports over time:
 
* reports over time:
 
** conditions
 
** conditions
 
*** add OR support to conditions ... this will be invasive, probably
 
*** add OR support to conditions ... this will be invasive, probably
* switch to rspec
 
** fix existing tests how they are
 
** learn to use rspec
 
** start writing new tests
 
 
==library==
 
===original list of things needed===
 
* Lookup books from library of congress or similar
 
* Check out books to people
 
* Track checkout history
 
* Print labels
 
* Inventory list (so we can check to see what's missing, etc.)
 
* Looking up all overdue books
 
* (this may not be a complete list)
 
 
===things left to do===
 
====before "beta" test====
 
* print labels (mostly done)
 
** needs small tweaking wrt the limits on the sides and such
 
* integrate the overdue list into a more general list...used to show what a "borrower" has checked out, lost, etc, and used in the overdue list. replace the separate checked out list from overdue list in "member" display.
 
 
====is this needed?====
 
* search by isbn? right now it's just a text search by title. having problems figuring out how to add more...
 
* how to handle what to label? currently new copies are added to a list in the session, as well as when you press the button, and removed when you print...this is wrong. we can use store in the database if they've been printed or not, and after you get the PDF you say "yes, it worked, mark them as labeled"...then search for unprinted ones to print.
 
* labels stuff supports it, just need teh interface. how to do this? we can show X number of tables (depending on how many labels to print) that looks like a label sheet, and have people uncheck the boxes that they want skipped. or just enter the number like it is with the current software.
 
* what happens after a book is lost?
 
* does there need to be a publicly accessible
 
 
====before/during release====
 
* moving from openbiblios schema (figured out)
 
** add foreign keys, and create (or redo..) the migrations
 
** need to create a temporary rails project that migrates the schema
 
 
====later====
 
* consider regenerating the xapian database on each start up. it might not be that hard on the database. I'll have to time it or something.
 
* isbn checksumming
 
 
 
 
==should do soonish==
 
 
* make it work with rails 2.2.2
 
* make it work with rails 2.2.2
 
* interface for adding contracts
 
* interface for adding contracts
 
* a way to disable contracts
 
* a way to disable contracts
 
==for a rainy day==
 
 
* validation is done on the submit button's onclick...why not the forms onsubmit?
 
* validation is done on the submit button's onclick...why not the forms onsubmit?
* coveredness without contracts is broken (in the js) -- no big deal
+
** important if they submit with the enter button, I think
** not sure where this is broken, this note was written a long time ago.
 
 
* covered condition (extra)
 
* covered condition (extra)
 
** so we can see either. we don't need side by side numbers at this point, but who knows???
 
** so we can see either. we don't need side by side numbers at this point, but who knows???
 
** maybe a graphing report
 
** maybe a graphing report
* update the documentation (meh, not *that* important)
 
** markstos's patch
 
 
* security fixing
 
* security fixing
 
** CSRF (use rails' protect_from_forgery and verify methods)
 
** CSRF (use rails' protect_from_forgery and verify methods)
Line 95: Line 31:
 
** check for SQL injection, we won't have to worry about this in most places since we use active record, but the reports where we use SQL directly should be checked.
 
** check for SQL injection, we won't have to worry about this in most places since we use active record, but the reports where we use SQL directly should be checked.
 
** [http://guides.rubyonrails.org/security.html Rails Security Guide]
 
** [http://guides.rubyonrails.org/security.html Rails Security Guide]
* look closer at the XSS stuff (safe erb) -- I got a lot of em
+
** look closer at the XSS stuff (safe erb) -- I got a lot of em
** the on_display stuff for contact searches is an XSS bug, sort of. regardless, it should be cleaned up.
+
*** the on_display stuff for contact searches is an XSS bug, sort of. regardless, it should be cleaned up.
 
* remove cruft from that ajax helper thing
 
* remove cruft from that ajax helper thing
 
** lots of stuff in app/helpers/application.rb that's probably not used. if it is, it shouldn't be.
 
** lots of stuff in app/helpers/application.rb that's probably not used. if it is, it shouldn't be.
* get rid of duplicated data in code
 
** permissions for various controllers are split between the sidebar and the controller itself
 
** a single place for this would be nice, then we could generate a page for admins that tells them what all of the roles give access to. this was requested by earthworm.
 
* fgss generic regexps
 
** 18:44 < aSmig> this should match everything but 31: ([0]{5,}|123456789|^.{1,4}$|^[^0-9]*$)
 
*** false positives still exist ... figure it out
 
  
==what I did today==
+
[[Category: Coders]][[Category: FGdb]]
Moved to [http://git.ryan52.info/?p=fgdb.rb;a=blob_plain;f=ChangeLog;hb=HEAD ChangeLog]
 

Latest revision as of 02:01, 27 March 2010

  • some changes to the gizmo_events (using a hash, edit buttons, add on submit, etc) should be ported to the contact methods (and other line item types, if not already), if they aren't already
    • add the onsubmit thing for contact_methods as well
    • add the line items edit link for payments and contact methods as well,
    • check the new line item type(s) I've added since then (it was just gizmoes, payments, and contact_methods)
  • get tests sane again
    • continuous integration is set up and working, but disabled until the tests work
  • add onblur for the automatic line item completion thing (in addition to <TAB>, but only on the last element, I think)
  • skedjulnator
    • merging the customizations and defaults
  • cleanup with the prefix in the line item js
  • fix our plugins stuff
    • move them to their own git repos
      • submodule them in
    • upgrade to the latest versions
    • forward patches upstream, and hope that they apply the changes
    • monkey patch wherever possible
  • reports over time:
    • conditions
      • add OR support to conditions ... this will be invasive, probably
  • make it work with rails 2.2.2
  • interface for adding contracts
  • a way to disable contracts
  • validation is done on the submit button's onclick...why not the forms onsubmit?
    • important if they submit with the enter button, I think
  • covered condition (extra)
    • so we can see either. we don't need side by side numbers at this point, but who knows???
    • maybe a graphing report
  • security fixing
    • CSRF (use rails' protect_from_forgery and verify methods)
      • Look at this: [1] looks really kewl!
    • check for SQL injection, we won't have to worry about this in most places since we use active record, but the reports where we use SQL directly should be checked.
    • Rails Security Guide
    • look closer at the XSS stuff (safe erb) -- I got a lot of em
      • the on_display stuff for contact searches is an XSS bug, sort of. regardless, it should be cleaned up.
  • remove cruft from that ajax helper thing
    • lots of stuff in app/helpers/application.rb that's probably not used. if it is, it shouldn't be.