I've been working on making the Calendar Control more of a reusable control rather than using the @DbLookup calls within the ccCalendar control itself. For the most part, I've succeeded in doing this however before I publish it I need some information as it doesn't quite work the way I expect it to.

So, here's the scenario. I've busted the code within the dayCells computed field to only contain the beginning cell HTML, basically the opening TD call. I then added another computed field to handle the closing of the TD. Now, in between these 2 I've placed an editable area. This editable area shows up in the design mode for the ccCalendar Custom Control. Now, when we drag the ccCalendar custom control onto a new XPage, the editable area is visible however you can't drag another custom control onto it. When you try it drops the control above everything else. Also, when you look at the source for the XPage before adding a custom control onto the editable area, there is no xp:this.facets tag. Now I can add this tag manually and define the custom control I created just to display the data and it all works flawlessly but I don't like that I have to hand code it. But below is some screen shots and a short screen cast of the behaviour I'm attempting to describe:

Here is the control after I dropped it onto a new XPage. See the Editable Area is available:


Here is the entire source of the new XPage, notice there is no xp:this.facets tag:


Here is the Screen Cast of what happens when you try to drop a custom control onto this editable area:

So, my question is this.... Should you add an Editable area within a repeat? If not, what is a better route?