Support arbitrary waveform viewer #1002
Conversation
oscargus
force-pushed
the
viewer
branch
5 times, most recently
from
a32cf67
to
829e97b
Compare
We cannot deprecate gtkwave arguments in the next release. We need to first release a version with the new feature, announcing that "old" aliases will be removed in a future version. Then, in a future release, we can remove the deprecated keywords/arguments. Other than that, this looks very interesting. So, if it's ready by the time we want to tag 5.0, we can sure have it merged before. |
|
The thing I am unsure how to handle are the option strings. Is there some previous example of aliasing those? But if the purpose is to deprecate in the long run, maybe they need to be handled explicitly anyway, so duplicated arguments and then check which has information. |
Closes #970
Haven't really had time to test this fully, so putting in draft. But since it seems like 5.0 is upcoming, this may be something to consider.
Basically, there is a
--viewerargument that lets you select a wave form viewer. Also, all--gtkwave-*arguments are renamed--viewer-*, but with aliases.(At least that is the idea once fully working.)
Motivated by https://surfer-project.org/ that is beginning to gain some traction. (Although possible to run in the browser there are also native versions.)