Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [soc-dev] [GSoC] Templates weekly report

Hi,

This is the weekly report for the Templates project

What the plan for last week was

  • I will continue working on this change set, and prepare the extension page from the Templates project side to be ready for merge.
    Hopefully both the change-sets will be merged this week.
  • I will start working on completion proposals for the template editor (See bug [1]) .
    For now, the list of proposals will only include the template variable keywords. i.e., if code completion is triggered in the context of a template variable like this: ${v:<ctrl-space>} the list will contain variable keywords like newName, newType, var, argType, etc.
What has been accomplished:
  • A first content assist proposals change set is on gerrit ([2]) waiting to be merged. I still need to add some tests for it to ensure it works properly.
    This change will give the following proposals, based on the scenario:
    • if triggered outside a template variable, it will give a list of java keywords as proposals
      e.g. ret<ctrl-space>  will return a list of proposals containing the return keyword



    • if triggered at the beginning of a template variable, right after the '${' escape, it will return a list of all simple template variable keywords like array, collection, array_type, etc.
      e.g. ${ar<ctrl-space>  will give a list of proposals containing argType, array, array_type, array_element.
    • if triggered inside a template variable, after the ':', in the context of a full template variable keyword (remember that a full template variable has the structure ${id:keyword(type/varRef)}) then the list of content  assist proposals will contain all the full variable template keywords as newName, newType, import, etc.
      e.g. ${id:f<ctrl-space>  will give a list of proposals containing field.

  • I also created a personal blog about the Templates editor [3], which aims to present the technical details behind the different features that we implemented using Xtext.
    The first post in the blog (the only one published as well) will give a short introduction to the Templates editor as well as some guides on how to build and run the project.
    You might find it interesting if you want to get started with the project. :-)

What the plan for next week is:

  • Add test cases for content assist proposals
  • Merge the content assist change-set
  • Prepare project documentation for the end of Google Summer of Code program.


Best Regards,
Stefan.

[1]: < https://bugs.eclipse.org/bugs/show_bug.cgi?id=424256 >

[2]: < https://git.eclipse.org/r/#/c/31112/ >

[3]: < http://stefanprisca-template-editor.blogspot.ro/ >




Back to the top