-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi.
- --On 07.03.2002 08:30:43 +0100 Emiliano wrote: >> > Easy, that's just a few lines of code, given that you have the >> > style element ID at hand. >> >> Element ID's bad... It has to be name based, otherwise using it for >> the component system is not possible. > > Element names are not unique. They are withhin their style... >> So the idea of "routing" the request to a real style. This style has >> elements with exactly the same names as the snippets in the layout >> tree. A set of custom function then fetches this element. (Even >> support of style element inheritance is planned.) Because this is not >> trivial, the idea of putting this logic into Midgard lead me to the >> "<[/path/to/style/element]>" approach, using clear text names as only >> possible reference to the element (what could be replaced with IDs >> (or GUIDs at least) would be the reference to the style itself. But >> even there the path would be preferable). > > The path to elt could work. Note that style names need not > (technically) be unique. Shouldn't Midgard enforce unique Style names within a given part of a tree, as it does with unique article names? It should be, if you ask me. At least for the sake of consistency, because everywhere else I have to follow the rule that a name has to be unique. Thats why we have the get_xxx_by_name functions, don't we? 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 iD8DBQE8hzu9JPh4Kn6d5FYRAmoDAJ4ys5TvPVRy30cNZQ7rhZEiETAhtwCfa2QO OhCU1nlY+CYr1gkt4ViMOSM= =UldO -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
