On Wednesday, 2014-01-15, 16:19:43, Mitch Curtis wrote: > On 01/15/2014 02:27 PM, Kevin Krammer wrote: > > On Wednesday, 2014-01-15, 00:14:37, Martin Klapetek wrote: > >> On Wed, Jan 15, 2014 at 12:09 AM, Mark Gaiser <[email protected]> wrote: > >>> Just events? No todo, journal and holiday? > >>> Or is "everything" a "event"? > >> > >> Yes, everything is an event which has a type property, which can be todo, > >> journal or holiday (or whatever). > > > > I am not sure if this is wise. On the calendaring level there will be > > events, todos, etc. > > Using "Event" in QML for the base type (ical calls them "calendar > > components", KDE's calendaring library calls them "incidences") might > > lead to confusions when applications handle things from both C++ and QML. > > > > Cheers, > > Kevin > > Also, Qt Quick Controls can't have C++ classes exposed. I would prefer > that we first make it possible to integrate your own events into the > Calendar somehow.
Makes sense. Just had to chime in on the idea that TODOs, etc were also
events, which they are not.
> During the sprint in Barcelona, I was told that events for the calendar
> in Plasma are stored in an SQL database. How about this:
We get them from a service (communicating through QLocalSocket).
> Calendar doesn't expose any model; any extra data that you want to
> associate with a date is managed by you. In the case of Plasma:
>
> Calendar {
> SqlCalendarModel { id: eventsSqlModel }
>
> style: CalendarStyle {
> dateDelegate: Rectangle {
> // ...
>
> Text {
> text: eventsSqlModel.eventAt(index).eventName
> }
> }
> }
> }
Sounds like a good approach to me.
Cheers,
Kevin
--
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Plasma-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/plasma-devel
