From: Alex B. <en...@tu...> - 2001-10-01 21:31:02
|
heh, take it back, this is complete... I'll publish a spec on the Make process with these conventions.. Opinions? Naming 'special' files for processing by make: --------------------- -Something.ent.xml Entity xml definition. Target build/site_name/lang_code/user/ent/ -Something.qry.xml Query xml definition. Target build/site_name/lang_code/user/qry/ -Something.form.xml Form xml definition. Target is host module directory. -Something.list.xml List xml definition. Target is host module directory. -Something.wiz.xml Wizard xml definition. Target is host module directory. -Something.cal.xml Calendar xml definition. Target is host module directory. -Something.email.xml Email xml definition. Target is host module directory. -Something.fax.xml Fax xml definition. Target is host module directory. -Something.role.xml Role xml definition. Target build/site_name/lang_code/user/role/ Usually located in user/site_name/role/ in source tree. -Something.lang.xml XML String Repository. Target build/site_name/lang_code/user/lang/ -Something.php.xml = this file will be processed from xml to php using default xml2php rules and written out in the same location in the build tree with the extension .php. -Something.lang_code.php (i.e. Something.de.php or Something.en.php) means the file will replace Something.php in same directory when the language code is the same as lang_code. Useful for writing the same module that has different logic based on the location/language. |