[Kde-pim] KDEPIM 4.0

[David Jarvie]

On Friday 23 March 2007 22:11, mark at easymailings.com wrote:
>> Am Freitag, 23. März 2007 schrieb mark at easymailings.com:
>
>>> Isn't this a problem of implementation rather than interface?
>>
>> No, it's a more fundamental problem of the way the whole resource
> system
>> is
>> designed.
>
> [snip detailed explanation of problem]
>
> So one possible fix is:
>
>     (1) downgrade all async load methods wrap synchronous
> ones, and
>
>     (2) use pessimistic locking instead of optimistic for
> all updates/
>
> I think this could be done w/o changing the interface.  Data loss
> sucks big time, and option (1) is a far superior option (IMHO).

This is only one aspect of the problem. The other is that the resources
classes are designed specifically for KOrganizer. To make them generally
usable for other applications requires a redesign which would certainly
involve changing the interface - currently it simply isn't possible to
inherit the resources classes to tailor them; instead it's necessary to
copy and alter them. Probably a greater use of template classes would be
necessary, but I haven't really thought how it could be done.

-- 
David Jarvie.
KAlarm author & maintainer.
http://www.astrojar.org.uk/kalarm

_______________________________________________
kde-pim mailing list
kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/