Re: [phplib] phplib - what is the point? From: Stephan Ullmann (steve <email protected>)
Date: 07/22/01

Hi,

I am a user of phplib for over a year now and this is my first posting to
this list. I have just a small comment about breaking the API for getting
phplib-components into PEAR.

On Sun, 22 Jul 2001, nathan r. hruby wrote:

> On Sun, 22 Jul 2001, [iso-8859-1] Björn Schotte wrote:
>
> > > Please be sure to keep the API intact.
> >
> > set_var() doesn't conform to PEAR guidelines, so it
> > has to be setVar() (for example).
> >
>
> So, at that point if you have to go and change every set_var call
> (phpSLash, for example, has 200+ set_var() calls) you might as well move
> to IT[X] or Smarty or FastTemplates or soem other thing. What's the point
> in porting if you break the API and every function in it? None. Every
> user of PHPLib templates will just need to go and edit their code which
> won't happen. You are promoting a fork, please don't.

I don't see a problem with breaking the API in that case. Would it be so
hard to create a wrapper with the old API that calls the new one? I think
not. This can be done by creating two classes (template.php and
template-phplib.php). The latter would just include template.php and the
wrapper functions. The biggest change in the code would be the renaming of
the include file...

Bye,
Stephan 

-- 
Abbestellen mit Mail an:   phplib-unsubscribe <email protected>
Kommandoliste mit Mail an: phplib-help <email protected>