Followup from #8: align version of wavedrompy and the embedded js files about sphinx-wavedrom HOT 7 CLOSED

FYA @wallento

from sphinx-wavedrom.

I assume it makes sense to keep the version numbers in sync, too.

(Fortunately) wavedrom doesn't change this massively often. I will try to understand the differences between both this weekend and get them in-sync, so that js and wavedrompy should all be in sync with 1.6.3 soon.

from sphinx-wavedrom.

1.8.0 I mean..

from sphinx-wavedrom.

Okay, I started with a few minor patches for the actual waveform, should be done soon. There are two other json formats in wavedrom: schematics and register bitfields. Both are probably useful, but I am a bit undecided if its best to have them in the same package actually. What do you guys think?

from sphinx-wavedrom.

FYI: I implemented the missing features today and pushed them to my fork. I plan to add proper tests and documentation before the PR. I think we are nearly on the same level as the javascript code!

from sphinx-wavedrom.

Quick update: https://pypi.org/project/wavedrom/1.8.0rc3/

I think we are up-to-date with the official release now!

from sphinx-wavedrom.

Good news, thanks! I'm not sure why I said we have embedded js files in this plugin, we clearly don't (it's been a while since I've used it).

In your PR, could you add a note on where the non-js implementation comes from and what it's limitations are wrt the "official" implementation?

from sphinx-wavedrom.