> Second guessing past decisions is unlikely to be fruitful, I'm not > interested in recriminations, but I'm not sure we're all on the same > page about whether the existing architecture is problematic. Is there > frustration? How bad is that frustration? Where is it focused?
So, personally, the CPIA layer, which I think is persisting lots of things that seem to me to be UI details, is frustrating to work with. I'm also worried about the notification/observer universe, but (perhaps because I understand it better) I'm not particularly frustrated with this (except when I'm trying to improve performance). If I could, I'd back up to 2005 and model recurring events as one item, not many. The current model is frustrating to work with, but I'm not sure how feasible it would be to change this now, so I'm not thinking we'll change recurrence any time soon. I've been wondering if it would work to have a few developers work on replacing CPIA, without making radical changes to collections/notifications (for now). In this scenario I envisage most developers focusing on incremental bug fixes and small features that new users clamor for. Sincerely, Jeffrey _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
