Ideas

[blitzmann]

Misc ideas will go here.

• GUI: Rework the Display class to utilize HyperTreeList. This will allow us to do a variety of things
  • Support for custom widgets within the list, which might be beneficial for things like gauges
  • Support for hiearchy. For most instance, this isn't needed, but might come in handy for fitting racks, or maybe selecting different booster side effects
  • Not as ugly as Grid
  • I like the idea of having column code that are imported and used as needed. Need to ensure this is still possible (most likely is)
• GUI: ship browser. The current one feels to congested, I want to migrate over to one that incorporates the market groups rather than the item groups. I also want to move away from three-stage system and use one that can work well however many levels there are. Undecided whether I want to attempt to convert this into a CustomTreeCtrl (or another HyperTreeList) (these would require custom widgets such as the ones we have now), or just simply rework the way it's made now to remove the concept of stages.

[DarkFenX]

We had an idea in the past where ship browsers would use market tree and follow 'min 4 max 10' concept (numbers can vary).

That is, if there're just 8 ships in interceptor group, do not divide it into racial subcategories, but divide for battleships.