Split proton into smaller standalone packages

[dvcrn]

This was an idea from a discussion on discuss.atom.io.

Proton has a few things that could stand on it's own for people that don't want to use everything at the same time.

• dotfile loader: This would probably the easiest part, a package that just loads a specific file (maybe ~/.atom by default), loads it and puts it into the atom object. (edn? cson? json?)
• dotfile mode: Leverages above plugin but sets / removes config keys. The wipe and install mechanism that proton currently uses, just as a standalone thing.
• chain mode: The proton prefix tree. User can specify keybindings and summon the chain overlay (what proton does when you hit space). When hitting a leaf, execute the editor action.

Proton itself is then requiring these packages, adds its layer system on top and glues everything together.

[sglyon]

To me this seems like extra work, both to do the splitting and to maintain 3 or 4 packages in lockstep.

Do you anticipate other packages using the components? If so, it might be worthwhile. If not, I would personally keep them as they are.

[smldis]

Hi @dvcrn, 2 years later could this be reevaluated?

Or alternatively is it possible to disable proton package management?

[dvcrn]

@smldis What do you want to accomplish? Just the configuration system or the which-key overlay?

[smldis]

The which key overlay with spacemacs like keybindings is the main feature I use, but in general splitting the package management from the other functionality would be awesome.
Also installed package management and package configuration could be (in theory) be decoupled right?

The proton style of package management is affected by the ever standing problem of distributions, for reference: (https://www.bassi.io/articles/2017/08/10/dev-v-ops/)
Note tha I do not think it is bad (I really like distributions and the community around them). But I think splitting orthogonal functionality can be a big win