richmond62 wrote: ↑Wed Dec 13, 2023 6:47 pm
Why not go off on a tangent that does not seem to interest anyone else?
After all, my Devawriter Pro for digitising ancient Indian languages is like that.
Are you being sarcastic and saying that I'm going off on a tangent with web stuff?
Or are you saying that the world wide web does not seem to interest anyone else besides me?
I don't see working with this xTalk interpreter as going off on a tangent at all, completely to the contrary, this is entirely related to Open-source and xTalk, and I'm convinced it could be made into a monster if we all pulled together as a team
Anyone with some JavaScript skills can work on the development of this xTalk 'engine'...
and I think that inherently makes it far more likely to get community contributions.
It's easy to add to its syntax and modify the existing syntax of the interpreter.
It loads much much faster than our Emscripten xTalk engine.
Its file format is 'stack as a web page', therefore you should be able to manipluate the DOM objects in ways that any web page things can. Add some SVG animation 'parts' (LC calls objects 'controls' and 'widgets') or new CSS based 'visual effects' syntax is entirely possible. I'm imagining mixing in some other xTalk-oriented JS libraries. ///_HyperScript+HTMX (
https://hyperscript.org ) could be really useful here and would keep it all in the family (the xTalk family).
With this setup, you can develop with xTalk from anywhere there's an HTML5 browser engine available.
No Xcode, Visual Studio needed and it's safe from over-zealous IT dept.
This may still be a diamond in the rough, but I thought you guys wanted less bells and whistles with your xTalk anyway?
This is absolutely PERFECT for schools and for students on low-powered Chromebooks or SoC type machines (RPi)
I runs 'Native' on a phone or iPad or Apple Silicon Macs.
It's as platform agnostic as you can get.
If you need any more 'native' access to the operating system you wrap it in a JS App engine like Electron and have all access to all of Node.js 'React-Native ecosystem from xTalk (would still need to make wrappers).
It has a working importer for HyperCard content, and some XCMDs/XFCNs can easily be reimplemented (as I did here for 'launchURL'). By piggy-backing riding on top of HTML5/jS, all the heavy lifting work of development is then being done by MEGA-Corps like Google & Apple, and we gain security and new features 'free'.
Most browsers (Chrome, FireFox, not Safari) now even have built-in support for WebMiDI so I can still easily do some live-coding music stuff while sticking to using xTalk (after writing some wrapper code, which I already added a check for if WebMIDI API is available).
... and again xTalk gains access to all of the gazillion JS libraries that exist, like Charts.js (isn't LC using that) for example.
This kinda solves our problem of lacking a real-pro-lead-software engineer now doesn't it?
and furthermore...
I'm not an lawyer but with a little work this could very probably free all our xTalk scripts from being in anyway bound to that 'LC Community license' in accordance with LC's publicly declared interpretation, because if your scripts don't need that particular xTalk Engine in order for the scripts to work, then your scripts are no longer a 'derivative work' are they? They're something separate, a work in generic 'xTalk lang'.
Mind you, I'm not saying we should abandon the LC Community Engines / IDE code-base at all. I still intend to compile new binaries from source (specially once I get a hold of an Apple Silicon Mac). I am getting more interested in compiling
on Linux, in part because that is also the recommended platform for compiling the Emscipten version of the engine.
What I am saying is that if we can re-implement most, if not all, of our syntax with another xTalk interpreter, one that was built to be far more open and web oriented from its inception, then we should. Then we'll have a second foundation, a backup plan (too bad the name 'Plan 9' was already taken by an OS). An xTalk foundation that runs on web is one that is going to be useable for a very long time, maybe as long as there are web browsers.