[geeklog-devel] Plugin layout

[Vincent Furia]

Basically I was thinking that only index.php have an "echo" statement.
 Everything else should pass around HTML strings.  That would allow us
to do cool stuff like apply post-processing filters on all pages (or
just some pages).

URL rewriting should be easy, if we just let the plugins deal with it.
 Just so long as the first parameter in a rewritten URL is a plugin
name so that index.php knows what to do.  Implementing something more
complex would (obviously) require more effort and complexity.

-Vinny


On Tue, 21 Dec 2004 22:55:26 -0600, Tony Bibbs <tony at tonybibbs.com> wrote:
> Vincent Furia wrote:
> 
> >Tony,
> >
> >The entire point of the "getPage" method in the plugin interface was
> >so that both procedural and MVCnPHP plugins could operate off the web
> >tree.  Procedural plugins could generate their web pages from that
> >function (or functions called from their) and MVCnPHP plugins could
> >instantiate their controller from that point.
> >
> >
> That's fine, the only thing I want to try and honor is URL rewriting.
> Thus a URL like:
> 
> http://www.example.com/index.php/article/PreSeasonDeer/
> 
> Should serve up fine.
> 
> The 'getPage' idea is nearly in-line with what I was expecting, I just
> didn't see how it would work for procedural plugins.
> 
> >That way everything except Geeklog-2's "index.php" will lie off the
> >web tree.  Even images and files could be fetched via plugin so that
> >access to them can be restricted without resorting to obfuscated names
> >and such (which is bad security anyway, just ask gallery).
> >
> >
> I don't argue this at all, again, it was more an issue of thinking
> through the procedural plugins.  I'm still fuzzy how this would work for
> them, though, I don't doubt it possible.  We just have to "make it so".
> 
> --Tony
> _______________________________________________
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
> http://lists.geeklog.net/listinfo/geeklog-devel
>