Re: [Nolug] PHP help

I got lost with this statement.

"why bother to learn the arcanities of a templating language like
smarty, when you already are using one with php?"

How is PHP itself as template engine? Would it be easy enough for a
non-coding web designer to use?

I've just recently got into using Smarty, and it would take lots of
effort to do same tasks in PHP only. Or perhaps I just don't know how.
I'm not an expert with Smarty, then on the other hand, I'm not
"programming" with it. Only displaying the HTML code and some data which
PHP collected for it. Web designers learn the simple tags easily so I
don't have to bother them with PHP side and they can use their own tools
for the web design.

Petri

Christopher M. Jones wrote:
> Why don't you have a look at one of the frameworks out there? I've been
> looking at Zend, lately. Seems to have some nice features. Also, for
> something more fully featured and packaged, you could look at Prado.
>
> Zend, for example, has a set of classes to handle ACLs. I'm pretty sure
> that Prado supports LDAP authentication (I know Horde does).
>
> As for a template engine, why not just use php? That's what php was
> designed for, after all. I mean, respectfully, why bother to learn the
> arcanities of a templating language like smarty, when you already are
> using one with php?
>
>
> On Thu, 2008-04-17 at 19:24 -0500, Dustin Puryear wrote:
>
>> Sguil is cool, but it's not really.. audit logging for an application.
>> My thoughts at this point are to just keep with log4php and setup an
>> audit definition. You can then point log4php at a file, syslog, RDBMS,
>> whatever. THEN you can use Sguil if it catches you fancy. :)
>>
>> Yes, as mentioned before we know and use php-ldap. I was just hoping
>> someone had already built an authn/authz framework that used LDAP and
>> possibly other configuration types. Something similar to the way you
>> build access control around enterprise apps using a generic framework. I
>> have yet to find anything in PHP for that. Oh well.
>>
>> --
>> Dustin Puryear
>> President and Sr. Consultant
>> Puryear Information Technology, LLC
>> 225-706-8414 x112
>> http://www.puryear-it.com
>>
>> Author, "Best Practices for Managing Linux and UNIX Servers"
>> http://www.puryear-it.com/pubs/linux-unix-best-practices/
>>
>>
>> Charles Paul wrote:
>>
>>>> > Audit Logging. We COULD use log4php I suppose. Other ideas?
>>>>
>>> Have you seen Sguil yet? http://sguil.sourceforge.net/
>>>
>>> The cleartext of your audit logs should be stored offsite, regardless
>>> of your log viewer.
>>>
>>>
>>>
>>>> Access Rights. We need to manage access to a given page and elements within
>>>> that page. We'll be doing this using LDAP groups. Best method?
>>>>
>>> The ldap functions, and maybe the PAM package (depending on where you
>>> want the auth done).
>>> ___________________
>>> Nolug mailing list
>>> nolug@nolug.org
>>>
>> ___________________
>> Nolug mailing list
>> nolug@nolug.org
>>
>
> ___________________
> Nolug mailing list
> nolug@nolug.org
>
>
___________________
Nolug mailing list
nolug@nolug.org
Received on 04/18/08