[cvs] [Wiki] changed: CustomizeApis

[Chuck Hagenbuch]

chuck  Thu, 21 Feb 2008 14:11:50 -0500

Modified page: http://wiki.horde.org/CustomizeApis
New Revision:  1.3
Change log:  wording tweak

@@ -1,11 +1,11 @@
-+ Replacing APIs with own solutions
++ Replacing APIs with your own solutions

 Horde applications are loosely coupled with each other through the
application APIs. Each application provides a set of external API methods
that can be called from other Horde applications through the Horde Registry,
or even externally through the Horde RPC interfaces. See the
((Doc/Dev/Registry|Registry wiki page)) for details.

-If you want to provide some functionality through your own or some external
code, all you need to do it to register you own code in the Horde Registry
and provide the required API methods. If you have your own address book or
CRM solution, you could replace Horde address book module Turba with that
program for example.
+If you want to provide some functionality through your own or some external
code, all you need to do it to register you own code in the Horde Registry
and provide the required API methods. For example, if you have your own
address book or CRM solution, you could replace Horde's address book module
Turba with that program.

-Here is some real world example. Say we have some CRM system that is
providing contacts. First create a small application stub, a Horde
mini-application. We call it "crm" and need the following 3 files to become
a working Horde module:
+Here is a real world example. Say we have a CRM system that is providing
contacts. First create a small application stub, a Horde mini-application.
We call it "crm" and need the following 3 files to become a working Horde
module:

 <code>
 horde/config/registry.d/crm.php
 horde/crm/config/conf.php