-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
- --- On 11.08.04 11:41 (+0200) Pascal Mayer wrote:
But I didn't clearly describe which "NAP" I am referring to :)
tnn> NAP does distinguish between Admin- and Site-URLs. Either of the tnn> two can be NULL, indicating the inavailability of a given leaf in tnn> the corresponding mode. This is true only for leaves, not for tnn> nodes. A leafe retrival might look like this:
The taviewer component as an example has different "action-links" depending on the current object (leaf/node) and current view.
"View, Delete, Approve, Create Article, Settings" or "Edit, Delete, Approve, Create Article, Settings" or just "Settings" ...
Are those links/actions retrievable from the component? It seems that they are hard-coded inside the styles of the components...?
Unfortunalety, they are. The NAP subsystem does not yet support different links into the AIS per leaf. I have some ideas how to implement this though, as it is on my todo list, but it involves rather extensive changes on the NAP subsystem, as I want to integrate a generic metadata handler (for things like approval or hiding of elements), which is not trivial. I haven't found the spare time yet to implement this, and I can't give you an ETA right now, as the stuff mentioned in mRFC 0006 (Midgard Website, Community, Development) is on top of my priority list right now.
Live long and prosper! Torben Nehmer
- -- Torben Nehmer, Guenzburg, Bavaria, Germany
http://www.nathan-syntronics.de, mailto:[EMAIL PROTECTED]
PGP Public Key: https://www.link-m.de/pgp/t.nehmer.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iD8DBQFBGfkvJPh4Kn6d5FYRApCdAJwPWEcC6r90Ag2JGxr1jy95V9WjOwCeKw2J L7uDCmxqHmJDb1seZSCIyao= =PE0I -----END PGP SIGNATURE-----
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
