Re: [recommenders-dev] [GSoC 2013] SnipMatch Weekly Report

[Madhuranga Lakjeewa <lakjeewadmm@xxxxxxxxx>]

Hi,
Here is the report for the last week. (18.07-24.07)

I could complete the implementation of search result view. There was a problem of focus managing in search result view. I wanted to close the views with mouse click action on out of the search result view. During the last week I could solve this problem and now it is working fine. I stated implementing snippet insertion mechanism. I read and search for the background information which i need for template processing. I studied how the template engine is working in current version of SnipMatch.

Plan for the next week:
Implementing the Template Processor. Template processor will read the snippet templates and support to insert the snippet in to the editor. 

The latest code is available in my git repository[1].

Thank you,
Madhuranga Lakjeewa

[1] https://github.com/lakjeewa/SnipMatch

On Thu, Jul 11, 2013 at 11:36 AM, Madhuranga Lakjeewa <lakjeewadmm@xxxxxxxxx> wrote:

Hi,
Here is my weekly report for the last week. (05.07-11.07)

I was improving the snippets search result view. I still could not resolve the focus issue.
Here is what i want to implement;
- When the user types the search query the focus should be kept with the search query text box.
- When the both  query text box and search result view is present, user should be able to back and forth between the views without closing any of the view.
- When both query text box and search result view lost the focus, both views should be closed.

My intention is to find a component who is responsible for all these views and address the issue using it (Without using separate threads). All these views are Shell objects. These shell have a single parent shell. I assume this shell can control the child shells, but still i could not find a way.

Plan for the next week:

* I will find the solution to this focus problem.
* I will start implementing the snippets insertion mechanism to the editor.

I had an idea to improving the search algorithm. But i decided to keep that step to a later stage. As my mentors also suggested, if we are going to use an library like Apache Lucene, better we proceed with the simple search engine.

The latest code is available in my git repository[1].

Thank you,
Madhuranga Lakjeewa

[1] 

https://github.com/lakjeewa/SnipMatch

On Thu, Jul 4, 2013 at 10:43 AM, Madhuranga Lakjeewa <lakjeewadmm@xxxxxxxxx> wrote:

Thanks Marcel.
At the yesterday meeting, Johannes asked me to check org.eclipse.core.runtime.jobs.Job for thread implementation. I will look at this and see how i can use this for my implementation.

Regards,
Madhuranga

On Thu, Jul 4, 2013 at 10:25 AM, Marcel Bruch <marcel.bruch@xxxxxxxxxxxxxx> wrote:

Hi Madhuranga,

thanks for the update. One note regarding threads: please postpone any multi-threading work until really necessary. The excessive use of threads in the old version of snipmatch is one reason why we start this project from scratch. Please use simple (Eclipse) Jobs instead.

Thanks,

Marcel

On Jul 4, 2013, at 6:29 AM, Madhuranga Lakjeewa <lakjeewadmm@xxxxxxxxx> wrote:

* Implementing a better search algorithm for SnipMatch search engine. I still did not have created separate threads for searching process and it causes to several problems. My plan is to use several threads and make it properly work.

_______________________________________________
recommenders-dev mailing list
recommenders-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/recommenders-dev