AbiWord26Plans
From AbiWiki
(Difference between revisions)
(Importing text file) |
(→Proposed plans for AbiWord 2.6) |
||
| Line 1: | Line 1: | ||
| - | ==== Proposed plans for [[AbiWord|AbiWord]] 2.6
==== | + | ==== Proposed plans for [[AbiWord|AbiWord]] 2.6 |
| + | ==== | ||
[[AbiWord|AbiWord]] 2.5 has been released, that means features that are currently not in won''t be available for 2.6. Plans are not automatically migrated because developer resources and focus may change. | [[AbiWord|AbiWord]] 2.5 has been released, that means features that are currently not in won''t be available for 2.6. Plans are not automatically migrated because developer resources and focus may change. | ||
| - | + | In | |
* libgsf everywhere | * libgsf everywhere | ||
| Line 13: | Line 14: | ||
* Toolbars: some work has been done | * Toolbars: some work has been done | ||
| - | + | Not in: | |
* merge Marc "double graphics" patch to use float/double for any measurement | * merge Marc "double graphics" patch to use float/double for any measurement | ||
| Line 19: | Line 20: | ||
* dialog framework and refactoring. Can be done progressively and will reduce tremendously the amount of code to implement the platform code. The word count dialog already does that on UNIX and Mac, and I sort of plan on installing libwine to try it on Windows with my limited capabalities | * dialog framework and refactoring. Can be done progressively and will reduce tremendously the amount of code to implement the platform code. The word count dialog already does that on UNIX and Mac, and I sort of plan on installing libwine to try it on Windows with my limited capabalities | ||
| - | + | performance: we have serious performance issues. they should be investigated and addressed. | |
* better toolbars | * better toolbars | ||
| Line 26: | Line 27: | ||
** Apple Page like (see rob) | ** Apple Page like (see rob) | ||
| - | + | usability: there are a lot of areas where our usability suck, including but not limited to stylesheets management. Lot of things need to be improved and I''m sure that the above refactoring would help us to do so easier. | |
** stylesheet ui | ** stylesheet ui | ||
** context menus | ** context menus | ||
| Line 36: | Line 37: | ||
--> | --> | ||
| + | |||
==== Contributors
==== | ==== Contributors
==== | ||
* Main.[[HubertFiguiere|HubertFiguiere]] - 28 Sep 2005 | * Main.[[HubertFiguiere|HubertFiguiere]] - 28 Sep 2005 | ||
[[Category:To Convert]] | [[Category:To Convert]] | ||
Revision as of 21:48, 14 February 2011
==== Proposed plans for AbiWord 2.6
==
AbiWord 2.5 has been released, that means features that are currently not in wont be available for 2.6. Plans are not automatically migrated because developer resources and focus may change.
In
- libgsf everywhere
- UnitTest improvements
- Toolbars: some work has been done
Not in:
- merge Marc "double graphics" patch to use float/double for any measurement
- dialog framework and refactoring. Can be done progressively and will reduce tremendously the amount of code to implement the platform code. The word count dialog already does that on UNIX and Mac, and I sort of plan on installing libwine to try it on Windows with my limited capabalities
performance: we have serious performance issues. they should be investigated and addressed.
- better toolbars
- tool palette: the tool palette that is currently cocoa specific should be made XP.
- customizable
- Apple Page like (see rob)
usability: there are a lot of areas where our usability suck, including but not limited to stylesheets management. Lot of things need to be improved and Im sure that the above refactoring would help us to do so easier.
- stylesheet ui
- context menus
- editing
- units everywhere we use dimensions
Contributors
- Main.HubertFiguiere - 28 Sep 2005
