-- Create database
- - quadrant: enum (tool, technique, platform, language)
- - cycle: enum (adapt, trial, assess, hold)
- - is_new: boolean
- - name: string
- - description: string
+- Bugs:
+ - Why's the trial and adopt ections so much larger than the asses and hold ?
+ - Is it a problem the index is potentially reset after adding/deleting blips ?
+ - Fix the ref table so items are printed out in order
+
+- Big Features
+ - The ability to drag and drop items within the map
+ - Would need to store the location of the items
+ - Ability to move maps into the future:
+ - Copy the radar but switch any 'is_new' items to False
+ - Any new items have 'is_new' set to true by default.
+
+- database
+ - Update README.md with steps for creating the database
+ - Surface the index number used ?
+ - Surface a 'Radar' table with name / index /
+ - Support showing different radars / multiple users / changes over time
+ - Allow saving radars under a different name.
- Include 'ecto_enum' to support enums: https://github.com/gjaldon/ecto_enum#using-postgress-enum-type
-- Get the d3.js libraries moved into the Phoenix framework
+- Move new-items and ref-table divs to a sliding panal
-- Update the tech-radar index form to generate the form based on the database contents
+- Resize the radar so its reactive (
-- Update the /radar page to include input forms for each of the cycles
- - Only show the form if a '+' button is clicked on the cycle row / 'clicking '-' hides the input row
- - clicking '-' item next to a row deletes it / removes it from the radar
+- Add an 'edit' tab along with the delete ? Probably just easier to delete and reenter.