It has been updated on msx hub as well, thanks Fr3nd
P.s. I understood it Karloch , just that I couldn't avoid elaborate on the idea The screen of the Spectrum looks like 4 pixels font/64 columns
Tested and working now like a charm, you rocks ducasp!
Thanks for the kind words Karloch!
Version 1.20 is available on my github (and should be available on MSX-HUB shortly, I've sent a pull request for a new package to fr3nd):
https://github.com/ducasp/MSX-Development/tree/master/UNAPI/...
# CHANGELOG v1.20
- ANSI-DRV.BIN is no longer externally loaded. I've converted it into a SDCC library, which give us a few benefits, first, performance wise it is a little bit better as now functions are called using a fast calling convention that doesn't use stack... Second, you can place it anywhere on your path and it will not complain about not being able to load ANSI-DRV.BIN... Last but not least... Having a SDCC library available might get more developers involved in using this great screen mode for many different applications. :)
If anyone is interested on using the SDCC library:
https://msx.org/forum/msx-talk/development/sdcc-new-library-...
;)
That's neat!
Good stuff!
It'd be nice to implement it in some text editor (like msx-vi :) ) to have syntax highlighting
Syntax highlighting is not only about colors, it is also about syntax tree and parsing logic... would be complicated to have it implemented on MSX imho
For a text editor I think is way more optimal to use SCREEN 0 with the 4 colors to build a text user interface MS-DOS EDIT. CoM style. The ANSI driver or lib uses SCREEN 7 and even if it is fast for the highres screen mode, I don't think it can match SCREEN 0.
Version 1.21 is available on my github and is available on MSX-HUB as well! (I had no luck using upgrade, had to hub uninstall telnet and then hub install telnet):
https://github.com/ducasp/MSX-Development/blob/2ed33656242b9...
CHANGELOG v1.21
- Now it is possible to connect to telnet servers hosted by Linux/BSD
daemons, this issue was first reported by PiterPunk and then by Xipepe,
it was caused due to some strings used during telnet negotiations being
stored on the first page of memory that sometimes is overriden with MSX
BIOS. This could potentially solve issues where some MSX setups would
have issues loading this client.
Hey ducasp, not sure if I have mentioned this already but: in order to distribute releases for your project, instead of including a ZIP file in the repository itself you can use GitHub's built-in releases mechanism. See for example here:
https://github.com/Konamiman/Nextor/releases/tag/v2.1.0-beta2
As you can see, the release gets a nice page where you can add whatever release notes you want and include all the relevant binaries to be easily downloaded. Also there's a "releases" tab right below the repository description where anyone can easily browse the existing releases.
More information here: https://help.github.com/en/github/administering-a-repository...
Hey ducasp, not sure if I have mentioned this already but: in order to distribute releases for your project, instead of including a ZIP file in the repository itself you can use GitHub's built-in releases mechanism. See for example here:
https://github.com/Konamiman/Nextor/releases/tag/v2.1.0-beta2
As you can see, the release gets a nice page where you can add whatever release notes you want and include all the relevant binaries to be easily downloaded. Also there's a "releases" tab right below the repository description where anyone can easily browse the existing releases.
More information here: https://help.github.com/en/github/administering-a-repository/creating-releases
That is quite cool, going to read it and learn how to do releases with GitHub!
Thanks Nestor! :)