RE: Future Aegir Development

Hi,

> - --Marcin Sołtysiak wrote on 2005-04-26 14:04:
> > Sounds promising but how? What manner? Should Aegir become 
> a kind of MidCOM
> > component or should it just be MidCOM aware?
> 
> In an ideal world, you'd rebuild the functionality aegir has 
> within MidCOM,
> basically writing components for the various parts (though 
> most of the content
> management has been reworked with AIS). So its mainly down to 
> the administrative
> stuff like site creation and snippet/style editing and the like.
> 
> Basically some "Real MidCOM Admin UI Project", that 
> superseedes current (rather
> simple) AIS.

There's nothing wrong with a perfect world aspiration. Perhaps we are able
to make a perfect software (tm) :)

Using MidCOM UI to manage midgard database objects would give a nice chance
to create a schema based editing pages like:

"default" => array (
    "name"        => "host",
    "description" => "Default Host Object",
    "fields"      => array (

        "name" => array (
            "description" => "Host name",
            "datatype"    => "text",
            "location"    => "name",
            "required" => true,
        ),

        "port" => array (
            "description" => "Host port",
            "datatype"    => "text",
            "location"    => "port",
            "required" => true,
        ),

        "prefix" => array (
            "description" => "Host prefix",
            "datatype"    => "text",
            "location"    => "prefix",
            "required" => true,
        ),

        "parameters" => array (
            "description" => "Parameters",
            "datatype"    => "kind-of-collection",
            "location"    => "parameter",
        ),
    )
), // default

And depending on what access range you want to pass to SG admins you could
modify default schema adding or removing fileds. If I understand it right,
from 1.7 a MgdSchema would be a default here.

Solt