<br><br><div class="gmail_quote">On Fri, Oct 7, 2011 at 1:39 PM, C. Boemann <span dir="ltr"><<a href="mailto:cbo@boemann.dk">cbo@boemann.dk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi fellow Words developers<br>
<br>
The sprint is nearing and I think it's time to start thinking about what we<br>
should do. The following is up for discussion at the sprint but I'd like to<br>
get a head start:<br>
<br>
Mission statement<br>
------------------------<br></blockquote><div><br>Ahhh, C.Boemann, you definitely know how to speak to the former Quality Assurance Manager in me!!!!!!<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Inspired by Krita we should come up with a mission statement. Here is a<br>
suggestion:<br>
<br>
"Calligra Words is an all purpose word processor useful for writing such<br>
diverse documents as for example: A simple letter, a university dissertation,<br>
a rule book, school reports and much more.<br>
<br>
We will not provide very specialized features if they clutter the user<br>
interface, but on the other hand should try to be flexible enough that people<br>
can create their own plugins.<br>
<br>
As examples we find changetracking a core feature, but a function that<br>
generates custom documents based on external input is not"<br></blockquote><div><br>I agree with the general scope given. I am not sure we need to give so much specifics in a mission statement (practical examples do not fit to a mission statement IMHO).<br>
We ought to make a small session during the sprint about the subject, and the one below (which is linked). I'll like it, it'll remind me of my former life ;)<br>I can take on responsibility for animating this session too if you want.<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
Road map<br>
------------<br>
With such a broad mission statement we need to limit ourselves initially. Not<br>
to the point of excluding contributions, but in defining what we, the core<br>
developers, will focus on.<br>
<br>
I suggest that we will target the university student. Meaning we should be<br>
able to view MS Word documents and be able to create from scratch reports and<br>
dissertations.<br>
<br>
The viewer part is not strictly needed but if a user is not able to view<br>
documents the user will choose another tool for viewing, and thus choosing<br>
Words for creating documents becomes very unlikely.<br>
<br>
For the creation part we need to support creation and editing of tables,<br>
change tracking, foot notes, endnotes, bibliography, basic page setup, images,<br>
and style management.<br>
<br>
We are already pretty far along this road (it's been an unspoken roadmap for<br>
quite a while) I suggest that we just keep on pushing for these features to<br>
mature and stabalize.<br>
<br>
In 8 months we ought to be really strong with these kinds of tasks.<br>
<br>
User interface<br>
------------------<br>
At the usability sprint in Berlin two weeks after the first Calligra sprint<br>
(also in Berlin) Celeste lead a small design process for the overall user<br>
interface for Words. As with all usability designs it has to undergo iterative<br>
finetuning and experimentation, but I quite like it already.<br>
<br>
I've implemented the idea but we need to carry on from there and continue<br>
improving the user interface.<br>
<br>
<a href="http://wstaw.org/m/2011/10/04/wordsui.png" target="_blank">http://wstaw.org/m/2011/10/04/wordsui.png</a><br></blockquote><div><br>That is definitely something we need to plan at the sprint. I have made quite some progress on the style widget (although i have had some IRL constraints which pulled me a bit away as of late).<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
kotext, textlayout, textshape, words division of responsibilities<br>
-----------------------------------------------------------------------------------<br>
We should come up with a plan for how we want the code structured in the long<br>
run. We've come a long way already, but we should discuss what further things<br>
we can do.<br></blockquote><div><br>As far as I know there is already a session planned that I'll animate on this very topic.<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
KoTextEditor hacking<br>
---------------------------<br>
I'd like a hacking session where we start extending the functionality of<br>
KoTextEditor.<br></blockquote><div><br>This is sort of influenced by the topic above.<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
Changetracking<br>
--------------------<br>
I'd like a brainstorm on how we proceed on change tracking. The current state<br>
leaves much to be desired.<br></blockquote><div><br>For this, i think there are some external constraints that we do not control entirely. There are some stuff needed internally though that we need to discuss (like the "post-it notes"/"notes bubbles" stuff).<br>
<br>PierreSt</div></div>