Thanks Jose,
If I'm understanding this correctly the simple way to do this is to
put the logic for each page in its own file. so instead of (de report
..) I would have a report.l file that just contains the guts of what
I'm coding.
Reloading model.l is not really an issue for me. Besides at the m
Hi Konrad,
On Tue, 6 Mar 2012 12:46:44 +1100
Konrad Zielinski wrote:
> Hi,
>
> At the moment I have my project in two files
>
> model.l which contains my domain classes, database init code and other
> related functions.
> server.l which contains my URL handling functions.
>
> I find that I'm
On March 5, 2012 at 8:49 AM Alexander Burger wrote:
> This sounds useful. I don't know about the types of restrictions which
> might be imposed by such servers.
It is often that you may run only a PHP script or a CGI. And the CGI
can be either compiled static binary or Perl or Bash.
best re
Hi Jakob,
> This. And the web framework could even have a "repl" or edit function
> where you could edit a running site live. It could have "Commit" and
In fact, the standard PicoLisp framework already comes with two such
features:
- you can can connect to a running PicoLisp server using "bin/p
