[Chandler-dev] Framing discussion about desktop architecture
grant at osafoundation.org
Wed Sep 12 14:14:04 PDT 2007
I meant to reply to your email early, sorry.
Personally, I've been considerably frustrated by how hard it is to
write code on our project. I don't work so much at the CPIA layer,
but below that the "brittle" and largely undocumented API problem
really impacts my productivity, whether it's because it makes making
changes more difficult, or whether it's because I'm often having to
be distracted to revisit old changes that have turned out to have had
surprising and negative consequences.
I can elucidate exactly which brittleness I find difficult, but this
is the high-level picture. I feel strongly enough about all this that
I'm quite sure I would be pretty unhappy chipping away at the code
base the same way that I have for the past 12 months.
On 6 Sep, 2007, at 17:28, Jeffrey Harris wrote:
>> 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
>> 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
> 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
> 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.
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> Open Source Applications Foundation "chandler-dev" mailing list
More information about the chandler-dev