[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    Re: State of scripts
From:       Pierre Stirnweiss <pstirnweiss () googlemail ! com>
Date:       2009-04-10 18:53:09
Message-ID: af76e3dc0904101153p663c966bk5e9cebb7eab2e4b7 () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


>
>
> Ideally we would have a design that we put up, write some examples in and
> then
> get feedback via blogs, code reviews and get external script-writers in to
> see
> what they think about the API we created.
> Much like Qt likes KDE developers because they are *users* of that API and
> give good critical feedback :)
>
> I apologize for the late point in time, just before the 2.0 final; but the
> scripting kind of fell off the radar for KWord.
> I do detect that the scripting API is unfinished with obvious gaps in the
> API
> and some odd leftovers showing what KWord looked like internally 3 years
> ago.
>
> I hope we can find some people to design a great API for KWord and text for
> the
> 2.1 release. But it will take more research than code, thats for sure.



Well, this is surely something we can speak about at the meeting. This is
along the lines of "sanitising the editing commands", which is a
pre-requisite for collaborative framework anyway. We already spoke about the
need of an interface (some sort of proxy) with the QTextDocument which would
get the "editing request" and deal with the undo/redo.

This is something I am willing to participate to.

Pierre


>
> _______________________________________________
> koffice-devel mailing list
> koffice-devel@kde.org
> https://mail.kde.org/mailman/listinfo/koffice-devel
>

[Attachment #5 (text/html)]

<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex;"><br> Ideally we would have a \
design that we put up, write some examples in and then<br> get feedback via blogs, \
code reviews and get external script-writers in to see<br> what they think about the \
API we created.<br> Much like Qt likes KDE developers because they are *users* of \
that API and<br> give good critical feedback :)<br>
<br>
I apologize for the late point in time, just before the 2.0 final; but the<br>
scripting kind of fell off the radar for KWord.<br>
I do detect that the scripting API is unfinished with obvious gaps in the API<br>
and some odd leftovers showing what KWord looked like internally 3 years ago.<br>
<br>
I hope we can find some people to design a great API for KWord and text for the<br>
2.1 release. But it will take more research than code, thats for \
sure.</blockquote><div><br></div><div><br></div><div>Well, this is surely something \
we can speak about at the meeting. This is along the lines of &quot;sanitising the \
editing commands&quot;, which is a pre-requisite for collaborative framework anyway. \
We already spoke about the need of an interface (some sort of proxy) with the \
QTextDocument which would get the &quot;editing request&quot; and deal with the \
undo/redo.</div> <div><br></div><div>This is something I am willing to participate \
to.</div><div><br></div><div>Pierre</div><div> </div><blockquote class="gmail_quote" \
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> <br>
<div><div></div><div class="h5">_______________________________________________<br>
koffice-devel mailing list<br>
<a href="mailto:koffice-devel@kde.org">koffice-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/koffice-devel" \
target="_blank">https://mail.kde.org/mailman/listinfo/koffice-devel</a><br> \
</div></div></blockquote></div><br>



_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel


[prev in list] [next in list] [prev in thread] [next in thread]