| Re: [recommenders-dev] [GSoC 2013] SnipMatch Weekly Report |
Hi,
This is my report for the last week.(08.08-14.08)
I could solve the template variable resolution problem which was a critical problem during last two weeks. Now my TemplateProcessor can resolve most of the standard jface code templates. Import variables are also clearly resolved while being inserting the import statements at the top of the java class.The other major task which i completed last week was the SnipMatch search engine. I could successfully associate Apache Lucene to our SnipMatch search engine. With this implementation the user should set two paths before execute SnipMatch, those are local snippets directory and Lucene index directory. I changed the SnipMatch preference window so that the user can set the paths to those directories. Lucene index is created based on the summery section of the Snippets.* Improving TemplateProcessor to increase the range of variables it can handle.
Plan for the next week:* Convert existing snippets to standard swt jface format so that we can test the SnipMatch well.* Improving the test coverage of the SnipMatch code base.The latest code base is available in my git repositoryp[1]. Please check the current improvements and let me know your ideas.
Thank you,
Madhuranga LakjeewaOn Fri, Aug 9, 2013 at 3:51 AM, Madhuranga Lakjeewa <lakjeewadmm@xxxxxxxxx> wrote:Hi,
Here is my report for the last week.(01.08-07.08)I was working with the TemplateProcessor which resolves the jface template variable. I could achieve considerable improvement with this. But still i have to sped some time to complete this in the next week also. I improved the search view by adding arrow key functionality to select snippets in the suggestion view. Now the users can go up and down in the suggestions list by using arrow keys and select a snippet by pressing the enter key. The search view focus did not work as intended when it was checked with Mac. I changed the previous approach of managing the focus event and now it is working fine. Since the template variable resolving problem takes time to solve i decided to start implementing snippet search mechanism in the background. I did a feasibility study on this and i think Apache Lucene best fits to our purpose.Plan for the next week:I hope to complete implementing snippet insertion mechanism. I will create the snippet search engine with Apache Lucene.
The latest code base is available in my git repositoryp[1].On Thu, Aug 1, 2013 at 2:05 AM, Madhuranga Lakjeewa <lakjeewadmm@xxxxxxxxx> wrote:
Hi,
Here is the report for the last week. (25.07-01.08)
I was implementing the snippet insertion mechanism. I created the TemplateProcessor which reads the user selected snippet and inserts that snippet in to the editor. Currently this is working fine for simple snippets like the snippets which don't have import statements. Actually that is the problem which i am searching for the solution at the moment. I searched for the resources where i can find the solution. I did several experiments and got favorable results. I studied the existing projects which have been implemented with Java template resolution.Find the way i can implementing java template variable resolution. I hope to complete the TemplateProcessor.
Plan for the next week:
The latest code base is available in my git repository[1].On Thu, Jul 18, 2013 at 9:15 AM, Madhuranga Lakjeewa <lakjeewadmm@xxxxxxxxx> wrote:Time period should be corrected as (11.07-17.07).The latest code is available in my git repository[1].Thank you,Madhuranga LakjeewaOn Thu, Jul 18, 2013 at 9:09 AM, Madhuranga Lakjeewa <lakjeewadmm@xxxxxxxxx> wrote:
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].
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.* I will find the solution to this focus problem.
Plan for the next week:
* 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].https://github.com/lakjeewa/SnipMatch
Thank you,
Madhuranga Lakjeewa
[1]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,
MadhurangaOn 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,MarcelOn 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