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. |
From: Andris S. <And...@li...> - 2001-10-06 10:43:51
|
> --------------------- > -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. I'm for file name instead of location, it makes things a lot more easy for xml2php & friends... Btw, I think you forgot some more types: Something.bcp.xml (page definition) Something.cfg.xml (Config) Something.dcf.xml (for Datasources) Something.lcf.xml (for Languages) Something.ocf.xml (for Operations) Andris P.S. What's new with xml2php? I think the only thing we need to do is to get rid of (convert to xml) some plain php files and up we go... |
From: alex b. <en...@tu...> - 2001-10-06 17:26:20
|
> I'm for file name instead of location, it makes things a lot more easy for > xml2php & friends... Btw, I think you forgot some more types: > Something.bcp.xml (page definition) > Something.cfg.xml (Config) > Something.dcf.xml (for Datasources) > Something.lcf.xml (for Languages) > Something.ocf.xml (for Operations) ah: you bring up a good point, so I need to clarify: all .php.xml files in htdocs are assumed to be BCPs Each of those files in conf/ _must_ exist for the system to function correctly, so we can map their formats to the complete filename, instead of just the extension. I'd be interested in people's opinions on that: for "experienced" bc people, this way is easier to deal with, for newbies it would require a little explanation... but remember also that I do intend to have a fairly beefy manal for this thing once it's done :) _alex > > Andris > > P.S. > What's new with xml2php? I think the only thing we need to do is to get rid > of > (convert to xml) some plain php files and up we go... > > > _______________________________________________ > binarycloud-dev mailing list > bin...@li... > https://lists.sourceforge.net/lists/listinfo/binarycloud-dev > |
From: Andreas A. <a.a...@th...> - 2001-10-02 11:30:54
|
Hi Alex, looks fine to me. Andi >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. > > >_______________________________________________ >binarycloud-dev mailing list >bin...@li... >https://lists.sourceforge.net/lists/listinfo/binarycloud-dev > |