GSoC 2012 Improve Usability Chelen: Difference between revisions

From Scribus Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
[[Category:GSOC2012]][[Category:GSOC]]
[[Category:GSOC2012]][[Category:GSOC]]


Project : '''Improve usability and get rid of little bugs'''
===Improve usability and get rid of little bugs===


   
   
Line 8: Line 8:




<big>'''Undo-redo'''</big>
==Undo-redo==




When we speak about user-friendliness, it also means that Scribus has to do what the user expect it does. We can notice that it remains some bug in undo/redo functionalities. Hence, it will be one of the main part of this proposal.
When we speak about user-friendliness, it also means that Scribus has to do what the user expect it does. We can notice that it remains some bug in undo/redo functionalities. Hence, it will be one of the main part of this proposal.


<big>Description</big>
<big>'''Description'''</big>


Currently, undo/redo is absent in for some functionality (changing style character http://bugs.scribus.net/view.php?id=10310) or have an abnormal behaviour (with pattern/graphic http://bugs.scribus.net/view.php?id=6220 , http://bugs.scribus.net/view.php?id=5210 , http://bugs.scribus.net/view.php?id=5210 or about save functionality http://bugs.scribus.net/view.php?id=3455). As we can see with those examples, there are some improvement to do in these case and especially with undo/redo when we resize/rotate a frame or a graphic.
Currently, undo/redo is absent in for some functionality (changing style character http://bugs.scribus.net/view.php?id=10310) or have an abnormal behaviour (with pattern/graphic http://bugs.scribus.net/view.php?id=6220 , http://bugs.scribus.net/view.php?id=5210 , http://bugs.scribus.net/view.php?id=5210 or about save functionality http://bugs.scribus.net/view.php?id=3455). As we can see with those examples, there are some improvement to do in these case and especially with undo/redo when we resize/rotate a frame or a graphic.
We can also notice that story editor lack undo/redo functionalities but cezary have already programmed that and will export his word from 1.4 to 1.5.
We can also notice that story editor lack undo/redo functionalities but cezary have already programmed that and will export his word from 1.4 to 1.5.


<big>Implementation</big>
<big>'''Implementation'''</big>


-I will firstly look at abnormal behaviour. Most of the time, it is due to separation between different basic actions. As Scribus can remember only 20 actions, this issue filled this queue and the user is enable to undo this action.
-I will firstly look at abnormal behaviour. Most of the time, it is due to separation between different basic actions. As Scribus can remember only 20 actions, this issue filled this queue and the user is enable to undo this action.

Revision as of 23:53, 26 March 2012


Improve usability and get rid of little bugs

As this subject suggest, it will not be just one big task but different little ones to improve user-friendliness of Scribus. During the GSoC, I will focus on two goal:


Undo-redo

When we speak about user-friendliness, it also means that Scribus has to do what the user expect it does. We can notice that it remains some bug in undo/redo functionalities. Hence, it will be one of the main part of this proposal.

Description

Currently, undo/redo is absent in for some functionality (changing style character http://bugs.scribus.net/view.php?id=10310) or have an abnormal behaviour (with pattern/graphic http://bugs.scribus.net/view.php?id=6220 , http://bugs.scribus.net/view.php?id=5210 , http://bugs.scribus.net/view.php?id=5210 or about save functionality http://bugs.scribus.net/view.php?id=3455). As we can see with those examples, there are some improvement to do in these case and especially with undo/redo when we resize/rotate a frame or a graphic. We can also notice that story editor lack undo/redo functionalities but cezary have already programmed that and will export his word from 1.4 to 1.5.

Implementation

-I will firstly look at abnormal behaviour. Most of the time, it is due to separation between different basic actions. As Scribus can remember only 20 actions, this issue filled this queue and the user is enable to undo this action.

-Then, I will add this functionality where it is missing like with style to be sure that the user can always come back when he does a mistake.

-To see until where he can come back. It could be great to add a widget with an history. With this, the user can see if the action that he want undo is again in the queue and he can select where he wants to come back without clicking to many time.

This page will be complete soon!