Bleyddyn
commented
10 years ago Looking at it I think it would be very complicated right now because of the way the columns are generated and handled for the skill planner.
Separate the 'Overview' table from the skill plan table. Right now having them share the same view means there's two separate sets of code in PlanView2 that are not really related. This would probably mean we'd have three panes in the skill planner. One for the search view (on the far left), then a new one in the middle for the Overview, which would only list the plans, then a third one on the right for displaying skills in whichever plan is selected in the Overview.
I would like to make the Overview be a cell based table, so I could have the name of the plan in the top part of the cell, with number of skills and training time in the bottom. The drawbacks to that are that we would be eliminating support for older OSes (10.6 and older, I think) and it would be harder to provide support for sorting the overview. Possibly a popup menu. The drawback to using a regular table with three columns is that we would be adding a lot of width to an already wide UI.
Once the skill plans are in their own table I think we could eliminate the "Skill Planner" preference pane and just let the user adjust the skill plan table by dragging and dropping in the table itself, plus providing a popup menu on the table header for showing and hiding columns. There's already code in there to do that for the Market Orders and Contracts tables.
Once all of that was done we could then work on the problem of figuring out how to sort skills in a plan without violating any pre-requisites. And hopefully provide some visual feedback on pre-requisites.
This will be somewhat tricky because we still need to maintain pre-requisites in the correct places.