Marco wrote:
Lennart Regebro wrote:
Is somebody working on transforming this skins templet into a portlet?
No, there are no such plans. Is there a problem with it being a templet?
1. The calendar is content and not layout.
2. Therefore different persons are working on it.
3. Different permissions are necessary.
> 4. The templet has no attribute for the source paths.
OK, I don't know enough about CPSSkins to understand why this makes a
difference. :)
Or will the CPSSharedCalendar portlet be able to display event docs, too?
No.
Is there a principle reason for it?
Partly, yes. The CPSSharedCalendar portlet is a CPSSharedCalendar
portlet and shows CPSSharedCalendar events. But the main reason is that
Nuxeo doesn't have any use for it, so we will not do it. If somebody
else wants to, then they are welcome, it is open source after all. :)
However, it seems to me that if you want a portlet for CMFCalendar
events, then that's what you should have, not try to force the
CPSSharedCalendar portlet to do it. :)
Unfortunately I don't have the knowledge
to do it my self. But I think it should be very easy since it only needs to
read a few attributes from the event doc, no need for manipulating the
event docs, just link to it.
Yes, but that's a completely different story from what it does now. The
events are different types of objects, they are found in a different
way, and the attributes have different names.
--
Lennart Regebro, Nuxeo http://www.nuxeo.com/
CPS Content Management http://www.cps-project.org/
_______________________________________________
cps-users mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/cps-users
