Closed ff6347 closed 8 years ago
Yepp this was also my first thought, maybe we could do it like processing, initially create a frontal-folder and if the user does not like to spam the user-directory she can choose another destination and move stuff...
For configs i though about using the standard user-app-path (library/application support/FRONTAL)... i think it depends if we want users to edit the config file by hand. so far i only have
as variables in the config, which can all three be modified through the interface...
As discussed today I'm a fan of a manged folder by frontal called
~/.frontal
It could contain themes, settings.json, other things. So a backup of .dotfiles would manage this folder as well. The application support is also a possibility but makes three paths
*nix --> home win --> Documents osx --> Library/Application Supprt
when using a
~/.frontal we can do *nix and osx the same way
Agreed.
A. As a temporary solution we keep a folder at location X (defined by user)
B. Target is a ~/.frontal folder managed through FRONTAL Which means we need:
Right. As discussed management will be a later feature.
I would suggest having a folder in the the user home directory
with
everyone could store themes there. A bit like grunt-init
This would also allow storing config files there.