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

List:       koffice-devel
Subject:    Re: Grammar checking
From:       "Jacob Rideout" <jacob () jacobrideout ! net>
Date:       2007-01-02 16:33:34
Message-ID: d37f1a780701020833t5135d044y1da50a45a26af714 () mail ! gmail ! com
[Download RAW message or body]

Cool, I just wanted to understand the technical barriers. Once, I get
Sonnet a little bit more stable, I'll see what I can do to held you
guys out.

Cheers,

Jacob

On 1/2/07, Thomas Zander <zander@kde.org> wrote:
> On Friday 29 December 2006 12:36, Jacob R Rideout wrote:
> > I've been working on a grammar checking module for Sonnet in kdelibs.
> > It would be great if we could integrate this into KOffice trunk.
>
> Indeed :)
> As you may know; this is a feature that is dependent on quite some
> infrastructure already being available. Since its a feature of the
> text-layout system.
> And since we could no longer use the old one, trunk has a completely new one.
>
> > However, before that happens some discussion must occur on what the
> > GUI should be. Do we want to go the traditional route and have blue
> > squiggle underlines for grammar errors and red for spelling? I have a
> > hunch there is a better way, but I don't know what it is.
>
> There are lots of details still to be determined.
> From the top of my head:
> * we need a plugin for the text-tool so sonnet can be notified when a word is
> changed. [1]
>
> * since we have model-view separation, with the text being painted in the
> model we need to have code that paints decorations like a selection or those
> red squiggly lines in the view.  This has to be actually painted in the tool
> (which is per view) to avoid those lines to be printed.
> This is currently a big TODO.
>
> * We will need direct support for sonnet in a multi-threaded class that loops
> over the content of a document and stores the new state somehow somewhere.
>
> So, while I'd love to have this technology in trunk as soon as possible, I'm
> not sure I dare ask you to dive into all those problems right now. I mean;
> you are more then welcome to! But I have to be honest and say you'll probably
> walk away frustrated sooner than actually finish this quite big task :)
>
> What I was thinking is that you could write some code in the KoTextTool meant
> to do checking of the current paragraph as soon as the user presses enter.
> And the last word when the user presses space.  Completely ignoring slowness
> and other user interface problems.
> This means it would not be a perfect solution, but I volunteer for refactoring
> that code (i.e. moving around) to make it multithreaded and all that other
> goodness after you get the basics working.
> Hows that?
>
>
> 1) see my thoughts on plugins here;
> http://wiki.koffice.org/index.php?title=KWord
> --
> Thomas Zander
>
>
> _______________________________________________
> koffice-devel mailing list
> koffice-devel@kde.org
> https://mail.kde.org/mailman/listinfo/koffice-devel
>
>
>
>
_______________________________________________
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]