3 ms·
It's a mix of old and new. Mostly old though. One of the problematic pieces is the custom expression language: It's half a programming language incompatible wi
by beders 5y ago
It's a mix of old and new. Mostly old though.
One of the problematic pieces is the custom expression language: It's half a programming language incompatible with JavaScript that you will constantly battle with.
Consequently it has a fn:jseval escape hatch.
I couldn't find a way to sort data locally. Escape hatch it is.
Projects like this, when they mature, inevitably create a new programming language that might or might not be better than the host language.
Remote actions: Sounds like a good idea, but now you have the worst of worlds: Code managed separately on front-end and back-end that is tightly coupled via `"setpath" et. al.
The concerns of the back-end are now not just which data to get or check, but also how it is presented on the front-end.
One good thing though: The learning curve is tiny!
- sawka 5y agoData sorting and data paging are top of mind for me. I wanted to get the APIs / tags for that right before committing them to the core. Hope to add them soon. Without those tags, you'll need to write an escape hatch :/, or sort and page the data on the backend and just have the frontend be a viewer. Remote actions are an option -- you don't need to use them, but they provide a great escape hatch when you do want your app logic to be implemented in your backend language, not on the frontend. This is great for people who might be python experts but don't want to touch frontend.