Make profile management contents visible in ~/.skeinforge

[clothbot]

The built-in skeinforge profile management hooks work as follows:

• File ~/.skeinforge/skeinforge_profile.csv controls whether cutting, extrusion, milling or winding profile subdirectory is picked.
  • SkeinFox default is "extrusion".
• File ~/.skeinforge/extrusion.csv controls which extrusion subdirectory (name) is used in extrusion profile mode.
  • SkeinFox default is "SkeinFox_MakerBot_ABS".

...so if you were to explicitly create ~/.skeinforge/extrusion/SkeinFox_v1.50_ABS-0.5Fill and ~/.skeinforge/extrusion/SkeinFox_v1.50_PLA-0.5Fill with their respective contents all you'd need to do is modify ~/.skeinforge/extrusion.csv to point at a different file-set.

Bonus of doing it this way is that the full set of SkeinFox-created profiles would be accessible from externally-launched skeinforge sessions, independent of what's embedded in SkeinFox at any given time.

[clothbot]

As it relates to git mechanisms, here of some ideas on how to implement:

• Initial create/copy/rename would create ~/.skeinforge/extrusion/profile_branch_name
• Select a profile would overwrite ~/.skeinforge/{skeinforge_profile,extrusion}.csv files
• Edit (currently Selected) profile would launch internal skeinforge.
• Save would commit just the selected profile changes to git.
• Save All/Exit could prompt to commit all detected changes to git, independent of selected profile. It is revision control after all; easy to revert. :-)

[jmil]

thanks for the ideas and implementation details! i'll have to think on this some more. i haven't used skeinforge profiles (and I heard there are specific naming convention requirements, so the debugging/failsafe implementation would be tricky). i agree it would be excellent though as long as we preserve absolute speed and can guarantee file writing. in SkeinFox, we let git do all this heavy lifting. i'd have to implement it directly myself if we go with this new route.