Scroll back should work with the mouse wheel. However next version will have a scrollbar :). The UI lib I use now is more flexible in scrollbar usage.
It's a bit tricky - select text - right click is copy and middle click is paste. The UI lib I used didn't have context menus. I switched the UI lib the next one will have copy & paste in the context menu.
However paste will still work on middle click.
Rewrote the UI layer - it's way faster than before and has some features it hadn't before. Scrollbars/Context menu/Output with scanlines.
I consider that big enough for a 0.3.1 bugfix release:
https://github.com/mkrueger/icy_term/releases/tag/0.3.1
You're basically my Q&A team :).
Rewrote the UI layer - it's way faster than before and has some features it hadn't before. Scrollbars/Context menu/Output with scanlines.
At least it's not that bad as some people think. If we would be in 1992
I would vote to replace ZModem with something more efficient - as said YModem-1kG should beat ZModem. And ZModem has many flaws. Like a buggy crc16 implementation and the ability to execute arbitrary commands on
the remote computer (didn't implement that for icy_term btw.) and a too complex communication system.
That leads to:
For BBS's, sometimes it just doesn't work. IT may pause, give errors or fail completely, or not even start.
Implementing ZModem isn't easy - it's easy to break and as said it's too complex. That's why so many variants exists like 4k/8k, PDZModem, FastZModem or LeechZModem etc. a good protocol should be as simple as possible (but not simpler) IMO.
I don't think it's a suitable protocol for the 90' or now -
however it's working and it's not as bad as ppl think. However it's widespread and anyone can use that. The killer feature back in the days
- for me - was that I could continue transfer with that.
I agree that these days the best way for BBS would be to allow http(s) downloads. However a good ZModem implementation can get ok speeds.
But the benefit for the http downloads is that they're on a different channel and users can do BBSing and downloading at the same time. So it would be really nice to have that in these days.
But if there are BBSes out there that use for example the HYDRA file transfer protocol (FSC-0072) I would be tempted to implement that and
try it out. (I don't know much about that protocol - don't ask). Or
JModem or one of the bi directional ones. Probably get some real world data.
Separately, how tough would it be to have linux builds? I can probably build myself but just asking if you have any ci/cd build type thing :)
I don't use the HTTP downloads because copy and paste in syncterm isn't that great. If you are willing to get up telnet capability, you can
have a client which can download and still browse a BBS at the same time.
A good selection of transfer protocols.
Which ones do you miss?
Hey with the scroll back thing, it looks like the scroll back buffer emptied when a clear screen is sent. Any chance of changing that, or making it a configuration item?
Need to think about this how this can be done properly. It's sometimes
not easy because it can get very messy when using some ansi features
like scrolling - would potentially mess up the buffer. It's something where I need to do some experimenting. Clearing everything on clear
screen is certainly safe.
Maybe a stupid idea, but what about a feature to 'log' it to a video format ?
Linux hates me and doesn't want that I deploy software there :(. Which
is sad because it's my daily driver.
Hm, that's unfortunate. Are there simple build instructions to just make
a local binary? Maybe I can help if so.
Omnibrain wrote to boraxman <=-
I don't use the HTTP downloads because copy and paste in syncterm isn't that great. If you are willing to get up telnet capability, you can
have a client which can download and still browse a BBS at the same time.
I've no issues with copy&paste in icy_term :). I've implemented only a very, very simple telnet protocol and I don't think I'll use any telnet features. It's simply not the right layer for that. Downloads should
work with ssh/raw/telnet connections.
However at some point I'll look at protocols again. I now just want to finish what I already have. ATM that would be ANSI music where I need a good output library. The other stuff is just an extra. But I value any feedback and try to get things into it.
But I want to start an ANSI drawing tool - I made one in the 90' (MysticDraw) the last update was 2003 or so where I translated it to
SDL. Now 20 years later I'll update it to rust. Never got feedback for
the old one and don't think I get feedback for the new one but I
maintain it :).
However I may rename it to IcyDraw - didn't know about MysticBBS back then.
Separately, how tough would it be to have linux builds? I can probably build myself but just asking if you have any ci/cd build type thing :)
It's extremely complex to get things done on linux. I had deb builds
but no one could use them. I can make a flatpak which nobody can
install.
I use linux for development but how to deploy software on linux remains
a complete mystery for me. The easiest deployment is windows. There is
an exe which runs. Getting MacOS build and signed was a nightmare but
it works now.
Linux hates me and doesn't want that I deploy software there :(. Which
is sad because it's my daily driver.
maybe you need to switch the toolchain to nightly:
rustup toolchain install nightly
rustup default nightly
Is there a Linux binary? I've downloaded the source code, but not sure how to compile. There is a script to build a flatpak, but I don't have flatpak installed. ___ MultiMail/Linux v0.52
I added some build instructions here:
https://github.com/mkrueger/icy_term
On Saturday, December 10th boraxman was heard saying...
Is there a Linux binary? I've downloaded the source code, but not su how to compile. There is a script to build a flatpak, but I don't ha flatpak installed. ___ MultiMail/Linux v0.52
I added some build instructions here:
https://github.com/mkrueger/icy_term
I've published a .deb: https://github.com/mkrueger/icy_term/releases/tag/0.3.2
Some feedback if it works would be nice. One user said in an older
version that it doesn't work for some reason. I suspected a different glibc version but didn't hear back.
Hey Omni, I tried building last night and haven't done any
troubleshooting yet but figured I'd let you know how it played out on a rather bog standard Arch install (which means probably a bit bleeding edge): https://pastebin.com/1cPEbdms
I'll keep trying it out. I did get a little confused with the icons at the top when connected. There were no tooltips or text to say what they were. Personally, I prefer text menus over trying to figure out what the icon means.
Also, I'm having trouble connecting to minds eye, I'll troubleshoot further and let you know. It's not Minds Eye BBS as I can connect with Syncterm.
The choice if rust was an interesting choice. The source tree after compilation was 1.6GB!!! That is not including files in the ~/.cargo directory that were also added (its 550MB). The binary itself after stripping was 29MB, which is OK.
"git pull" should fix that issue.
I recommend doing a "cargo update" as well but that bug should be fixed
by updating the source.
| Sysop: | Chris Crash |
|---|---|
| Location: | Huntington Beach, CA. |
| Users: | 557 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 99:05:16 |
| Calls: | 10,385 |
| Files: | 5 |
| Messages: | 360,812 |