Well at least this remove the tests from the engine.
So egegctively engine won’t prevent you about that fact.
Then you should test everything is really working.
If you have no big problems I’ll commit this in the trunk.
I tried those changes April last year, haven’t noticed anything bad,
but I don’t know what to look for. Seems to work, but obviously you
know your code better than I.
About hook support for agents you could try it effectively.
Agents needs to be derived from the agents bases classes, in that
sense they’re already hooks of the activities.
I was thinking about changing engine/compiler/agents_pre.php and
engine/config.egw.inc.php->galaxia_get_agents_list() to also check an
egroupware hook ‘workflow_agent’, so other applications can provide
their own agents without copying in the files and editing the list in
config.egw.inc.php similar to how the link system works.
It seems that only ui_agent* is called directly from the engine in
agents_pre.php, and that bo_agent* can reside wherever.
I’m a little confused as to how the AdminActivityOptions works though,
as it references an undeclared variable $this->t.
Does that sound ok? Good idea? Any files I missed?
Nathan Gray
nathan at goarctic dot com
Extra punctuation??? Ug!!!
Just say no! Punctuation marks do not gain significance if you
increase their number, they make you look silly. One is sufficient.
Check out the new SourceForge.net Marketplace.
It’s the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
eGroupWare-developers mailing list
eGroupWare-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-developers