Feature #1290: === Core: framework ===
Agree on new Core directory structure and class renaming to Rename certain classes and methods.
|Status:||Rejected||Start date:||01 Jul 2016|
Within this item we have to agree on
- new Core directory structure (how to split, new directory names)
- Joachim's suggestion on new Core structure is a good starting point
- exact list of classes which should be renamed, and their new names
- also including form factors names
When we have a settled list, someone will create an issue and make the renaming in one go.
To my opinion it is important that
- this activity should not be smeared over time
- there should be well defined moment in time, when it begins, and when it ends
- this activity should not be mixed with another refactoring (like moving class methods around, method renaming here-and-there, change of parametrisation etc).
- it should be done in dedicated branch without mixing with unrelated commits
- we should plan it so well, to not to return to the subject month later.
Another suggestion is that the actual implementation should be done only after our continuous integration procedure is fully settled, i.e.
- we have nightly builds on Windows, MacOS and Linux
- including automatic generation of windows/macos installers
- we have automatic tests of user examples too
- our project should be already migrated to github/gitlab
|FacettedSphere (diff from #1)|
./Sample ./FormFactors ./InterferenceFunctions ./Instrument ./InputOuput ./StandardSamples ./TestMachinery ./Basics ./Geometry ./Materials
#5 Updated by wuttke about 4 years ago
- Subject changed from Agree on new Core directory structure and class renaming to Rename certain classes and methods.
"directory structure" taken out of the title of this issue; if you want, reopen as a separate issue.
A good directory structure can be of some help in analyzing the code, and facilitates usage of a conventional text editor. Besides that it has no further implications (unless we talk about migrating Fit/ to a separate library); in particular, it does not affect the user API.
In contrast, changed class and method names will be visible to users, and will break the API, unless backward compatibility is ensured by extra efforts. So these changes indeed do need careful preparation.
#6 Updated by wuttke about 4 years ago
- Subject changed from Rename certain classes and methods. to Agree on new Core directory structure and class renaming to Rename certain classes and methods.
- Status changed from Sprint to Rejected
Perhaps it is cleaner to reject this issue, and to open a new issue specifically about the class&method renaming, using input from above.