QML Calendar components for Akonadi in scratch repo

[Mark]

On Mon, Jul 15, 2013 at 7:32 PM, Kevin Krammer <krammer at kde.org> wrote:
> On Monday, 2013-07-15, Mark wrote:
>> On Sun, Jul 14, 2013 at 7:58 PM, Kevin Krammer <krammer at kde.org> wrote:
>
>> > I am not sure if the components from runtime are used anywhere, or if
>> > they are anywhere outside Kontact Touch.
>> > It could be a dependency thing, i.e. not making kdepimlibs depend on
>> > QtDeclarative.
>> >
>> > So I think you are right that for the moment runtime would be the obvious
>> > choice.
>> >
>> > However I don't think it would be confusing to have different things in
>> > different modules.
>> > QML using developers wouldn't care since they would use import and let
>> > the declarative engine handle the plugin lookup, no?
>>
>> Yeah, you're right. What would you suggest, move those calendar
>> components to kdepimlibs asap or keep them in runtime for the time
>> being?
>> And what to do with the other components in kdepim-runtime? Since they
>> probably should all be placed in kdepimlibs i guess.
>
> I'd like to dicuss this first to find out whether the placement was because of
> the QDeclarative dependency.

If you want and have the time, you can discuss it there at akademy
since most folks are there anyway. Otherwise we probably would have to
discuss this at the next pim sprint in a few months. I hope the
components are done before that though :) at least the reading part,
updating/deleting/adding events is a whole different beast to tackle.

>
>> From my point of view it doesn't matter where they are, but i prefer
>> them to be in the right location from the start and not leaving them
>> in runtime for a few months before moving them to kdepimlibs.
>
> Well, something moving from an App module to a library module happens all the
> time, essentially when more than one applications wants to use the same stuff.
> Since the App module depends on the library module there is no change in
> availability either.

It's easier for me as well if it stays in one place and stays there :)
>
> In the current situation timing is less of an issue, the feature freeze for
> 4.12 will be in October or November.

Actually.. i don't mind those sets to be "KDE 5" material. It can't be
used for any KDE 4.x series anymore since the workspace is on lockdown
after 4.11 thus those components can't even be used to recreate the
calendar popup for 4.11 or 4.12..
>
> Cheers,
> Kevin
> --
> Kevin Krammer, KDE developer, xdg-utils developer
> KDE user support, developer mentoring
>
> _______________________________________________
> Plasma-devel mailing list
> Plasma-devel at kde.org
> https://mail.kde.org/mailman/listinfo/plasma-devel
>