Refactoring #1549
Feature #1290: === Core: framework ===
Envelope task #1566: == API changes ==
rename class FitSuite
| Status: | Rejected | Start date: | 01 Aug 2016 | |
|---|---|---|---|---|
| Priority: | Low | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | - |
Description
»FitSuite« is one possible name for the entire fit library (#1548).
It is not so good a name for the top-level class that connects the fit library with the application, depends on the application, and therefore is defined and implemented in files that reside in the application.
Proposals:- FitOwner
- FitController
- ManageFit
- RunFit
History
#1 Updated by wuttke almost 4 years ago
- Parent task changed from #284 to #1566
#2 Updated by herck almost 4 years ago
I vote for FitController
#3 Updated by pospelov almost 4 years ago
I don't like FitController that much. It is also hard to explain users, why we have renamed FitSuite to something else.
As for the name of the general library, FitSuite is a bit pretentious (ba.FitSuite still not), and may make users expecting too much. We will be only able to deliver collection of minimisers under common interface.
Also there is FitSuite here
http://www.fs.kfki.hu/index.html
These are our Hungarian friends
Nevertheless, here are a bit more options to not to let this fruitful discussion ends too early
- FitPlan
- FitAssistant
- FitEntity
- FitSession
- FitTerminal
- FitUnit
- FitWorkstation
#4 Updated by wuttke almost 4 years ago
- Status changed from Rfc to Waiting
- Priority changed from Normal to Low
#5 Updated by wuttke over 3 years ago
- Status changed from Waiting to Rejected
will come up automatically with #1469, no need for action till then