Digikam/GSoC2012/CameraUserInterfaceRevamp: Difference between revisions

From KDE Community Wiki
No edit summary
mNo edit summary
Line 17: Line 17:
In more detail: Write a model listing images on a camera (There are two backends, USB mass storage cameras, which are basically files on disk, and GPhoto2 cameras, which require access through a library). Take the existing digikam icon view and delegate classes, which are prepared for code re-use, and put together an icon view for the model. Cleanly separate the code that does the actual work (downloading, converting, renaming) from the UI. Wrap that in the main window.
In more detail: Write a model listing images on a camera (There are two backends, USB mass storage cameras, which are basically files on disk, and GPhoto2 cameras, which require access through a library). Take the existing digikam icon view and delegate classes, which are prepared for code re-use, and put together an icon view for the model. Cleanly separate the code that does the actual work (downloading, converting, renaming) from the UI. Wrap that in the main window.


User Interface design: the current one is powerful, exposing many options. We want to preserve that. But at the same time, there are three very common actions: a) Download all new files to the last used album b) Download all new files to a new album c) Download all new files to an existing album.
User Interface design: the current one is powerful, exposing many options. We want to preserve that. But at the same time, there are three very common actions:  
 
a) Download all new files to the last used album  
 
b) Download all new files to a new album  
 
c) Download all new files to an existing album.
 
It should be possible to carry out task (a) with one click, task (b) and (c) with two or three clicks, without opening a dialog. Friendly to the new user, preserving access to all options for the poweruser.
It should be possible to carry out task (a) with one click, task (b) and (c) with two or three clicks, without opening a dialog. Friendly to the new user, preserving access to all options for the poweruser.


Line 38: Line 45:
= Description & Related Work =
= Description & Related Work =
== Introduction ==
== Introduction ==
Here is a [https://projects.kde.org/projects/extragear/graphics/digikam/repository/revisions/master/entry/utilities/cameragui/TODO technical TODO list] relevant of this project


=== Scope ===
=== Scope ===




== Design ==
== Design ==


More detailed information can be found in the [.pdf Specification]
=== UI/UX Design ===


== Implementation ==
== Implementation ==
Line 53: Line 58:


= Affected Modules =
= Affected Modules =


===Primary Modules===
===Primary Modules===
Line 98: Line 104:


== TODO ==
== TODO ==
Here is a [https://projects.kde.org/projects/extragear/graphics/digikam/repository/revisions/master/entry/utilities/cameragui/TODO technical TODO list] relevant of this project.
{| style="width: 100%"
{| style="width: 100%"
|-
|-

Revision as of 00:48, 7 March 2012

Digikam GSoC 2012 Camera User Interface Revamp

This page is meant to gather information about the GSoC 2012 Idea, Camera User Interface Revamp.

Requirements and Considerations

Summary

DigiKam features a graphical interface to access and download pictures from digital cameras. Code is rather old, using Qt3Support classes for the icon view, the UI code intermangled deeply with backend code, and has not seen very much care and love for some years.

This project would involve taking the old code apart, rewriting a clean code base backend and front-end, but also adding user interface elements to make the most important everyday task as easy as possible.


More Details

In more detail: Write a model listing images on a camera (There are two backends, USB mass storage cameras, which are basically files on disk, and GPhoto2 cameras, which require access through a library). Take the existing digikam icon view and delegate classes, which are prepared for code re-use, and put together an icon view for the model. Cleanly separate the code that does the actual work (downloading, converting, renaming) from the UI. Wrap that in the main window.

User Interface design: the current one is powerful, exposing many options. We want to preserve that. But at the same time, there are three very common actions:

a) Download all new files to the last used album

b) Download all new files to a new album

c) Download all new files to an existing album.

It should be possible to carry out task (a) with one click, task (b) and (c) with two or three clicks, without opening a dialog. Friendly to the new user, preserving access to all options for the poweruser.


Creation Date 14-February-2012
Status Proposal
Maintainers Gilles Caulier - Development Marcel Wiesweg - Development Islam Wazery - Development

Description & Related Work

Introduction

Scope

Design

UI/UX Design

Implementation

Project repository: [1]

Affected Modules

Primary Modules

Name of module Description of changes

Secondary Modules

Name of module Description of changes

Relevant Bugs

URL Name of Bug
121310 Allow to have a group of pictures.
126149 Camera stores both jpeg and raw (nef), handle both as one.
158437 Add ability to create/assign tags to pictures while importing.
216491 Camera interface view does not work to preview movies.


Project Timeline

TODO

Here is a technical TODO list relevant of this project.

Milestone name Milestone description Assigned to Status
Islam Wazery In Progress

Completed

Milestone name Milestone description Assigned to Status


Note

Please use the talk page to discuss this proposal.