Does Elgg need a "Calypso" turn?
By kanha
"that two of the things that helped it make the strong, stable, powerful tool it is — backward compatibility and working without JavaScript — were actually holding it back" - https://ma.tt/2015/11/dance-to-calypso/
Has already Elgg 2 taken the Calyso turn or .... not yet?
Feedback and Planning
Discussions about the past, present, and future of Elgg and this community site.
- Juho Jaakkola@juho.jaakkola
Juho Jaakkola - 0 likes
- Juho Jaakkola@juho.jaakkola
Juho Jaakkola - 0 likes
- Juho Jaakkola@juho.jaakkola
Juho Jaakkola - 0 likes
- Matt Beckett@Beck24
Matt Beckett - 0 likes
You must log in to post replies.So far there isn't a decision about a JS framework: https://github.com/Elgg/Elgg/issues/5921
Instead we should first work on an API that could easily provide Elgg data to any kind of frontend. Devs could then build the UI from a scratch with any javascript library of their choosing and use Elgg just as a backend.
Most important need is more devs to develop the Elgg core.
Indeed, there currently is no proper API. That's what I meant in my first comment.
There are a number of web services plugins floating around that do various things, but for any real application APIs are going to be specific to use cases, so yeah it's mostly based around ability to quickly build out a custom API.
I know what I need to be more active is time... seems the older my kids get the less time I have. I thought them being more independent would mean less parenting effort. That's apparently not the case :)