Cooperation on the ELten Code

Hello!
Since I've addressed developers so recently, maybe it's worth writing a few words about cooperation, what is needed and so on.
It was on github that I pushed further changes towards version 2.3, namely unification, so that I could work on the new engine right after the release of 2.3.
For the reminder, the Elten repository can be found here:
https://github.com/dawidpieper/elten2

At the time of writing this post, the newest commit is
f7a9891..6a43793 master.

Let's see what we have here.
The entire server section does not interest us, there is a server code, in fact not the latest, because I have not updated it yet, I will do it after some planned modifications.
We are interested in the client folder, here we have the client code, of version newer than last stable - 2.26 presently.

The core folder contains the Ruby code of the current build.
And, for the sake of clarity, there are almost certainly fatal mistakes there.
If something is here, the only thing that is certain is that it was possible to run it. And that's it.
But for now let's give a peace to it.
Next we have a folder core+experimental. Here is an old live project, an attempt to write a speech dispatcher support (Linux), and so on. The project is no longer valid, it was replaced by Elten Engine, but the code is preserved for ilustrative purposes.
The dict folder contains German and English translations.
ext is an external Elten modules folder, and so an agent code, a launcher, and so on.
installer is the installer and updater.
lib is the elten.dll library, which will be no longer used as of Elten 3.0.

We are interested in the engine folder at the moment, which in general is a garbage.
This is an experimental version of the new engine.
In this folder you will find the src folder and api folder in it.

And here is an invitation for help to anyone willing.
I'm writing support for the engine under WinAPI, functions for creating windows, speech (library screenreaderapi) and so on.
Only Windows so far, Linux and Mac will come later.

It's all written in C.
If someone wants to help here, ye can do it in three ways:
1. sort out the code, because I write it quickly and am going to clean up it later. If you like to have fun in clearing, you can organize it, comment, standardize variable names and so on.
2. Write ports for Linux and Mac. There, in every function you have #ifdef WIN32, the code for Windows. If anyone knows how to port a function to Linux or Mac, I would be very grateful for your support.
3. Embrace the window. For now, the engine creates this window only on Windows. Well, that's all. You can start writing a procedure for a window on a Mac and Linux.

On the days when I finish the process of saying goodbye to WinAPI in the core code, you'll get launchers for the engine that do work, then you will be able to do even more.

If someone decides to help, of course, I invite you to send a pull request.

Thank you in advance.

Hello David. As i understood,it will be version for android and for ios? If it's true,can you please upload or give me privately code of android version,to i can compile it in android studio or in any other ide and test it? It seems,what you uploaded not all code,because,for example,in folder server/audioblogs/posts it's only one document licenses.txt and no any code. Also,for example,in folder server/audiomessages there is only licenses.txt and not any more,and it's .in the most subfolders of folder server. If i rong,excuse me please. Thanks.

i was asking david too

Hello,
i find the server part interesting.
Can i host my own elten?
How can do i it?
Regards
Armin Moradi

Why you want do it?

wow. of course every one can host there own elten, but i think it must be a private elten for experiments. if you will promote your own elten, than the official one will be less active. thank you for understanding

and may be pajper will close the source

that is not allowed come on man if you have your ownelten you can use it against this one think

i agree.