Re: Installer broken

On 9/04/2010 0:47, [email protected] wrote:
>...
> 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
>
If there was a "production-quality" upgrade script that could convert
1.x modules into valid 2.x code & templates, I'd be happy to see that
too. Problem is that expectations would be much higher there than in
the "let's see if this works" case where you just try an old module
as is, and then tweak it to fit.

I guess the approach you describe would appeal to a different audience
than the approach I described. I don't have a problem with modules that
"sort of" work if I know that beforehand - it's better than nothing,
and I like the fact that I can play around with it in legacy mode
before deciding to take the leap and try a full conversion. But that's
just the way I tick ;-)

Mike.