CiviCRM Community Forums (archive)

Hello, Jaap,

That page doesn't seem to communicate some important context -- the page was discussing designs/ideas/proposals and not actual implementations. I've added a note at the top about that.

With that said, there has been some recent/bleeding-edge progress on this front, but the implementation is still incomplete & experimental. If using the latest/developmental versions of civix and CiviCRM (from git), then one can use "civix generate:entity" to create some skeletal files:

 * xml/schema/CRM/Myextension/MyEntity.xml
 * CRM/Myextension/BAO/MyEntity.php
 * api/v3/MyEntity.php

However, there are several bits that it doesn't setup automatically -- for CiviHR and CiviVolunteer, we've written these parts manually:

 * Add hook_civicrm_entityTypes (eg this code is in CiviHR: https://github.com/civicrm/civihr/blob/master/hrjob/hrjob.php#L90 )
 * Generate DAOs (eg in CiviHR, we have these files: https://github.com/civicrm/civihr/blob/master/hrjob/bin/setup.sh , https://github.com/civicrm/civihr/blob/master/hrjob/xml/schema/Schema.xml.inc , and https://github.com/civicrm/civihr/blob/master/hrjob/xml/schema/CRM/HRJob/files.xml)
 * Generate SQL (eg in CiviHR, we run setup.sh above and then manually copy/paste .sql from civicrm/sql/civicrm.mysql to https://github.com/civicrm/civihr/blob/master/hrjob/sql/auto_install.sql )

It would be great if we could update civix to handle these parts, too, but I don't think I'll have time for that in July. (Patches/collaborations would be quite welcome, though. )

Hi,

once generated, the bao/dao will work directy from the extension.
For sepa, we do create a symlink from the core civi to our xml, run GenCode.php and copy back manually the sql+DAO

Works ok and what Tim is working on seems to avoid most of the manual work, but it's still in the "you need to look at the code and know how it would be done manually" stage, I presume.

X+