Calligra/Words: Difference between revisions
No edit summary |
No edit summary |
||
(15 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
[[ | [[Category:Words]] | ||
'''Calligra Words''' is for creating word processing documents, and not for desktop | |||
publishing. Our focus is to provide a powerful and easy to use experience for | |||
everyone without being the specialized tool for any specific group of users. | |||
That said we try to have enough separation in our code that people (maybe even | |||
ourselves in the future) can create extra plugins or custom user interfaces. | |||
Here are some pages with more details and design documents (most is leftover from KWord though); | |||
=Current Design Explanation= | =Current Design Explanation= | ||
* [[Calligra/Words/Tutorials]] List of tutorials relating to ODF and | * [[Calligra/Words/Tutorials]] List of tutorials relating to ODF and Words | ||
* [[Calligra/Words/Tables]] The tables in | * [[Calligra/Words/Tables]] The tables in Words are based on Qt tables, here is how Qt tables work at the low low level. | ||
* [[Calligra/Words/RequirementSpecifications/ChangeTracking]] Requirement specifications for Change tracking. | * [[Calligra/Words/RequirementSpecifications/ChangeTracking]] Requirement specifications for Change tracking. | ||
* [[Calligra/Words/Outline]] | |||
* [[Calligra/Text Layout]] | |||
= | =User interface Design= | ||
* [[Calligra/ | * [[Calligra/End_2010_Text_Styles_UI_IRC_Meeting]] A re-work of the text styles tree. | ||
= Usecases for new tech or 'in-development' stuff = | = Usecases for new tech or 'in-development' stuff = | ||
Line 22: | Line 25: | ||
=End User Ready= | =End User Ready= | ||
In order to make | In order to make Words end user ready we have to know who the end user is. Turns out that there are different definitions which give different answers. The full details can be found at [[Calligra/Words/EndUserReady/Personas]] | ||
=Bug processing = | =Bug processing = | ||
The Calligra Words bugs are first triaged and prioritized. Depending on interest from developers (often related to priority but not nessessarily so) | |||
the fixing will start. This can be anywhere from immidiately to several years later | |||
Prioritization is based on being ready for a basic user like [[Calligra/Words/EndUserReady/Personas|Susan]] or for a more specilized user like A.D.Vance. | |||
Right now we have plenty to do to support Susan, so it's quite unlikely the advanced cases will have much interest, but this is open source, and everybody is free to do what they want, so you never know ;) | |||
* | =See also= | ||
* | *[[/DanskInterop/]] | ||
*[[/Requirement Specifications//]] |
Latest revision as of 00:36, 9 March 2012
Calligra Words is for creating word processing documents, and not for desktop publishing. Our focus is to provide a powerful and easy to use experience for everyone without being the specialized tool for any specific group of users. That said we try to have enough separation in our code that people (maybe even ourselves in the future) can create extra plugins or custom user interfaces.
Here are some pages with more details and design documents (most is leftover from KWord though);
Current Design Explanation
- Calligra/Words/Tutorials List of tutorials relating to ODF and Words
- Calligra/Words/Tables The tables in Words are based on Qt tables, here is how Qt tables work at the low low level.
- Calligra/Words/RequirementSpecifications/ChangeTracking Requirement specifications for Change tracking.
- Calligra/Words/Outline
- Calligra/Text Layout
User interface Design
- Calligra/End_2010_Text_Styles_UI_IRC_Meeting A re-work of the text styles tree.
Usecases for new tech or 'in-development' stuff
- Calligra/Words/Master Documents Explains how a master document can make life easier.
- Calligra/Libs/KoText/Change tracking What do we want to do with Change Tracking then?
- Calligra/Libs/KoText/Text Plugins Usecases for writing plugins for the text shape. And which technology to use.
- Calligra/Words/Scripting Scratchpad for scripting. Nothing final, just designing at the moment. Input welcome.
End User Ready
In order to make Words end user ready we have to know who the end user is. Turns out that there are different definitions which give different answers. The full details can be found at Calligra/Words/EndUserReady/Personas
Bug processing
The Calligra Words bugs are first triaged and prioritized. Depending on interest from developers (often related to priority but not nessessarily so) the fixing will start. This can be anywhere from immidiately to several years later
Prioritization is based on being ready for a basic user like Susan or for a more specilized user like A.D.Vance.
Right now we have plenty to do to support Susan, so it's quite unlikely the advanced cases will have much interest, but this is open source, and everybody is free to do what they want, so you never know ;)