yeah this one is all in lua. I’m ok in js. And also just very ok in lua, and barely passable in python and a few other niche scripts. Started in ti-basic in algebra two 🤓
Thanks! And yeah, totally fixable. It's just a default behavior of love2d. by default love is 60 fps in a tight loop--- redrawing everything 60 timers per second! there's a love function called love.event.wait() that Ive been using in the update. the cursor blink will be the only thing that needs to fire on a timer, and when I move down to 10fps, it's still just fine. And then I boost to 60fps during active typing, and drop back down after a super short idle, about half a second. So while typing everything is "game speed" and then it slows and becomes 10fps and CPU is mostly asleep. There's a few other draw functions too in a couple menes I'm cleaning up that we're adding to the load. In essence, I used love2d because I wanted a word processor that moved at game speed, made a word processor that moves at game speed, but it's resource hungry like a game, so then I had to learn how *actual* word processors and text editors handle this. Next time I'll read up first!
yup!!!! This is something I just realized last week with the help of another user. Basically it’s a first person shooter powering a text editor. A love2d quirk baked in. So I’ve reduced the frame rate and changed it to a dirty flag system for the update. This is brings down the usage considerably on my system, and to almost nothing in idle, with no performance issues. Basically, the blinking cursor is the culprit! This is an interesting thing I learned. In older systems, the blinking cursor was an actual physical oscillation that came from the hardware, not something that was programmed. Dont worry, the cursor will still blink in 2.0. And it should be super low power, and work on all sorts of older machines. That's the hope and goal.
Thanks for the other compliments! Bear with me while I reinvent the wheel from scratch. (In this project, I started with literal ASCII and one byte per character.) First project I’ve ever released, and so it’s been a learning experience turning it from something like an art project into a polished app that works like a finely tuned machine.
What do you want them to do? I made them do something at one point, but don’t remember what because they’re not on my keyboard so I stopped developing them.
So I don’t have any strong opinions. I can make them do almost whatever you want. Use that power responsibly :)
coding (at my level) is just problem solving and play-testing. it's really not that hard, and it's quite fun. What's challenging is boxing it up and putting it out into the world
Thank you! Honestly, if I didn't have to do all the packaging and cross-platform testing, I could drop it tomorrow. Or in a couple days. A week. O: I'm just giving myself time for all the annoying last minute technical things, which I am dreading. The coding and designing part, I love
🫡 love it, thank you. A big 2.0 update is in the works (no feature creep, just better) so let me know any essentials you need. I’ll be dropping a devlog in a day or two with my plans.
this is weird, sorry that this is happening. Control m should get you a file menu where you can see all your documents, not a dialog for a new document. You’re in windows? What keyboard layout are you in? I’ll try to recreate this when I get home later today because this is very odd behavior. If you want to send a video, send one to Theo.is.baker@gmail.com.
thanks for your patience. I used vintage terminal fonts from the 70s and 80:, and I didn’t realize at the time how Anglo-centric and almost imperial they were. I’ve become really fascinated with this intersection of history, font design, technology over the past couple days, and have come out of it inspired to make SpacePad truly international in both function and feel by emulating and recreating the actual terminal fonts from different countries and language groups, many of which are poorly documented. A mistake i made led to me discovering how to make this app a lot better, so thanks again for the ❤️🙌🙌🙌
alright, I’ve got a patch with about 90% support of French in AZERTY, using the fonts in program right now. Missing the Ÿ and a couple diacritics but most other things are there. Will post tonight or tomorrow. And then 100% support in version 1.2, June 1st. Ÿves isn’t that common of a name, is it?
this is an incredible resource; thank you. Check back in a couple of days for a temporary patch that stops the crashing, or about ten days for the international edition. Many thanks for the compliments and the download. Happy writing!
thanks for you comment. Yes I am planning full international Latin support for an update coming in about ten days with a range of intl terminal fonts.
I thought I had sanitized for exactly this case, but I’ve heard there’s also issues with Romanian keyboard layouts. I might actually just do a patch for this scenario crash in the next couple days before I do the update, Sorry to be so American! Full international support in the works!
in the meantime you can use a English keyboard layout which I have tested throughly and which will block any characters the program can’t handle.
OK, this was a doozy. I uploaded a new a super solid appimage that works in mint 21.3, full instructions in the readme. If you're using a high density retina display, the window might be significantly smaller than designed. Spent all day trouble shooting it. But a full fix for window scaling will have to wait till v1.2. If you're using a 1920x1080, display, should be perfectly fine!
thanks for trying. Yeah there’s something I’m not seeing. I’m gonna make a usb mint 21.3 set up tomorrow morning and figure it out. you could always just download love and run the spacepad.love file that’s in the zip for the rpi If you’re eager to take a look at the app. Until then!
ok, also poking around I think you may need to install Fuse. Because that's needed for AppImages to run. And I think that was removed from ubuntu 22.04. Yeah, I think that might be it. try "sudo apt install libfuse2" and try to run it again. Ahhhhh, Linux! Sorry about this.
I've taken it down for now. No idea why that happened right now. But I'll get this fixed first thing tomorrow. In the meantime, you could try just running this command: ./SpacePad_v1.AppImage --appimage-extract-and-run.... it's possible there's a mint compatibility thing I need to look into, and if there is, this should let you use the app in the meantime.
woah this is a bad build. It ain’t supposed to look like that!!!! I’ll update this first thing tomorrow morning. Thanks for posting this. Yikes!!!! This is just the framework screen. I think its possible I might have just posted the wrong file.
