Sardana Enhancement Proposals
Sardana Enhancement Proposals (SEPs) are the design documents used by the
Sardana community to propose, discuss and document major changes to
Sardana. They are historical design records, kept in Markdown format in
the doc/source/reference/sep directory of the repository, and are not
rendered as part of this documentation.
SEP |
Status |
Title |
|---|---|---|
OBSOLETE |
Introducing Sardana Enhancement Proposal |
|
OBSOLETE |
Reorganization of code repos |
|
ACCEPTED |
Improve integration of 1D and 2D experimental channels |
|
REJECTED |
Adapt to TEP3 (Tango-independent taurus.core) |
|
ACCEPTED |
HKL integration |
|
ACCEPTED |
Implementation of tests infrastructure |
|
ACCEPTED |
Continuous Scan Implementation |
|
OBSOLETE |
Code contribution workflow |
|
CANDIDATE |
Remove from Taurus objects the direct Logger dependence |
|
ACCEPTED |
Compact Read+Write widgets in Taurus |
|
OBSOLETE |
Taurus separation |
|
ACCEPTED |
Direct load of .ui files |
|
CANDIDATE |
Use python Enum instead of taurus Enumeration |
|
REJECTED |
Unified plugins support in Taurus & Sardana (moved to TEP13) |
|
DRAFT |
MSENV taurus schema |
|
ACCEPTED |
Moving Sardana to Github |
|
ACCEPTED |
Plugins (controllers, macros, etc.) catalogue |
|
DRAFT |
Ongoing acquisition formalization and implementation |
|
ACCEPTED |
Extend acquisition and synchronization concepts for SEP2 needs |
|
DRAFT |
Refactor plugin system |
|
DRAFT |
Sardana Configuration Tool |