Posted by Roland Tanglao on January 28, 2007 at 2:57am
Welcome! Let's figure out together here on this group how to best use Lisp in Drupal. Things to talk about including testing, making the documentation better, making the dript code better, better integrating dript into Drupal, etc.. Use the dript project page for feature requests, bugs and nitty gritty code stuff. (and of course thanks to Chelah for starting dript!)
Comments
A great starting point!
A great starting point to bring Lisp into Drupal. We all know that Drupal is very much PHP. Here we will get to see Lispers and PHPers share and shred their differences. My suggestion is the distribution or works. PHP gets to harness the core while Lisp make up the skins. Working together is always better.
Go get them Roland! Thanks for the support.
Workflow
I was just searching for some scripting language with limited (controlled) power for Drupal to code rules which will affect node revisions and workflow based on predicate evaluation. And you guys seems alredy done a thing! I'm absolutely lame in Lisp right now but feels like that it is exactly what I need... Thank you Chelah and Roland for your work!
just helping chelean and learning
chelean has done most of the work! thank him! of course the best way we can help is to test and to contribute our thoughts (and code if able!).
Personalization, adaptive moderation
Smarty is a common option to separate module and theme developars work. Where Lisp can rule I think is a personalization and moderation rules which can be tuned by site administrators. Blocks visibility now can be determined by evaluating PHP script -- a possible place for Lisp. Drupal roles are not enough to express adaptive site behaviour. I imagine site admin use web interface to tune weight parameters in Lisp script which determines weither the particular node edit was a spam or vandalism. This script uses predefined functions to check for bad words, anonymous proxies, revision similarities etc.
Site-wide adaptive behavior
Apart from access control, other rules in Drupal have to be set on the individual node type, block and post. When a site grows the administrator confusion grows as well, making large Drupal site very complex to maintain. I think Drupal needs a single point of reference to configure all the rules. This is a place where Dript can play its role. I'm thinking and planning along that line for Dript. In term of visibility, I think, the best place to tweak is in the theme. Currently Drupal theming is very much PHP especially with PHPTemplate engine.
In its current state Dript is implemented as a filter. Dript works around node attributes including CCK fields. Dript needs to access other Drupal elements and settings.
sin, your points noted.