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

From FreekiWiki
Jump to navigation Jump to search
(moved to in the git repo)
(clean a bit)
 
(298 intermediate revisions by 2 users not shown)
Line 1: Line 1:
==o hai==
+
* 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
Because I don't like trac. I probably don't like any project management program for that matter. Using this because I loose TODO files on my system too easily. :p
+
** add the onsubmit thing for contact_methods as well
 
+
** add the line items edit link for payments and contact methods as well,
==todo list==
+
** check the new line item type(s) I've added since then (it was just gizmoes, payments, and contact_methods)
===working on===
+
* get tests sane again
* reports over time
+
** 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)
===things left for git===
+
* skedjulnator
* update the release scripts (IMPORTANT!!! because I'm really stupid sometimes)
+
** merging the customizations and defaults
* update the documentation (meh, not *that* important)
+
* cleanup with the prefix in the line item js
* gitweb on devo (currently have it on my vps...)
+
* fix our plugins stuff
* trac (or switch to ticgit)
+
** move them to their own git repos
* cruise control (useless since all of the tests are broken)
+
*** submodule them in
* rewrite the commit email script -- it sucks (I can live with it now)
+
** upgrade to the latest versions
* figure out somewhere for the devel data to live that is faster than the horrible freegeek dsl (maybe on my home server?) (I don't care -- sneakernet ftw!)
+
** forward patches upstream, and hope that they apply the changes
 
+
** monkey patch wherever possible
===and after that(Sat 12/27/08)===
+
* reports over time:
====needed====
+
** conditions
* disable certain gizmo_types
+
*** add OR support to conditions ... this will be invasive, probably
* deadbeat discounts weren't setting occured_at -- fixed, but need to clean up data again...
+
* make it work with rails 2.2.2
* gizmo_types changes (#581)
+
* interface for adding contracts
* covered report
+
* a way to disable contracts
====would be nice====
+
* validation is done on the submit button's onclick...why not the forms onsubmit?
* FIND A REAL PROJECT :)
+
** important if they submit with the enter button, I think
* switch to rspec
+
* covered condition (extra)
** and get tests that work
+
** so we can see either. we don't need side by side numbers at this point, but who knows???
* "power user" multiple systems per line item
+
** maybe a graphing report
 
* security fixing
 
* security fixing
** XSS (use ruby's h method from cgi.rb)
 
 
** CSRF (use rails' protect_from_forgery and verify methods)
 
** CSRF (use rails' protect_from_forgery and verify methods)
** check for SQL injection, we won't have to worry about this in most
+
*** Look at this: [http://github.com/emk/mephisto/commit/c500bf8e05c250d02672c30d079a0bdeb66f0569] looks really kewl!
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]
===should do soonish===
+
** look closer at the XSS stuff (safe erb) -- I got a lot of em
* work on library stuff
+
*** the on_display stuff for contact searches is an XSS bug, sort of. regardless, it should be cleaned up.
* settings page
+
* remove cruft from that ajax helper thing
* vhost based routes for separating fgdb and library, and having a setup page. I'm working on this at a glaciers pace, but I'm still working on it.
+
** lots of stuff in app/helpers/application.rb that's probably not used. if it is, it shouldn't be.
* make it work with rails 2.2.2
 
 
 
===for a rainy day===
 
* get rid of duplicated data in code
 
** conditions stuff is all over the place
 
** permissions for various controllers are split between the sidebar and the controller itself
 
* fgss generic regexps
 
* move the vendor/plugins to their own submodules...maybe I shoulda done this first, since it's gonna get even more messy with the git bug...anyway, too late for that, whatever. I'll work it out :)
 
* reform the "what I did today" section to be a changelog of fgdb.rb. We should keep track of when what happens. maybe I'll move it to it's own page once it has something useful in it.
 
  
==what I did today==
+
[[Category: Coders]][[Category: FGdb]]
Moved to [http://git.ryan52.info/?p=fgdb.rb;a=blob_plain;f=ChangeLog;hb=HEAD]
 

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.