Philip Bauer

That is unfortunate especially since it's documented in http://chameleon.readthedocs.org/en/latest//reference.html#tal-repeat I never used `first` before but now that I see it I like it

I don't think implementing it is up my alley but I'll try to explain it allthough the example from the chameleon-docs is kinda self-explaining: ``` Meta Type Object ID ```...

I like the ability to filter by source and target. But I don't really understand how the output in the screenshot should work. When relations always point from one content...

Part 1 already works. Part 2 is still missing.

@dataflake thanks for the info. I don't get why `tal:content="python:template.macros"` does not work in Plone (we use Zope 4.0b10 which has the mentioned fix).

I frequently used the option to use `kill -s SIGUSR1 ` to get a stacktrace of a running instance without halting it. I'm not sure if that's directly related but...

I think to support all use-cases that `plone.api` and the relations-controlpanel (`@@inspect-relations` and `@@rebuild-relations`) offer we need 2 endpoints with different names. E.g. `@contentrelations` which operates on the context and...

We discussed it some more and would propose the names `@relations` for the endpoint that uses the context (by default as source) and `@manage-relations` for the endpoint on the portal...

We discussed it again some more and @sneridagh and me agreed that `@relations` and `@relations-catalog` might be a good choice.

That's not really a open decision since the site-root is now dexterity and has a intid it can have relations. The use-case to relate from there to other content also...