Phil Wareham
Phil Wareham
In the short-term, we can slim down the jQuery UI library elements to only the bits we actually use - that will make transitioning to a new library or writing...
Shall we do a branch where we can test this and generally improve JS throughout?
I wonder if we could have some sort of cross-over/migration period where the older UI is still available - is that even possible? We could strip jQuery UI back to...
Just putting this here for future reference too: https://github.com/ElemeFE/element UI component library built on Vue.js. Also a sidenote, Vue has built-in drag/drop page reordering stuff so might be worth investigating...
On the other hand - the JS components from UIkit would probably be the path of least resistance, since it doesn't involve a complete rethink of how our admin side...
Been thinking about this more. Maybe the best route would be to use Web Components instead and forget the whole framework route. I can see a time in the future...
Just thinking how this could be done in a performant and bulletproof way. Sure, you could simply count the lines in the en.ini file (if it exists in the `lang`...
We could use the Crowdin API, but that also tracks translation completion percentage of files that we don't yet use in Textpattern (although might in future) such as the translated...
Oh, I see - yes that could work since we only officially update the languages with each release.
I could probably adjust the API stuff in https://textpattern.com/about/languages to allow that page to be used as an endpoint to check percentages. As long as we cache the API for...