GSoC/2015/StatusReports: Difference between revisions

From KDE Community Wiki
< GSoC‎ | 2015
Line 21: Line 21:
''' This is what I learned during GSoC: '''
''' This is what I learned during GSoC: '''


== Student Name ==  
== Mohamed Anwer ==  


'''Project Name:'''  
'''Project Name:''' [digiKam] Rewrite database KIO-slaves as pure Qt5 with multithreading


'''A  Brief Description:'''   
'''A  Brief Description:'''  Originally, KIO-Slaves was implemented to run database queries in a separate process to prevent problems with SQlite. Since SQlite support queries from separate threads, KIO-slaves can be dropped, and a new API can be implemented using pure Qt threads API. This will improve digiKam portability, and permit adjusting CPU cores assigned to database processes efficiently.


''' Status: '''
''' Status: ''' In progress


''' Screenshot: '''
''' Screenshot: '''


''' IRC Nick: '''  
''' IRC Nick: ''' tootis


''' IRC Channels: '''  
''' IRC Channels: ''' #digikam


'''Blog: '''  
'''Blog: ''' https://mohamedanwer.wordpress.com


''' This is awesome about GSoC: '''
''' This is awesome about GSoC: '''

Revision as of 14:39, 30 May 2015

Status reports for GSoC, OPFW and SoK 2015.

Student Name (Please leave this as a template and make a copy for yourself!)

Project Name:

A Brief Description:

Status:

Screenshot:

IRC Nick:

IRC Channels:

Blog:

This is awesome about GSoC:

This is what I learned during GSoC:

Mohamed Anwer

Project Name: [digiKam] Rewrite database KIO-slaves as pure Qt5 with multithreading

A Brief Description: Originally, KIO-Slaves was implemented to run database queries in a separate process to prevent problems with SQlite. Since SQlite support queries from separate threads, KIO-slaves can be dropped, and a new API can be implemented using pure Qt threads API. This will improve digiKam portability, and permit adjusting CPU cores assigned to database processes efficiently.

Status: In progress

Screenshot:

IRC Nick: tootis

IRC Channels: #digikam

Blog: https://mohamedanwer.wordpress.com

This is awesome about GSoC:

This is what I learned during GSoC: