Comparing revisions for PluginsInDevelopment
- [13445] 2006-03-12 11:08:13 by BrianKoontz (unregistered user)
- [18809] 2008-01-28 00:12:52 by BrianKoontz (unregistered user) [Modified links pointing to docs server]
Additions:
- Rubric - With the demise of [[de.lirio.us]] imminent, I thought it might be interesting to incorporate [[http://search.cpan.org/dist/Rubric/ Rubric]] (the underlying Perl engine that de.lirio.us uses) into Wikka. Right now, I'm debating between two approaches:
- Create a PHP front-end to replace the CGI front-end currently distributed with Rubric. Rubric would be installed on the host machine as the complete package, with some functionality disabled (such as login and session management). Pros are that Rubric could be used "out of the box" with minimal modification, and Rubric could be easily updated as the complete package, right off of CPAN. Cons? Interfacing between PHP and Perl isn't trivial. PECL-Perl requires PHP 5.0. Mac OS X users (10.3.x) and others with PHP 4.x systems would have to upgrade to PHP 5.0, which isn't so trivial either.
- Re-write Rubric as a PHP application (phpRubric). Don't rewrite the functionality that isn't necessary for Wikka implementation. Convert the flat file DB structure to access MySQL through the existing Wikka DB interface. Pros are that phpRubric could be distributed as a 3rd-party plugin that could be completely installed within the Wikka framework. Cons? Updating phpRubric to reflect updates to Rubric would not be trivial.
After playing around with option #1 on my iBook without much success (upgrading from PHP 4.x to 5.0 under OS X is something of a chore), I'm leaning towards option #2. Comments would be appreciated!
- Create a PHP front-end to replace the CGI front-end currently distributed with Rubric. Rubric would be installed on the host machine as the complete package, with some functionality disabled (such as login and session management). Pros are that Rubric could be used "out of the box" with minimal modification, and Rubric could be easily updated as the complete package, right off of CPAN. Cons? Interfacing between PHP and Perl isn't trivial. PECL-Perl requires PHP 5.0. Mac OS X users (10.3.x) and others with PHP 4.x systems would have to upgrade to PHP 5.0, which isn't so trivial either.
- Re-write Rubric as a PHP application (phpRubric). Don't rewrite the functionality that isn't necessary for Wikka implementation. Convert the flat file DB structure to access MySQL through the existing Wikka DB interface. Pros are that phpRubric could be distributed as a 3rd-party plugin that could be completely installed within the Wikka framework. Cons? Updating phpRubric to reflect updates to Rubric would not be trivial.
After playing around with option #1 on my iBook without much success (upgrading from PHP 4.x to 5.0 under OS X is something of a chore), I'm leaning towards option #2. Comments would be appreciated!
