Recent searches
Search options
LiSA - A sign language learning app.
Releasing full version v1.0.0.
- Body model mechanics are final, using quaternions and vectors.
- Different sign languages can be selected.
- Full alphabet for #LSF is already available.
- Written in Rust with Egui.
- Lots of fixes and refactoring.
Read the changelog for more details.
Now it is time to work on adding new signs.
IMPORTANT: The signs already available are not crosschecked by someone, who is more competent than me. Do not trust the signs completely for now!
WINDOWS: When starting the Windows build in Wine under Linux, the app stalls sometimes with a lot of weird errors.
As I don't know, what is causing this, I did NOT update the Windows binary in the repository. You have to build it yourself!
Most work left will be on the signs data. A collaborative approach would be the best.
Moving the sign data to a completely separate repository would be my favorite option.
I keep working on it. But this will be slow. I usually create around 3 new signs a day. In a year, this will lead to a nice basic stock. But it could be faster with other people helping.
And I won't do any other sign languages.
Does anybody know a good method or tool for collaborative work on data?
Another important point:
I thought about applying to funding. The development of the app would have qualified for a lot of (European) funds. But I missed that.
If YOU want to help creating the sign data, you could try to get a funding for it. There is a realistic chance to get some. France is always keen on supporting their own language. Combined with accessibility, this should be worth of funding.
I would help you with that attempt.
If you think, the idea is good but the frontend is not, create your own. That is, why I want to separate the sign data.
The app is "mine", but the sign data should never be.