[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-frameworks-devel
Subject:    Re: New framework: KCalCore
From:       Aleix Pol <aleixpol () kde ! org>
Date:       2019-04-15 13:05:13
Message-ID: CACcA1RpNDnvVpEaNACpgsA3joHkANxL=-mYmmo85FeN7TMsbmA () mail ! gmail ! com
[Download RAW message or body]

On Mon, Apr 15, 2019 at 2:52 PM David Jarvie <djarvie@kde.org> wrote:
>
>
>
> On 15 April 2019 13:25:56 BST, Allen Winter <allen.winter@kdab.com> wrote=
:
> > On Monday, April 15, 2019 6:40:06 AM EDT Daniel Vr=C3=A1til wrote:
> > > On Sunday, 14 April 2019 20:17:54 CEST David Faure wrote:
> > > > On dimanche 14 avril 2019 19:46:02 CEST David Jarvie wrote:
> > > > > On 14 April 2019 12:31:41 BST, David Faure <faure@kde.org>
> > wrote:
> > > > > > On dimanche 7 avril 2019 14:45:09 CEST Volker Krause wrote:
> > > > > > > Hi,
> > > > > > >
> > > > > > > I'd like to propose KCalCore for review to move from KDE PIM
> > to KF5.
> > > > > > >
> > > > > > > KCalCore is an implementation of the iCalendar standard
> > based on
> > > > > >
> > > > > > libical,
> > > > > >
> > > > > > I wonder about the name, which doesn't mean much outside the
> > circle of
> > > > > > PIM people. Shouldn't this be called KCalendar ?
> > > > > >
> > > > > > If the "Core" simply means non-GUI, we certainly don't have
> > that word
> > > > > > in every non-GUI framework.
> > > > >
> > > > > Renaming makes sense. KCalendar suggests it could be about
> > calendar
> > > > > systems,
> > > > Indeed.
> > > >
> > > > > so to avoid that confusion, perhaps call it KiCalendar?
> > > >
> > > > Doesn't read very well....
> > > > I would want to say KCalendarEvents but I guess the more correct
> > generic
> > > > term would be KCalendarIncidences ... not convicing either.
> > > >
> > > > Maybe KCal is enough? Reminds of iCal.
> > >
> > > Wasn't KCal the original name of the library from pre-Akonadi times?
> > KCalCore
> > > was a fork of KCal with the pre-Akonadi "Resources" system
> > removed...
> > >
> > Yep.  Back to the Future.  Let's stay away from "KCal" and "KCalendar"
> >
> > commit 6b4c1896211075fcd0b88b2c617eaacd831c9f6d
> > Author: Allen Winter <winter@kde.org>
> > Date:   Sat Jul 17 17:00:14 2010 +0000
> >
> >     Add the new KCalCore library.
> >
> >  The KCalCore library deprecates and mostly replaces the KCal library.
> >     KCalCore is free of any relation to the old Calendar resources and
> > focuses entirely on iCalendar and vCalendar storage and data
> > manipulation.
> >  KCalCore used QSharedPointers for safe memory access, is free of i18n
> >  strings and contains no methods for user interaction: KCalCore is all
> >     about the calendar data.
>
> Would KCalendarSerialization be a better name? I think that sums up its p=
urpose.
>
> --
> David Jarvie
> KAlarm author, KDE developer
> http://www.astrojar.org.uk/kalarm

KContacts is the framework dealing with vcards (which are equivalent
to iCal, for contacts). It makes sense to follow the same naming.

If we really don't want calendaring functions there, we could consider
calling it KiCal, I don't think it's that bad either and it's
definitely more self-explanatory. Or we call it KCalendar and allow
having calendar building blocks in it which could make sense as well,
if required.

Aleix
[prev in list] [next in list] [prev in thread] [next in thread]