[SailfishDevel] Minutes] SailfishOS community meeting 21.5. + planning for next one 11.6.

Andrey Kozhevnikov coderusinbox at gmail.com
Thu May 21 20:27:15 UTC 2015


I'm just giving you an idea how it used by developers :)

22.05.2015 01:25, Mohammed Hassan пишет:
> On Thu, May 21, 2015 at 11:38:08PM +0500, Andrey Kozhevnikov wrote:
>> Thank you for comments.
>>
>> No matter if QtDocumentGallery will be used or other backend, if
>> Sailfish.Pickers will be available to use (at least pages for selecting
>> media)
> If the Qt document gallery import is in one of the pickers then it means it
> is supported implicitly as you can create QML types from it.
>
>> For thumbnails i'm actively using video thumbnailer and nemomobile Thumbnail
>> component.
> That does not make them suitable for white listing unfortunately ;-)
>
> Cheers,
>
>> 21.05.2015 23:33, Mohammed Hassan пишет:
>>> On Thu, May 21, 2015 at 03:39:30PM +0000, Iekku Pylkka wrote:
>>>>   Hi,
>>>>   Thanks to everyone who attended today's meeting. Minutes/logs:
>>>>   Minutes:
>>>>
>>>>   [1]http://merproject.org/meetings/mer-meeting/2015/mer-meeting.2015-05-
>>>>   21-14.30.html
>>> I missed the meeting unfortunately but I feel I should comment on a few points:
>>>
>>> CameraExtensions: This is part of jolla camera and it was written AFAICT to work
>>> around the limitation of QtMultimedia declarative API. There is no point in allowing
>>> this in harbour since we are moving to QtMultimedia 5.5 in order to support GStreamer 1.x
>>> which should hopefully improve the situation.
>>>
>>> * QtDocumentGallery: This is not maintained upstream AFAIK and we might be the only
>>> users of such library. I would pretty much love to move away from it and use grilo
>>> instead. Once that happens we can start allowing anything that has been migrated
>>> in harbour.
>>>
>>> * Thumbnailing: We have 2 thumbnails in the platform. The nemo thumbnailer which provides
>>> only QML API (Used by UI apps) and tumbler which is used by buteo for MTP. Both of them need
>>> to e merged together and perhaps a C++ library should be written on top of which we can have
>>> a declarative bindings.
>>>
>>> I have just commented on the bits I know and on why they cannot be allowed in harbour
>>> for the time being. Help is of course greatly welcomed :-)
>>>
>>> Cheers,
>>> _______________________________________________
>>> SailfishOS.org Devel mailing list
>>> To unsubscribe, please send a mail to devel-unsubscribe at lists.sailfishos.org
>> _______________________________________________
>> SailfishOS.org Devel mailing list
>> To unsubscribe, please send a mail to devel-unsubscribe at lists.sailfishos.org
> _______________________________________________
> SailfishOS.org Devel mailing list
> To unsubscribe, please send a mail to devel-unsubscribe at lists.sailfishos.org



More information about the Devel mailing list