Apart from these practical impediments, I also have some more fundamental doubts when it comes to storing each and every new Midgard-based framework development in the Midgard database, instead of on the file system. I think it's a pity that this way, we condemn ourselves to isolation, and with our small community, we'll never be able to follow the advances in the broader php community (I'm thinking application frameworks here, not php versions).
Yet another alternative is to use Emiliano's filetemplates. Not many peoplehave been using it, but I have the feeling that it could be a suitable alternative for development.
I tried it once, but I was too new to Midgard to make it work -- or to make any sense of it. But as of late, I have been exploring the nice perl script that generates the files out of the DB and thinking about it... Emiliano was onto something there.
I think it boils down to one simple thing: Midgard manages 'pages' and 'snippets' (that is, code) in the same way that it manages 'articles', 'topics' and 'attachments' (that is, content). This makes for a more consistent and robust framework, and for ackward development.
We definitely need a clear option to open Midgard to the wealth of IDEs and good text, html and image editors without having to explicitly code an integration layer (as with PHPMole). And that usually boils down to having stuff as... files. Plain old files.
And yet, this need not affect the way we distribute apps or the way we run production servers. Maybe it still makes sense to use large XML files to distribute apps, and to store all the code in mysql. Let production servers be production servers.
And let developers live and user their tools ;)
cheers,
martin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
