|| ||Piotr Pokora <pp-AT-infoglob.com>|
|| ||Announcement: Midgard 1.8alpha2 "Independent" released!|
|| ||Tue, 2 May 2006 14:44:58 +0200|
Lodz, May 2nd 2006 -- The Midgard Project has released the second
alpha release version for the upcoming 1.8 stable branch of the
Midgard Open Source Content Management System.
Midgard's 1.8 branch focus on improved stability for Midgard2 technology
preview features introduced in 1.7 branch.
This release is adressed for Midgard developers and users who already
use configured Midgard development environments.
Due to the initial support for Midgard CMS PEAR packages it's not
recommended for initial setups.
New branch provides metadata for all objects registered from schemas.
Improved MgdSchema types managament includes features like automatic
guid accessibility and ISO datetimes.
Midgard-schema, new command line tool creates database's storage tables
and performs tests on registered types before implementing application
in production environment.
PHP is no more the only one scripting language supported by Midgard.
Due to MgdSchema technology Midgard provides better connectivity for
1.8 branch is the last one Midgard branch with repligard.
A new Java tool, Exorcist is available as a preview for general database
replication, including Midgard and other CMS's databases.
##Midgard 1.8 for end users
New configuration file format allows users to reuse the same midgard configuration among many
different applications and among many environments. New file format is in beta state in this
release and will be provided as the only one recommended way to configure any applications in
future Midgard releases. The main goal is to reuse configuration even with different binaries
without any need to rebuild Midgard.
* Midgard CMS - MidCOM is installable and available as PEAR packages.
* New command line tool midgard-schema allows developers to create objects' database storage
automatically. This tool is also able to perform basic object's operations ( like invoking real
create or update methods ) before classes are registered in production environment.
###New file format is currently supported by:
* midgard-php used with php-cli
* midgard-apache2 module
##Midgard 1.8 for developers
New midgard_metadata class is new Midgard's internally initialized type which is integral part of
every user defined class. midgard_metadata object is accessible as 'metadata' property for every
newly created object instance. Informations like date of object's creation or last update,
visibility or object's creator are available for all classes defined in schema files. This
functionality also supports sheduling dates for registered classes. Even for attachments or
###Midgard metadata in Query Builder
As Midgard Query Builder is the default way to query objects from database, it also supports
metadata constraints. Any object may be queried from database not only using its own properties but
also using metadata property.
Following Midgard mRFC 0020 midgard_metadata properties with MGD_TYPE_TIMESTAMP represents dates as
ISO datetimes. All dates are stored in UTC timezone in database.
###Improved support for GUIDs
All midgard_metadata properties which are links to other types use only guids instead of ids.
Additionaly every object in midgard database is represented by guid which is now stored in object's
table and doesn't have to be retrieved by particular method. Database upgrade performed by datagard
updates every record in database, so even records created or updated with old traditional Midgard
API are converted and ready for new applications.
Midgard Reflection is designed for developers who need to write "schema aware" applications without
any knowledge about schema registered for application.Property's or type's attributes defined in
schema files are easily accessible with Midgard Reflection objects.
###New datatypes for object's properties.
With Midgard's Reflection one may retrieve property's type. Types like longtext or datetime defined
in application's schema are easily accessible on any level wihout any need to redefine such data
for application which create user's GUI based on used objects.
##Changes from 1.7 branch:
* Metadata for all MgdSchema objects
* Support for ISO metadata datetimes
* New Quota for MgdSchema objects
* Rewritten database SELECTs with performance in mind
* Metadata and joined objects supported by MidgardQueryBuilder
* Guids support for objects and metadata
* New midgard-schema command line tool for testing schemas and creating database tables
* repligard as part of midgard-data package
* exorcist , a new tool for database replication
##Changes from 1.8alpha1 release:
* Improved Midgard Query Builder
* Improved metadata object properties
* ability to create metadata table columns with midgard-schema
* Midgard Reflection Property
* Improved MgdSchema objects' constructor
* Experimental core's GObjects handler
* Core's warning and error messages populated as php error messages
* Extension is not built against MySQL or Apache
* PEAR packages installation and configuration support
* New unified configuration file support
* Database UTF-8 update support
##Planned for next releases
* Next 1.8beta1 release: May/June 2006
* Automated database MgdSchema management and table initialization
* Deprecation of the classic functional Midgard API in favor of
MgdSchema and Query Builder
* Deprecation of repligard and apache1 support.
* Integrated midgard-java package
###Download page for latest release:
###Getting started with Midgard:
###User and developers support:
* Mailing list: email@example.com
* IRC: #midgard on irc.midgard-project.org
The Midgard Content Management Framework was initially released in May
1999, and has since gathered a sizable user and developer community.
Midgard powers thousands of web sites ranging from simple organizational
websites to major portals like New Zealand eGovernment site and
Midgard is being developed by an international team of professionals.
Midgard's development team includes new media designers, system
integrators and content management consultants. Midgard development is
being supported by several commercial and governmental entities
including the European Union.
Piotr Pokora, Midgard release manager
Henri Bergius, Midgard spokesman
The Midgard Project
to post comments)