Omnibrain wrote to All <=-
Released a new version of IcyDraw:
https://github.com/mkrueger/icy_tools/releases/tag/IcyDraw0.4.0
It's a multi platform ansi editor. This one is more targeted at sysops
:). Has for example tdf font support - the new version supports figlet fonts as well.
Improved the UI a lot & fixed many issues. I use it myself a lot more.
- Many improvements to half block drawing
- Added status bar
- Files from 16colo.rs can now be opened from the file open dialog
- Added translations: br, ca, cs, es, fr, hu, it, pl, ro
- Improved plugin system & added new plugins from https://github.com/hellocodelinux/plugins_icy_draw - Improved the rendering of the text area - new style for selection/borders - Reworked
& improved mirror mode - Tag editor got improved - tags can now be optionally be generated in line or added with gotoxy after ansi is
drawn
Esp. the last one is nice for sysops - replacement tags like @username@ can be handled with the tag feature of icy draw.
The Linux version is just a .deb package. Not everyone uses .deb packages.
So I downloaded the Source archive, but there is no apparent way (instructions) to build it, so I gave up.
Packaging on linux is hard IMO. There are too many ways doing that.
Maybe I just add an .appimg - should be easy for icy* because rust links statically.
Omnibrain wrote to Gamgee <=-
The Linux version is just a .deb package. Not everyone uses .deb packages.
Packaging on linux is hard IMO. There are too many ways doing that.
Maybe I just add an .appimg - should be easy for icy* because rust
links statically.
So I downloaded the Source archive, but there is no apparent way (instructions) to build it, so I gave up.
Ah I see - I merged my repos and build instructions were birried in icy_term docs. Moved them where they belong to.
Install rust toolchain: https://www.rust-lang.org/tools/install
"cargo build"
It'll tell you what's missing.
On the build server I use
"apt-get install build-essential libgtk-3-dev libasound2-dev libxcb-shape0-dev libxcb-xfixes0-dev"
But not sure if all are still required.
Install rust toolchain: https://www.rust-lang.org/tools/install
"cargo build" It'll tell you what's
missing.
On 17 Feb 2025, Omnibrain said the following...
Packaging on linux is hard IMO. There are too many ways doing
that. Maybe I just add an .appimg - should be easy for icy* because rust links statically.
there's nothing special about 'make install' or package installation in general.. you can just dump binaries in /usr/local/bin and throw a few .desktop files in /usr/share/applications to run them. perhaps experiment with a vm fresh install of a few linux flavors to see if/where all the binaries "just work" ?
Yes, there are lots of different ways. I'd suggest only releasing the source code and let people build it themselves.
Okay, thanks for the clarification. All of that seems a little.... intrusive... and most people are not going to jump through those hoops, in my opinion. Maybe I'll give it another look sometime.
I had no issues getting it compiled here. Not knowing rust though I don't know how to make an icy_term binary. I have to run it with cargo.
perhaps just a little text mode installer would suffice. one that can
also uninstall, because that's just the right thing to do ;)
Omnibrain wrote to Gamgee <=-
Yes, there are lots of different ways. I'd suggest only releasing the source code and let people build it themselves.
Source code is always released.
Okay, thanks for the clarification. All of that seems a little.... intrusive... and most people are not going to jump through those hoops,
in my opinion. Maybe I'll give it another look sometime.
Not sure if all are still required. Haven't tried on a clean system for years. But if someone can remove some deps: I take pull requests :).
Most is because of the deps - it builds a gfx layer up from zero so the
UI libs need some low level stuff that wasn't shipped on the
distribution I had.
Getting the up2ate minimum library set isn't on top of my todo list. As long as it works on the build server I'm fine with it.
Problem is libc - so it doesn't just work everywhwere. Then there is no
Then there is no
way of deinstalling.
perhaps experi
with a vm fresh install of a few linux flavors to see if/where all th binaries "just work" ?
perhaps experi
with a vm fresh install of a few linux flavors to see if/where a binaries "just work" ?
As a developer trying to offer a product to "users", perhaps you
*should* try to build it on a clean system, because that's what nearly all users are.... using.
I appreciate that you're developing new/useful software... But as a developer wanting more people to use the software, isn't it a little narrow-focused to only worry about whether it works on your build server (only)? People can't use/recommend it if they can't run it...
glibc will net you almost every linux user.. if you want to go the extra mile and have a musl build, good on ya.. but you're worried about the 1%
its in target/debug/* or target/release/* (if you build with --release flag).
Yes it is. LOL I saw it there last night and shook my head at how
blind I can be. Works great.
So I hope that the app images solve it for most users. Compiling by
source can be hard. (ok cargo makes things a lot easier...)
Omnibrain wrote to Tiny <=-
Yes it is. LOL I saw it there last night and shook my head at how
blind I can be. Works great.
So I hope that the app images solve it for most users. Compiling by
source can be hard. (ok cargo makes things a lot easier...)
Why are you compiling from source?
definitely the user's fault git clone doesn't grab plugins_icy_draw by default (which isn't documented anywhere)
Maybe because they use Linux, but not a distro that uses .deb packages?
Why are you compiling from source?
Omnibrain wrote to Gamgee <=-
Maybe because they use Linux, but not a distro that uses .deb packages?
This is a guess - so far I know just of 1 user with that use case.
And that's why I added .AppImage.
The binary wouldn't run on this system, somethign about glibc not being the same. It compiled fine and works fine so I'm using it happily.
I know in another post you said most of your IcyTerm users were on Windows. Perhaps.... you would have more Linux users if it wasn't so difficult to get it installed on Linux...?
I would like to try it, and
don't mind at all if I have to compile something, assuming it's the "normal" way of configure/make/make install or whatever. Having to install entire toolchains (rust/cargo/whatever) to build something is not something I want to risk my system's stability over, and therefore I can't use your product. I'm willing to bet there are PLENTY of other Linux users in the exact same position. You're limiting your audience for reason(s) that I don't get. But OK. <SHRUG>
Ok maybe because I build on ubuntu latest. Are you on debian stable or something in that line?
Omnibrain wrote to Gamgee <=-
I know in another post you said most of your IcyTerm users were on Windows. Perhaps.... you would have more Linux users if it wasn't so difficult to get it installed on Linux...?
As said earlier - most linux users are using a debian based distro.
And getting all distros atm is hard. I added AppImage - do you've
issues with running AppImages?
don't mind at all if I have to compile something, assuming it's the "normal" way of configure/make/make install or whatever. Having to install entire toolchains (rust/cargo/whatever) to build something is
not something I want to risk my system's stability over, and therefore I can't use your product. I'm willing to bet there are PLENTY of other Linux users in the exact same position. You're limiting your audience
for reason(s) that I don't get. But OK. <SHRUG>
So you're saying you want to compile it but not when toolchains/debs
are needed? From my POV this is a contradiction.
So again: Does AppImage help on your system or not? And if not which package format would do? And no I can't fix that rust/cargo is needed.
That's not what I said. I already have toolchains - the standard stuff in any Linux installation - GCC, perl, python, etc. What I did say was that I don't want to install *another* toolchain in order to be able to use one application.
No, AppImage isn't something I want to use. Perhaps it's the rust/cargo thing that is the obstacle here. Look, I really am not trying to give you a hard time, and I am *VERY* appreciative of anyone developing new things in this hobby of ours. Thank you for doing it. It's just that for me, this particular one isn't a good fit. I wish you big success with it and again, thank you for your efforts.
I'm running ZorinOS which is based on ubuntu 22.04. Everything just works perfectly, I had tried a rolling distro (tumbleweed) and I am just not into playing around when an update stops the DE from launching. I can fix stuff, I just don't want to anymore. All my windows games work great without any putzing about. ;)
ZorinOS is great - I like it.
Gaming is now a thing on linux - used it for years now - not going
back.
I set up a 22.04. pipeline for future releases - at least for .deb.
ZorinOS is great - I like it.
I do too. It's the only distro I've tried that has somehow added a
delay to the sound driver so that when the HDMI monitor is changing resulation the game doesn't fall back to another sound device.
I like ZorinOS and even purchased the Pro license b/c its the Linux OS
I put on my daughters computer and wanted her to have the Pro...
That being said, a Pro license only lasted for [I think] 2 versions of ZorinOS; I bought it on 15, was able to download 16 & 17 but not 18 -
I think for $35 they should let you have all future versions... or at
LEAST 5??
| Sysop: | Angel Ripoll |
|---|---|
| Location: | Madrid, Spain |
| Users: | 14 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 113:18:49 |
| Calls: | 817 |
| Calls today: | 2 |
| Files: | 14,864 |
| D/L today: |
2 files (9K bytes) |
| Messages: | 70,545 |