8086.js icon indicating copy to clipboard operation
8086.js copied to clipboard

Options to show registers in different number systems

Open roerohan opened this issue 5 years ago • 6 comments

Options to show registers in different number systems

The numbers on the UI are shown as hexadecimal numbers. A useful feature would be to have a dropdown somewhere on the UI to change the number system in which the registers are displayed. Possible alternatives to hexadecimal numbers would be

  • Binary numbers
  • Octal numbers
  • Decimal numbers

https://github.com/roerohan/8086.js/blob/017505bca69da4b7e803a2cd3e5353f9a14c5660/src/components/Register/index.jsx#L49

roerohan avatar Sep 24 '20 06:09 roerohan

Hey, I'm new to JS but can I work on this?

Thanks.

sathuhebbar avatar Oct 05 '23 04:10 sathuhebbar

Hey @sathuhebbar ,

Go ahead!

roerohan avatar Oct 05 '23 09:10 roerohan

Hey, just wanted to know what versions of nodejs and npm are preferred. Issues like ERR_OSSL_EVP_UNSUPPORTED seem to occur when I use nodejs20 and npm20 (on openSUSE Tumbleweed).

sathuhebbar avatar Oct 06 '23 13:10 sathuhebbar

Also, modifying the values in the registers to invalid values (like very large values) causes no errors (the invalid value seems to stay in the register as is). Is this expected behaviour? I think a few checks are required here.

sathuhebbar avatar Oct 06 '23 14:10 sathuhebbar

Also, modifying the values in the registers to invalid values (like very large values) causes no errors (the invalid value seems to stay in the register as is). Is this expected behaviour? I think a few checks are required here.

Feel free to add these checks.

roerohan avatar Oct 10 '23 13:10 roerohan

Hey, just wanted to know what versions of nodejs and npm are preferred. Issues like ERR_OSSL_EVP_UNSUPPORTED seem to occur when I use nodejs20 and npm20 (on openSUSE Tumbleweed).

For development, we had used node 14. It's a very old project and the packages aren't up to date since it's not actively maintained. However, in #65 , this is being worked on. The packages are going to be updated to support the latest node and npm versions.

For now, as you can see in deploy.yml everything seems to be hunky dory with node 12. You can try running it with node 12 or node 14.

roerohan avatar Oct 10 '23 13:10 roerohan