Currently, switching out CSS / JS files is just a matter of replacing the assets.ini file with one configured for a different front end framework. However, the view logic makes things a bit more complicated. Due to each front end framework using its own syntax and classes, to change a theme one would have to go through all the up until now defined elements in the twig view files and change all classes and nesting to match the new theme. This is impractical to say the least.
One way to make this simpler (and to basically allow for the existence of a "theme marketplace") is to support "theme folders" in the Twig default view folders, and then nest the individual views under those, like they're nested now. So just add another level for the theme, and then reference the theme's folder in each render call by variable.
Rauth works well for limiting access to classes and methods, but sometimes people will still want to limit access to routes directly.
Find a way to hack around the router's configuration so that route definitions can include the "groups" allowed to access them. Then, in a UI we've yet to build, make possible group-to-route matching. Coupled with Rauth, this will give the end user full and totally granular control over all areas of the app.
Due to a new directory layout for the configuration files, the glide setup results in an error because it sets the wrong folder as the source of the images by default. The fix is minor, just editing the paths to use the new ROOT constant defined in index.php rather than calculating relative paths.
Hi, I was just skimming through your project and I noticed that your database tables in nofw/data/db/cron.sql use DEFAULT CHARSET=utf8. You might want to consider using utf8mb4 instead to avoid MySQL truncating 4 byte UTF-8 characters.
Cheers for sharing your work, it's always interesting seeing how people put things together.
Due to some critical issues that render Gatekeeper completely insufficient for any kind of production use, namely this, this, this, this and more, and due to the complete unresponsiveness by project maintainer, I now consider Gatekeeper vaporware and am looking for alternatives.
Currently, the most likely course of action is grabbing what works from GK, putting it into a new package, and developing the rest of it properly around some interfaces. This breaking away from GK is planned for version 3.0.
Glide currently resizes images on-demand, when they're requested and if they're allowed. Sometimes, however, a user might want to generate these images well in advance.
Build a UI which would bypass the size restrictions of the current ImageController and allow for manual input of a file and all sizes a user wants to generate from it, then generate those images into the public folder ready for use. The uploaded image would be stored into the assets/image folder as usual.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent