Hi Randy,
from 1.6 on every class name should start with the applications name and
an (optional) name-part separated by an underscore, eg:
app/inc/class.app_name.inc.php:
class app_name
{
function __construct()
{
}
}
Then these classes can be autoloaded and simply used like this:
$myobj = new app_name();
These naming schema also solves the problem mentioned by randy: class
names have to be unique (to be loaded together). Loading together
happens in more places one might think:
home, sitemgr, api-hook-class, ...
Ralf
randy schrieb:
I thought I was smart a year ago when I named one of the classes in my app
"ui" and let all my ui classes in my app inherit it. It causes some
conflict with the class called ‘ui’ in emailadmin.
Just thought I would let others know of my mistake.
–
Ralf Becker
eGroupWare Training & Support ==> http://www.egroupware-support.de
Outdoor Unlimited Training GmbH [www.outdoor-training.de]
Handelsregister HRB Kaiserslautern 3587
Geschäftsführer Birgit und Ralf Becker
Leibnizstr. 17, 67663 Kaiserslautern, Germany
Telefon +49 (0)631 31657-0
Check out the new SourceForge.net Marketplace.
It’s the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
eGroupWare-developers mailing list
eGroupWare-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-developers