Replies: 2 comments 6 replies
-
My original thought (not per se the answer) is that every new project starts with its own static-root, and that is the case with all the templates and in truth still solidly the start for any project. That is why the templates are designed that during design time, you load (ql:quicktime :myproj/tools) and during deployment (ql:quicktime :myproj) the idea being that the tools system loads builder related resources, the design time portions of plug-ins etc. So till now, I have relied on plug-ins using an internet based resource for their files or you manually copy. So the code in the plug-ins templates or look at clog-ace. The code is designed to fall over to internet if the resource not there. It is a system that works, but is does leave things up in the air a bit for a non-plugin library or code base and just in general. So a tool makes sense to solve and a standard of what is and what will be. I will work on asap. |
Beta Was this translation helpful? Give feedback.
-
Here is an idea for something that could work, but I have no idea how straightforward it would be to implement. Imagine CLOG having an asset registry for JS code (but also fonts etc.). In Lisp code, I'd write something like
and then
CLOG would set up the underlying Web server to serve a local file from |
Beta Was this translation helpful? Give feedback.
-
For loading JS code, we have
clog:load-script
. Give it a URL, and that's it. Great.But what if you want to use your CLOG app offline? You then want the script loaded from a local file. For that, I see only one possibility: define your own
:static-root
, copy over all the files from CLOG's default root directory, and add the ones you want to load.Unfortunately, that's not composable. If everyone does it, we won't be able to integrate each other's code.
So... is there another way?
Beta Was this translation helpful? Give feedback.
All reactions