Greetings and Salutations!
------------------------------------------------------------------------
Table of Contents
------------------------------------------------------------------------
- Editors Notes
- Midgard and SOAP
- Aegir CMS 1.0 beta2 released
- MidCOM 0.3.0
- Bugtracker Summary / Release Planning
- Mailinglist Summary
------------------------------------------------------------------------
Editors Notes
From: Torben Nehmer <[EMAIL PROTECTED]>
------------------------------------------------------------------------
Since I'm currently very busy I will give you only a short summary on
what happened the last two weeks. I hope that I will have more time
next week.
------------------------------------------------------------------------
Midgard and SOAP
From: Peter Suschlik <[EMAIL PROTECTED]>
Editor: Torben Nehmer <[EMAIL PROTECTED]>
------------------------------------------------------------------------
Peter wrote me a short (German) summary about what he is doing, I'm
trying to translate and summarize that here as good as I can:
The basic idea is developing a way to access Midgard using SOAP (Simple
Object Access Protocol) rather then the regular Web-Browser-Way. This
is important for creating sophisticateda applications, which can't
solely rely on HTTP to do their work.
He is cureently creating a proof-of-concept with a preliminary
implementation. Currently no specific functions are wrapped, just a
easy method in calling the Midgard functions are available.
This might look like this (PEAR/SOAP)
> // mgd_version()
>
> $soap_return = $soap->call('func', array('version'), $soap_options);
> echo $soap_return->value; // => your midgard version
>
> // mgd_get_topic(1);
> $soap_return = $soap->call('func', array('get_topic', 1),
> $soap_options);
>
> $topic = $soap_return->value;
> echo $topic->id; // => 1
> echo $topic->score; // => 0
Peter wants feedback at this point:
Should there be wrapper-classes for the specific Midgard Objects or
should this be the responsibility of the application?
You can find the current implementation in the CVS at /contrib/soap.
------------------------------------------------------------------------
Aegir CMS 1.0 beta2 released
From: Henri Bergius <[EMAIL PROTECTED]>
------------------------------------------------------------------------
POZNAN, ESPOO, Nov 5th 2002 -- The Aegir CMS development team has
released the second public beta of the Aegir CMS Open Source Content
Management System.
Aegir CMS is derived from the succesful Nadmin Studio application
built on the reliable Midgard content management framework. The
application is licensed under the Artistic License-derived Nadmin
Studio License.
Aegir CMS's key features include:
* MS Word -compatible content editor
* Staging/live setup
* Multi-company hosting (ASP) support
* Flexible templating and layout system
* Full Midgard Content Management framework
Changes from Aegir CMS 1.0 beta1 (released as beta1.0):
Installation package:
* Package fixed to work without preinstalled Nadmin Studio
* Package doesn't require sitegroups in repligard configuration
User interface:
* Icons are moved to Midgard's attachment system
* DHTML editor now utilizes standard GNOME buttons
* Minor cosmetic fixes
Core:
* Aegir CMS now resides in /aegir/
* NemeinAuthentication used for all authentication
* New Change Log system for posting system notifications
* GUIDs and paths separated from Nadmin Studio installation
* Some minor bugfixes
The Aegir CMS development project aims to further improve the Nadmin
Studio codebase to provide the most versatile and user-friendly
Content Management System built on an Open Source framework.
New volunteers are welcome to the project. The Aegir CMS codebase
provides PHP and Midgard developers a quite easy platform to develop
and improve content management functionalities.
Aegir CMS 1.0 beta2 is available for download at:
http://www.aegir-cms.org/Download/
Aegir CMS requires a working installation of Midgard 1.4.3. Midgard is
available in the following formats:
Source packages for Linux and Unix systems:
http://www.midgard-project.org/download/
Debian GNU/Linux (Woody) packages:
http://www.midgard-project.org/download/Debian%20Woody/
More information:
Aegir CMS developer team
[EMAIL PROTECTED]
http://www.aegir-cms.org/
------------------------------------------------------------------------
MidCOM 0.3.0
From: Torben Nehmer <[EMAIL PROTECTED]>
------------------------------------------------------------------------
MidCOM is going ahead, I just uploaded MidCOM 0.3.0 onto Nathan [1]. The
infrastructure is complete except for the Admin Site Builder, which
will be built on top of the current infrastructure. The preliminiary specs
for the Admin Site Builder can be found in the specifications on Nathan.
Everything you need to create components and display their
content on a website works at this point. Administration must be done
through
Asgard for now, but I'm working on that one.
Further release Plans: The Admin Site Builder should be available around
the end of November, a caching Engine and a packaging System will come
around
Mid-December.
For the brave who would look it over: Have Fun!
[1]: http://www.nathan-syntronics.de/midgard/docs/midcom.html
------------------------------------------------------------------------
Bugtracker Summary / Release Planning
Editor: Torben Nehmer <[EMAIL PROTECTED]>
------------------------------------------------------------------------
There is are some new minor bugs around Midgard, see the Bugtracker [2]
for details:
The first bug concerns Repligard's being able to replace Hostnames on
import which would be just out of convenience. Not a big deal I hope.
This one will most probably go into 1.5.0. [3]
Also, Repligard's export order is unpredictable, which makes it
difficult to make high-quality patches for CVS Development or so. [4]
On the Bug Squashing front we make good progress. There are some open
issues around Opening Attachments as Read-Only, the Object Constructors
and some minor things which are not so important. If those are resolved
either
way, I will pull out 1.4.4 and finally move on to get 1.5.0 into the
shelves.
[2]: http://bugs.midgard-project.org/
[3]: Bug #225
[4]: Bug #228
------------------------------------------------------------------------
Mailinglist Summary
Editor: Torben Nehmer <[EMAIL PROTECTED]>
------------------------------------------------------------------------
There was quite abit discussion about the SOAP API from Peter. The
overall feedback was quite good, it is a good approach to increasing
Midgard's connectivity.
The longest discussion thread was generated by my Midgard Review. Some
arguments where around Midgard's performance, especially where
improvment might come, staging-live setup strategies and some
strategies concerning the long-term roadmap of Midgard. I will put these
together in a few days for one of the next MWS' to get a concise
summary of the ideas.
According to the CVS list, Emiliano has started to move Midgard's
memory management to GLib. Most probably because there are some
critical memory leaks on some *BSD platforms.
------------------------------------------------------------------------
Want to continue reading MWS? Please help us create this newsletter.
Currently, it's mostly a one-man show, which is anticipated to fail in
the long term. We urgently need volunteer writers who prepare items.
Please see the contributing page to find out how to help. We're looking
forward to receiving your mail at [10].
Midgard is an Open Source Content Management System, visit our Homepage
[11] for further Information.
[10]: [EMAIL PROTECTED]
[11]: http://www.midgard-project.org
Live long and prosper!
Torben Nehmer
--
Torben Nehmer, Munich, Germany
http://www.nathan-syntronics.de, mailto:torben@;nehmer.net
PGP Public Key: https://www.link-m.de/pgp/t.nehmer.asc
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
