CRIMP

I've just rolled a new release based on our php engine, and uploaded to sourceforge for users to download. To differentiate from perl-bsaed crimp I've named the release crimphp and reset the version counter to 1.0. (0 comments)

I've just rolled a new release based on our php engine, and uploaded to sourceforge for users to download. To differentiate from perl-bsaed crimp I've named the release crimphp and reset the version counter to 1.0.

I've just rolled a new release based on our php engine, and uploaded to sourceforge for users to download. To differentiate from perl-bsaed crimp I've named the release crimphp and reset the version counter to 1.0. (0 comments)

I've just rolled a new release based on our php engine, and uploaded to sourceforge for users to download. To differentiate from perl-bsaed crimp I've named the release crimphp and reset the version counter to 1.0.

ok, I've taken all my development code for the unrelease v2, and ported it to php. I've also created a php-crimp to perl-crimp bridge that enables use of _some_ (most, but not all, alas) of the modules designed for object-oriented perl-based crimp ... [More] within the php environment. this works by spawning a special perl script that creates a $crimp object which outputs php code instead of printing directly (which would go to the browser if being run like fully fledged perl-crimp). this php code is taken by the 'perl' php-crimp plugin and run through like any other php code. In effect, the perl plugin is run to produce php code which then runs natively on the new crimp platform.ok, that sounded much more convoluted than it really is.. just trust me: you can run perl crimp plugins inside php-based crimp, so we don't need to convert everything in one go. eventually all plugins will be php-based for speed (running perl seperately has overhead which slows things down)I'll be hopefully rolling a new release when I've got the php kinks ironed out. this will either be a christmas or new-year release (I like big dates, so I'm likely to put off releasing till the aforementioned big dates, even if things appear to be fine, so that we have a milestone to aim for)... (0 comments) [Less]

ok, I've taken all my development code for the unrelease v2, and ported it to php. I've also created a php-crimp to perl-crimp bridge that enables use of _some_ (most, but not all, alas) of the modules designed for object-oriented perl-based crimp ... [More] within the php environment. this works by spawning a special perl script that creates a $crimp object which outputs php code instead of printing directly (which would go to the browser if being run like fully fledged perl-crimp). this php code is taken by the 'perl' php-crimp plugin and run through like any other php code. In effect, the perl plugin is run to produce php code which then runs natively on the new crimp platform. ok, that sounded much more convoluted than it really is.. just trust me: you can run perl crimp plugins inside php-based crimp, so we don't need to convert everything in one go. eventually all plugins will be php-based for speed (running perl seperately has overhead which slows things down) I'll be hopefully rolling a new release when I've got the php kinks ironed out. this will either be a christmas or new-year release (I like big dates, so I'm likely to put off releasing till the aforementioned big dates, even if things appear to be fine, so that we have a milestone to aim for)... [Less]

ok, I've taken all my development code for the unrelease v2, and ported it to php. I've also created a php-crimp to perl-crimp bridge that enables use of _some_ (most, but not all, alas) of the modules designed for object-oriented perl-based crimp ... [More] within the php environment. this works by spawning a special perl script that creates a $crimp object which outputs php code instead of printing directly (which would go to the browser if being run like fully fledged perl-crimp). this php code is taken by the 'perl' php-crimp plugin and run through like any other php code. In effect, the perl plugin is run to produce php code which then runs natively on the new crimp platform. ok, that sounded much more convoluted than it really is.. just trust me: you can run perl crimp plugins inside php-based crimp, so we don't need to convert everything in one go. eventually all plugins will be php-based for speed (running perl seperately has overhead which slows things down) I'll be hopefully rolling a new release when I've got the php kinks ironed out. this will either be a christmas or new-year release (I like big dates, so I'm likely to put off releasing till the aforementioned big dates, even if things appear to be fine, so that we have a milestone to aim for)... [Less]

ok, I've taken all my development code for the unrelease v2, and ported it to php. I've also created a php-crimp to perl-crimp bridge that enables use of _some_ (most, but not all, alas) of the modules designed for object-oriented perl-based crimp ... [More] within the php environment. this works by spawning a special perl script that creates a $crimp object which outputs php code instead of printing directly (which would go to the browser if being run like fully fledged perl-crimp). this php code is taken by the 'perl' php-crimp plugin and run through like any other php code. In effect, the perl plugin is run to produce php code which then runs natively on the new crimp platform.ok, that sounded much more convoluted than it really is.. just trust me: you can run perl crimp plugins inside php-based crimp, so we don't need to convert everything in one go. eventually all plugins will be php-based for speed (running perl seperately has overhead which slows things down)I'll be hopefully rolling a new release when I've got the php kinks ironed out. this will either be a christmas or new-year release (I like big dates, so I'm likely to put off releasing till the aforementioned big dates, even if things appear to be fine, so that we have a milestone to aim for)... (0 comments) [Less]

Things may have been rather quiet on the public front of late, but that doesn't mean we've been sitting on our laurels. No, I've been busy updating the engine to a fully object oriented design. Also, I'm making CRIMP into a state where it can run ... [More] perpetually with the webserver forwarding requests to the running instance (maybe via fastcgi or mod_perl) and having CRIMP execute the required, preloaded, plugins and sending the result back to the webserver. (I've got to add a configuration option to prevent preloading of modules if the owner so desires, so that CRIMP will perform as it does at v.1, just with the objectified interface.) [Less]

Things may have been rather quiet on the public front of late, but that doesn't mean we've been sitting on our laurels. No, I've been busy updating the engine to a fully object oriented design. Also, I'm making CRIMP into a state where it can run ... [More] perpetually with the webserver forwarding requests to the running instance (maybe via fastcgi or mod_perl) and having CRIMP execute the required, preloaded, plugins and sending the result back to the webserver. (I've got to add a configuration option to prevent preloading of modules if the owner so desires, so that CRIMP will perform as it does at v.1, just with the objectified interface.) (0 comments) [Less]