Wouldn't it be kind of a small component if we restrict it to just
calendar stuff?
My opinion on this is to just keep it with the other stuff in the
service component, since we already have things there. Hopefully there
has been enough discussion about it and there is enough precedent with
the recurrence entities that people won't have a hard time with it.
Don't worry too much about it. It is what it is, and it's okay.
-David
On Oct 3, 2008, at 9:21 AM, Adrian Crum wrote:
As was discussed before, I had a hard time deciding where to put the
new temporal expression stuff because of dependencies in the build
process. I ended up putting it in the service component in order to
get everything to compile okay, but seriously, it doesn't make sense
having it there.
I have more calendar-related classes I want to introduce to the
project, and I will end up having the same problem with those. I
don't want to put everything in service. I need a new folder in the
framework folder.
The calendar classes (recurrence and temporal expression) depend
upon the base and entity components. The service component depends
upon the calendar classes (for job scheduling). So, I need the new
folder to be in between entity and service in the build process.
I'd like to add a calendar folder to the framework folder. It would
contain all of the existing recurrence classes, the temporal
expression classes, and the yet-to-be-committed classes.
I wouldn't suggest this if I could find some other logical way to
place things.
What do you think?
-Adrian
