-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Labels
code issueCode is not wrong, but something is offCode is not wrong, but something is offenhancementNew feature or requestNew feature or request
Description
Current standard use case for the library:
- The user imports pylinkage
- It defines a linkage of its liking
- Views the linkage with a function
- Defines any score function
- Somehow optimize everything?
- View the result again? What linkage?
If you change any parameter, the workflow is likely to be ran again. This is a tedious process.
What I'm thinking of:
- The user imports pylinkage in a
linkage.pyfile. - This file contains at least three functions:
define_linkage(dimensions, init_position) -> Linkageoptimize_linkage(dimensions, init_position) -> score
- With that we create the entry points "pylinkage-gui" and "pylinkage".
- To view a linkage
pylinkage-gui linkage.py - To optimize
pylinkage linkage.py.
- To view a linkage
I strongly advice again using OOP on front-end as it will be confusing for users. On the back-end side that may be a good option.
Metadata
Metadata
Assignees
Labels
code issueCode is not wrong, but something is offCode is not wrong, but something is offenhancementNew feature or requestNew feature or request