Re: Installer broken
| Newsgroups | gmane.comp.cms.xaraya.devel |
|---|---|
| Organization | Xaraya |
| Message-ID | <[email protected]> |
mikespub wrote: > That's what we are trying to accomplish with this - get many of the > 1.1+ modules to "mostly" run without major rewrites for 2.x, until > such time that someone looks after it ;-) > Have to say I don't find this a good idea. 1. I would prefer this sort of thing be done with some external scripts, rather than putting things into the core. 2. Embedding transforms like this in the core encourages the perception that Xaraya will support legacy modules, something I have been at pains to discourage. 3. You haven't really gotten rid of the need for a "Xaraya expert". This just creates such an impression unfortunately. Any non-numeric entity will crash the templates again, for starters. 4. In my view half a module is worse than no module at all. Half a module is useless in a production environment, while at the same time creating pressure to "finish the job". 5.So I worry about winding up with a situation like we have now in 1x: a Xaraya with a multitude of modules that "sort of" work. Again, if there is to be such functionality I'd prefer to see it implemented via upgrade scripts. Marc