>"Clean Code" has a good chapter about that:
Thanks for the guidance. Yes the book's concurrency chapter was very
helpful. I went through it an now i have an understanding in turning off
multi threading and what relevant components must be run with multi
threading in LT.
> Marcin will correct me if I'm wrong, but multi threading should happen in
> the LanguageTool core, not in the OpenOffice specific parts of
> At least POS tagging and rule matching (only rules on the
> sentence/paragraph level) can run in multiple threads. The solution should
> be developed in a way that makes it possible to turn off multithreading
> that encapsulates all multithreading aspects to its own class.
This is what i figured out after looking at the source code.As i am still
experimenting this approach can be improved further. But at the moment,
1. Multi threading for rule matching
package - de.danielnaber.languagetool.gui;
method - private int checkText(final JLanguageTool langTool, final String
text,final StringBuilder sb)
In here the rules are running in single thread at the moment, this has
caused a time delay in the Tool. This process of rule matching and POS
tagging can be implemented in multi threads on the sentence level (as it is
not hard to process in sentence level, i hope that there is no need to
implement this for word level). I have understood its code now and will
start on this with the reference of the book.
There are few more ares where we can speed up the current process, i hope to
check the possibility of those also and will update.
In addition to that i thought to implement another new feature with LT,
which is to add auto 'check test' when we enter some additional text into LT
panel. At the moment it doesn't auto refreshes with new text adding. Surely
it will give more user friendliness to LT with this feature :)
When i was experimenting with LT i came across several bugs which can be
fixed with some effort. I have started working on fixing one of them which i
have reported into,
BTW is it really essential to submit a patch for applying for GSoC, will our
proposal be rejected for not fulfilling this requirement?
That's all for now.
On Sat, Mar 26, 2011 at 12:52 AM, Daniel Naber <list2006@...:
> On Freitag, 25. März 2011, Shameera Rathnayaka wrote:
> > Thanks for your clear explanation. As it says i need to refer source
> > code deeply and understand the LT core well, does it need the knowledge
> > in XML to a huge extent?
> No, not much XML knowledge should be needed.
> > (coz im not an expert in XML at the moment,
> > will it be an issue to understand the process without knowing XML
> > severely??) Could you please further explain the line "developed in
> > a way that makes it possible to turn off multithreading and that
> > encapsulates all multithreading aspects to its own class."
> "Clean Code" has a good chapter about that:
> Enable your software for Intel(R) Active Management Technology to meet the
> growing manageability and security demands of your customers. Businesses
> are taking advantage of Intel(R) vPro (TM) technology - will your software
> be a part of the solution? Download the Intel(R) Manageability Checker
> today! http://p.sf.net/sfu/intel-dev2devmar
> Languagetool-devel mailing list
Department of Computer Science and Engineering
University of Moratuwa.