CSL to store code that works

Hi,
Your software is great!!!
However, I would like to use it to catalog code that actually works (i.e., the snippets could be directly included in a PHP project, instead of having to copy and paste the code). I managed change the functions:

function dec_string($string) {
return ($string);
}


function enc_string($string) {
return ($string);
}

in functions.php, to eliminate the reversing of the snippet, but I still get a problem:
when writing something like
<? echo "hello"; ?> the library app changes the code to
<? echo \"hello\"; ?>
What else should I change so the snippets are usuable as I save them?

Thanks in advance,
Bob

By using

function dec_string($string) {
return stripslashes($string);
}


function enc_string($string) {
return stripslashes($string);
}

in functions.php seems to resolve the problem.

Apache would not execute files that end with .s as PHP files; in fact, it outputs the contents of the snippet right into the browser, just as with a regular text file
(and the contents of the directory could be filtered out/hidden from direct view with .htaccess).
Is there anthing else that I should be aware of?

Another thing is that I am thinking about is integrating some of the ideas found in php.ide, so you are able to run/debug the scripts in a separate window.

It is nice that there in no security authentication scheme implemeted; it makes it easier to custom build this part (with .htaccess or MySQL for example).


Thanks.
Bob

[stuart]

I was always intending to rewrite CSL so it could work with real files (scan file or directories), add the code to MySQL and allow sub-directories. This would have been ideal for projects and could also work for version control. I never got round to it!!
I think your ideas are similar and would love to see the final version. Most of the code for CSL was writen quite a while ago and I am aware of some minor errors, most of which are php configuration issues.
I did write in in a component based method so that its easily editable, this applies to both design and development. An other thing i wanted to do was add a database abstraction layer but, still allow flat text file usage. I have many ideas to improve it (and to get it work in more configs).
At one time I started to add security but this is something I dont like out of the box. There are various methods for security and sometimes the code can be confusing to users wishing to remove it or change it, not to mention config problems. So I felt it was much better exclude it altogether.

I look forward to seing your improvements

Regards,
Stuart

Thanks.