<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
On 10/11/2011 01:44 PM, Pierre Stirnweiss wrote:
<br>
<blockquote
cite="mid:CAOjaSmjAE7No+Gr2mh+LHAisdbzv+1YHaxp5LvfB8PHLsg4uCg@mail.gmail.com"
type="cite">
<div>
<blockquote>
<div>
<blockquote>
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>
Long-term I would like to make it easy to extend Calligra
Active with<br>
editing capabilities. That means our libraries and the
functionality<br>
provided by Words can be reused for other UI's like the
QML-based<br>
Active-UI, an alternate desktop-UI (think of a kids interface
or an<br>
interface specialized on other use-cases or an interface for
different<br>
form factors or one for star trek fans or whatever crazy
and/or<br>
innovative things a developer likes to do build up with our<br>
frameworks).<br>
<div>
<blockquote>
KoTextEditor hacking<br>
---------------------------<br>
I'd like a hacking session where we start extending the
functionality of<br>
KoTextEditor.<br>
</blockquote>
</div>
</blockquote>
<blockquote>
What is the goal? I mean what exactly do we like to
change/extend<br>
in what direction? I ask cause that is not clear to me if it
comes to<br>
the concrete code. Maybe it's not defined yet what will be
part of<br>
the sprint-session?<br>
</blockquote>
<div><br>
The above two points are on the agenda of the sprint in our
brainstorm session about textshape/textlayout/kotext
architecture. <br>
</div>
</div>
</blockquote>
Great to read :-)<br>
<blockquote
cite="mid:CAOjaSmjAE7No+Gr2mh+LHAisdbzv+1YHaxp5LvfB8PHLsg4uCg@mail.gmail.com"
type="cite">
<div>
<blockquote>
I btw will not attend the sprint but I can participate online
:)
<div><br>
</div>
</blockquote>
<div>Arf, it's too bad you can't be here. It would be real good
if there could be a way to have you live at least with sound
(both directions), ideally with video (at least from us to
you). <br>
</div>
</div>
</blockquote>
I've a working Skype-setup so that shouldn't be a problem. Ideally
we could record/broadcast so others could participate/inform
themselfs too but I am not sure what Software to use for that :-/<br>
<blockquote
cite="mid:CAOjaSmjAE7No+Gr2mh+LHAisdbzv+1YHaxp5LvfB8PHLsg4uCg@mail.gmail.com"
type="cite">
<div>
<div>
</div>
<blockquote>
<div>
<blockquote>
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>
Identify problems and put them into bugzilla? But yes, that
will not<br>
magically fix them. At least it would be a start and provide
more<br>
details what exactly still leaves much to be desired.
<div>
<div><br>
</div>
</div>
</blockquote>
<div>Well, there are bugs/fundamental design restrictions
(mostly related to deleted stuff) and there is the odf1.1/1.2
tiny difference in spec. <br>
</div>
</div>
</blockquote>
Ah, interesting to know. That means that the sponsored work on
getting change-tracking into Calligra brings fruits on the table
cause it identifies points of weakness. A nice example why standards
should be implemented in an open and libre community.<br>
<br>
</body>
</html>