-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Ami.

- --On 06.03.2002 16:24:03 +0200 Ami Ganguli wrote:

>> Attached to this Mail is the first Draft over a thing we here at
>> Linksystem Muenchen call the "Midgard Components" Framework.
>> 
>> It is still incomplete, but take a look and tell me what you think!
> 
> It looks cool.  What I'd suggest though is that you (or we) try to

We sounds good *gg* The project will get big enough, especially if all
the ideas like dynamic administration sites and the advanced layout
engine will be incorporated.


> find an incremental way to doing this.  Otherwise you risk getting
> into the same mess that I did with my Midgard 2.0 work.

I know. What I have in mind is creating the basic infrastructure, that
is flexible enough to incorporate the more advanced components later on.

As said, I'm trying to get a proof of concept working within the next
couple of days (perhaps to end of next week). As soon this is there, I
will be able to increase the detail of the current draft. After that I
think the real work can start *g*

 
> I also have a little more time now, so I'm trying to get some
> development done.  My approach is to try to get some of the ideas I
> was working on before into use without rewriting Midgard as a whole.
> Your component idea might fit well into that.

Cool. Especially, if we could coordinate the effort, I'd like to see
some parts of the MidCom Code be transferred into Midgard itself.

Espically one thing: Dynamic Style Switching. I'd like a low-level
(read: C) Function that gives me a new syntax Element like this:
<[/path/to/style/anelement]> which loads the given element from the DB
and executes it.

Currently I'm planning doing this at PHP Level with mgd_eval style
solutions, but it is still very slow.

A more advanced version like "mgd_switch_style("/path/to/style")" which
loads the corresponding style would also be good as a _second_ way to
use Layout elemnts of other trees.


> Note that your global namespace might be an LDAP tree.  We were
> looking at this a long time ago (back in the Aurora days) and
> eventually let the idea drop.  But if we take a more pragmatic
> approach it could provide a first step, even if we decide to rip out
> the LDAP stuff in the end.  Imagine, for example, if you hacked up
> Alan's PHP Lite so that <[ldap:path]> (or something similar) used the
> standard PHP ldap functions to do an LDAP lookup on the variable.  I
> know it's not what you want in the end, but it's easy and might
> provide a starting point.

I wasn't using LDAP because I'm trying to keep things as simple as
possible. I don't want to integrate too much things into it at this
first stage, so I adapted SUN's naming conventions. They are good and
they work...


Live long and prosper!
Torben Nehmer

- --
Torben Nehmer, Munich, Germany
http://www.nathan-syntronics.de, mailto:[EMAIL PROTECTED]
PGP Public Key ID on wwwkeys.(de.)pgp.net: 0x7E9DE456
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Weitere Infos: siehe http://www.gnupg.org

iD8DBQE8hinvJPh4Kn6d5FYRArJ+AKDQQpKKUQ3LGOFODFYDPMep2ket0gCg2WMo
jZS455R9tWmneEaGk65j6lQ=
=I8W9
-----END PGP SIGNATURE-----


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to