Replies: 6 comments 7 replies
|
So the idea is to have a set of executable command-line interfaces/scripts that solve some tasks that are often necessary, like e.g., visualising splines, maybe converting between different formats of splines, etc...? |
|
Visualizing, yes. We can also do simple conversions, but there're different options for different IO types and it'd be unnecessarily complicated to support them. However, if you catch yourself opening python interactive mode just to do this one specific task very often and you can abstract general use-case of this situation, you should consider adding it |
|
As far as I know you can also add multiple commands like splinepy-show and splinepy-solve or something like that. It would make the interfaces easier. I will look into it when I get home. |
|
Soo I have made a spike with command stubs. These have to be correctly implemented now. It is also possible to do separate commands like 'splinepy-plot' and 'splinepy-convert'. What would you think is better? |
|
single command |
|
I might have forgotten to mention that the subcommand method is implemented as a spike in the branch splinepy:ft-cli. Feel free to check it out. If I find the time I will also work on implementing the plotting function, but I would like to quickly talk about some things before I do it. |
|
I like the subcommands, but in general I am not really in favor of these scripts. It is just one more thing to maintain, also one which is very hard to test |
|
good point. Maybe only |
|
With show what are the default options? And here we also have the problem with import options. Should it just import with default options and show it? |
|
@clemens-fricke can we have something like |
|
I am still interested in having |
Uh oh!
There was an error while loading. Please reload this page.
Let's add some cli scripts to the package. To start with, a
load-and-show. Please extend ideas here!All reactions