Hi All,
It seems to me that midgard's chief failing is that it is still very
poorly documented. I do realise that the development team is busy doing
developement (and yay! good on them :-)) and as such, documentation
isn't the first thing on their mind. A couple of things could be done to
help alleviate the problem. One thing that comes to mind is that perhaps
they could set up the current, largely incomplete manual so that midgard
developer/user types can annotate the entries - like the annotated PHP
manual. I am sure that we all come across similar problems, and either
solve them ourselves or dig info from the mailing list to solve them. If
there were a more central place for stuff like that to go, it'd make at
least my life a little easier.
The question is about the relationship between the current release
of midgard and the upcoming midgard2. I am starting to develop what will
turn out to be a fairly large site, and have chosen midgard/php as the
environment in which i am going to do the development. Will there be any
major difficulties in migrating from 1.2.4 to the new version of midgard
when the time comes? Will there be many changes in the API? will ther
ebe tools to upgrade the database?
peace
chris
-------------------------------------------------------------------------------
Chris Albone Ph: +612 9351 7774
Systems Manager, Phax:+612 9351 7778
Faculty of Medicine Email: [EMAIL PROTECTED]
University of Sydney "the only sin is shallowness"
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
