search

edaa-org / pyEDAA.ToolSetup

https://edaa-org.github.io/pyEDAA.ToolSetup
Other
5 stars 0 forks source link

Name of the layer #3

Closed Paebbels closed 2 years ago

Paebbels commented 2 years ago

@umarcor how to name the "configuration" layer?

  1. pyEDAA.Configure
  2. pyEDAA.Configuration
  3. pyEDAA.CLIConfiguration
  4. pyEDAA.Setup
  5. pyEDAA.ToolSetup ✔️

Maybe the second form is the better one. I don't know why I called everything "Configure"...

Can you please:

I'll take care of renaming if name is changed for

umarcor commented 2 years ago

Should it be Configuration or Configurations?

Paebbels commented 2 years ago

I think it should be singular as we have ProjectModel or CLITool.

Paebbels commented 2 years ago

Hmmm we have pyEDAA.Reports in plural ... (we might need to think about it later)

umarcor commented 2 years ago

Add the generated logo to the edaa-org website in section "Projects and Configurations".

I think pyEDAA.Configurations belongs to Interacting with CLIs, because it is related to the configuration of the location of CLI tools. Conversely, the "Projects and Configurations" is about YAML/JSON files describing a project, such as .core (CAPI2) files.

Paebbels commented 2 years ago

Oh, you're right, it's a difference kind of configuration :).

I adjusted the issue text.

Paebbels commented 2 years ago

Or is it then a pyEDAA.CLIConfiguration to keep normal Configuration name free for later usage?

umarcor commented 2 years ago

I would actually call this Setup (or Setups), instead of Configuration. In essence, this layer describes (or finds out) which is the existing tool setup/installation on the system. That avoids misunderstandings with "other configurations".