I did some experiments a while back but didn't get very far. My plan was to make the tool library manager into a child MDI window. (Sorry if my terminology is wrong). I mean it would be another tab like a document or spreadsheet. User could leave it open indefinitely. It would have additional tools for managing lists and groups of tools, importing and exporting individually selected tools or lists, and launching the editor to create/edit a tool.dubstar-04 wrote: ↑Fri Jan 12, 2018 8:13 amCertainly. If you can list any thoughts or ideas you have I can start thinking about it now and planning how to tackle it.
The library shouldn't store the tools in preferences as it does now. They should be written to the user's Path directory. The user should be able to have multiple tool files in that directory and the manager reads them all and shows them in context. User can move/copy tools between lists or write out to a new list.
Stretch goal: maybe a user could put a tool list under version control by linking it to a github repo.
Stetch goal #2: Maybe each list has a location (this could be stored in preferences) So a user could add a list by referencing an URL.
Those are a few thoughts I've had.