[Fwd: [Back-end-development] Integrating Phorum into Back-end]

Hello,

Thought that I'd forward this question over to the phpSlash list to see
if anyone has done anything like this and would have some suggestions. 
Tim's looking to bring this into Back-End, but hopefully we'd be able to
bring that over to PSL pretty easily to add to the new foundry.

Mike

-----Forwarded Message-----
From: Tim Verhoeven <[email protected]>
To: Back-end Development list <back-end-development-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: [Back-end-development] Integrating Phorum into Back-end
Date: Wed, 21 Jan 2004 11:45:19 +0100

Hey,

As some of you know I'm trying to integrate the Phorum messageboard 
(www.phorum.org) into Back-end. Yesterday I've made some first attempts at 
it. This using the BE_survey.php file as a example. (Uses PHP's output 
buffering and includes).

This allowed me to get started with it and get a feeling on how the Phorum 
code is build.
Basically each function is written in a seperate php file. Some basic 
functions are present in common.php. But all the rest are standalone. So 
no OO or functions calls we can use. There also is no central index file 
that controls the flow, so a typical phorum page contains links to a lot 
of different files.
Templates is very simple, they just include a header and footer into the 
output.
For DB they use a abstraction layer (nothing standard).

As I understand it Back-end needs it's content passed (using a variable, 
function, ...). So there are some strategies to make Phorum integrate into 
Backend :

1) Make a "index" file ourself that intercepts all links made on phorum 
   pages and use those to select to correct page to include.
   Problems : we need to parse the get arguments and forward those and 
              edit each file to change all <a> tags.
2) Make functions for each phorum file and have a "index" file that calls 
   the required function. So we don't need to parse the get arguments.
   Problems : a lot of rewriting, we still could use PHP output buffering 
              to reduce that workload.
3) Rewrite it into a "real" Backend module/plugin with a class file 
   containing all functions. This allows to rewrite all stuff to use 
   Back-end provided functions (DB, Session, cookies,...)
   Problems : a lot ot work, no real quick results.

So now for discussion. Did I miss another way to do this. What is the best 
option to choose. As I see it, it will be nearly impossible to make the 
ingration work without touching any of the phorum files. So for me at the 
moment I'm more going for option 3.

Any other ideas, sugggestions, ...

Regards,
Tim Verhoeven



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Back-end-development mailing list
Back-end-development-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/back-end-development
-- 
Mike Gifford, OpenConcept Consulting
Free Software for Social Change -> http://www.openconcept.ca
Stop Cdn Pension Plan War Investments -> http://coat.openconcept.ca/
Another world is not only possible, she is on her way -Arundhati Roy



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn