Should clockwork have the ability to create new WFF projects?

[gondwanasoft]

Fitbit's CLI implements a command for creating new Fitbit OS projects. There doesn't seem to be any equivalent for WFF projects. Should clockwork provide this capability?

There's a tiny chance that it could be as simple as copying the files and directories from Watch Face Format Boilerplate Project into cwd. This would be equivalent to clockwork's current ability to install packages but targeting cwd instead of /packages, so could perhaps reuse some of that code.

Documentation to help the dev tailor the newly-created project would be necessary if it can't be done automatically. If Watch Face Format Boilerplate Project is somehow used, I could do this.

[Turtlepaw]

I've been planning to implement this. Although, I'm not sure how this should work with clockwork init:

1. Determine if the project already is a watch face format project, then create files as needed
2. Separate clockwork init and add clockwork create

[gondwanasoft]

I suspect that init would need to be retained in its own right so that pre-existing WFF projects could be adapted to use clockwork. However, if clockwork was creating a new project, it probably makes sense for clockwork to do init as part of the creation.

I guess it's possible that someone might want to use clockwork to create a project but then not use clockwork subsequently (eg, to build). That makes a case for not doing init automatically (or making it optional), but that should be so rare that isn't worth handling. Devs could simply delete the init-created files and folder if they don't want them.

[Turtlepaw]

I suspect that init would need to be retained in its own right so that pre-existing WFF projects could be adapted to use clockwork. However, if clockwork was creating a new project, it probably makes sense for clockwork to do init as part of the creation.

Yeah, that's what I thought.

I guess it's possible that someone might want to use clockwork to create a project but then not use clockwork subsequently (eg, to build). That makes a case for not doing init automatically (or making it optional), but that should be so rare that isn't worth handling. Devs could simply delete the init-created files and folder if they don't want them.

Clockwork doesn't create a lot of clockwork specific files so users who don't want to use clockwork to build can just delete those files as you've said.