Euphoria 4.2 still needs help!
- Posted by ghaberek (admin) Oct 26, 2023
- 1144 views
Forked from Re: IUP 3.31
Speaking of Euphoria 4.2. Will we see it before the end of this year or sometime early next year?
Here is where I currently stand.
I have a full-time job, a spouse, two kids, and "several" hobbies. To say my free time is limited would be an understatement, but I try to put as much of that limited free time as I can towards Euphoria. I have acquired a laptop specifically for use as a development machine. Euphoria isn't paying the bills so this laptop is cheap and slow but also light and portable. I can easily take it places, unlike my home "gaming" laptop. I have found a third place, specifically a new makerspace in my area, where I can spend some time each week sitting quietly (or at least undisturbed and without distraction) to focus specifically on Euphoria. These are very recent changes but they're a big step in the right direction. I also recently closed off the 2023 survey, as responses seemed to taper off through September. I'm about halfway done compiling the results and I will have a list of notes and comments soon, hopefully by the end of the year.
I have a lot of the build process figured out now including working build for 64-bit ARM. The build process still isn't great but it's stable enough to move forward with other tasks. My current priority is to update the GitHub actions script to publish "nightly" builds for most platforms, including Windows (X86/X86_64) and Linux (X86/X86_64/ARM/ARM64) but probably not Mac OS yet. These builds will include the bare minimum in a zip file: binaries, standard library, and HTML documentation. No demos, no source code, no Windows installer, no distro packages, etc. From there I'll blend in the new features I've been working on. One new feature will be added at a time and I'll need everyone testing these things as they come out so we can find any lingering bugs. New features so far include, in no particular order: foreign function interface (libffi), cryptographic hashes (SHA2, etc.), gzip compression, zip files, JSON parser, template parser, libCURL, SQLite3, and IUP.
I still need help with the checking/closing/updating tickets and updating/proofreading documentation. Honestly, at this point I'm less concerned about what we do and more concerned that we do something... anything. But whoever brings a solution to the table needs to own it and see it through from start to finish. My suggestion would be to move tickets and documentation to GitHub's issues and wiki respectively, and leave this website as the news and forum. I can help accommodate whatever you'd like to do. Other options for documentation might be something like Read the Docs or GitHub Pages, or just focus on updating and extending eudoc, but in the end Creole needs to go away as it clearly lost its format war with Markdown years ago.
As they say, "many hands make light work." Currently my hands are quite full, and that makes every task very heavy.
-Greg
