Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use entry points #15

Open
HugoFara opened this issue Jun 28, 2023 · 0 comments
Open

Use entry points #15

HugoFara opened this issue Jun 28, 2023 · 0 comments
Labels
code issue Code is not wrong, but something is off enhancement New feature or request

Comments

@HugoFara
Copy link
Owner

HugoFara commented Jun 28, 2023

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.py file.
  • This file contains at least three functions:
    • define_linkage(dimensions, init_position) -> Linkage
    • optimize_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.

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.

@HugoFara HugoFara added enhancement New feature or request code issue Code is not wrong, but something is off labels Jun 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code issue Code is not wrong, but something is off enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant