Kicking the Repligard habit
Henri Bergius <henri.bergius-ZpG/[email protected]>
| Newsgroups | gmane.comp.web.midgard.devel |
|---|---|
| Message-ID | <[email protected]> |
Greetings! Here is an idea about making the Midgard setup process completely Repligard-free. That would enable us to deprecate Repligard earlier, and would also make style template creation and packaging much easier. This really calls for an mRFC, but I wanted to post the quick idea here as it came up on #midgard. [20:25] bergie: torben: I've been thinking of killing m-t in favor of some files + "compiled" configuration snippet in /sitegroup-config. That's what you wanted all along, right? [20:26] torben: yep [20:26] torben: although i'd put that compiled config directly into a generated code-global [20:26] torben: the less work you have to do, the better [20:26] bergie: true [20:26] torben: unless mgd_include_snippet is caught by mmp in the code-global element [20:26] bergie: ...and for compatibility I could make a style that would provide "m-t -like" elements [20:26] torben: the key is that mmp must catch this, [20:27] torben: true [20:27] bergie: ...and then upgrade tool that would make a site's style child style of the "m-t style" [20:28] bergie: probably the generated hosts/root pages should have some parameter noting that they're MidCOM sites generated with some version, so they could be upgraded as needed [20:34] torben: yeah [20:34] torben: that should be easy [20:34] torben: would it be an idea tying this to the midcom version? [20:38] bergie: yeah, guess so [20:38] bergie: "2.5" etc [20:39] bergie: or maybe the full version string [20:39] bergie: anyway, this way the site wizard could generate the full config, and it would be editable using normal admin UI [20:39] bergie: ...or by changing settings later in site wizard [20:40] torben: yup [20:41] bergie: mainly I guess "code-global" should be machine-generated [20:46] torben: yup, although you could "encaspultate" the auto- generated part insome ////// AUTOGENERATED START|END range, so that one can add additional stuff [20:46] torben: though i'm not sure if i like it [20:46] bergie: I'll think about it a bit [20:46] bergie: needs an mRFC anyway :-) [20:46] bergie: Basically the idea is to get rid of Repligard in Midgard install [20:47] torben: yeah, definitly [20:47] bergie: * Move style templates to "Mambo-like" packages [20:47] bergie: * There are no admin UIs that need importing any more [20:47] bergie: * We can generate the "Midgard Welcome Site" using a simple PHP script [20:47] bergie: * m-t moves to files [20:47] bergie: s/files/elements generated by site wizard [20:49] bergie: actually, now that I think of it, the style packages could be PEAR packages too, with custom role for importing the elements into DB (we could now keep images and CSS in "static" space) Henri Bergius Consultant Partner, Nemein henri.bergius-ZpG/[email protected] Midgard CMS www.midgard-project.org