project
project summary freshmeat entry development infos mailing list WebInstaller database tools ChangeLog
page plugins
ProtectedEmail PowerSearch README README.config README.plugins README.fragments ProtectedMode INTERNALS WordIndex AboutPlugins PhpInfo OrphanedPages ListOfPluginHooks RSS RecentChanges PageIndex NewestPages SearchPages MostVisitedPages MostOftenChangedPages UpdatedPages
usage hint
9OTUNE YOGURT SÜREER AYRAN OLANA KADAR SİKERİMxD
The project moved to http://phpjs.berlios.de/ and http://developer.berlios.de/projects/phpjs, but any discussions should still go onto this page.
- won't ever be 100% *EcmaScript compliant, this is not a goal currently
- will certainly remain a mix of JavaScript and PHP, but also incorporate a few Perl and Pascal language constructs
- it will probably take a few more months before it gets feature complete
announcement
milky: I'm currently working on a JavaScriptInterpreter, which would allow users to embed (server-side) executable code into pages (yes, really freely editable!), because it would not be run by PHP itself but instead operate in a SandBox. Safe interfaces into the hosting interpreter (PHP) can of course be implemented (limited non-sql database queries and such things).
It's eventually too early to announce it, as it is only half finished, but I thought it would be interesting to tell it here. In the end it will only be an EcmaScript-lookalike interpreter, and have rather limited capabilities (not everything can be implemented, it will initially miss arrays, not to speak of objects). But then it is a rather fast interpreter, once the source code was compiled into its internal pre-bytecode formate. And it will also support a few PHP-lookalike features and language-constructs (which is not too difficult, since PHP also looks a bit like EcmaScript).
goal
The reason for making this, is to allow for Wiki plugins, that can be interchanged between different WikiWares, regardless if they are written in PHP, Perl or Python. With an unified Wiki-API builtin this became possible.
The currently developed interpreter (but eventually only the interpreter part), should at least be easy to port to Perl, once it is working.
related discussions