GSoC/2017/StatusReports/MikhailIvchenko: Difference between revisions
EgorMatirov (talk | contribs) No edit summary |
EgorMatirov (talk | contribs) |
||
| (11 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
== Go language support in KDevelop == | == Go language support in KDevelop == | ||
I'm working on | I'm working on Go language support in KDevelop. [https://www.kdevelop.org/ KDevelop] is a cross-platform IDE with awesome plugins support and possibility to implement support for various build systems and languages. [https://golang.org/ The Go language] is an cross-platform open-source compiled statically-typed language which tends to be simple and readable, and mainly targets console apps and network services. | ||
My project aims on improving overall stability of Go support, making it to cover more specific scenarios and making user experience more pleasurable. That consist of providing building (via go build), launching, formatting (via go fmt) and linting (via gometalinter) support. | |||
More information is available in my [https://docs.google.com/document/d/1jCTC5NlFfGmPvUqqrCEsB1xQEgGZVFwaYmELjZ2a-ZA/edit?usp=sharing proposal]. | |||
== Code == | |||
* [https://phabricator.kde.org/diffusion/commit/query/76GeP9V4PxZg/ Commits] | * [https://phabricator.kde.org/diffusion/commit/query/76GeP9V4PxZg/ Commits] | ||
== Work reports == | |||
* [http://ematirov.blogspot.ru/2017/06/gsoc-week-3.html Week 3 report. Why test coverage of parser matters?] | |||
* [http://ematirov.blogspot.ru/2017/06/go-support-in-kdevelop-gsoc-week-4-du.html Week 4 report. DU-Chain time!] | |||
* [http://ematirov.blogspot.ru/2017/07/gsoc-week-5.html Week 5 report.] | |||
* [http://ematirov.blogspot.ru/2017/07/gsoc-week-6-7.html Week 6-7 report. Launching!] | |||
* [http://ematirov.blogspot.ru/2017/07/gsoc-week-8.html Week 8 report. Formatting and linting.] | |||
* [http://ematirov.blogspot.ru/2017/08/gsoc-week-9-10.html Week 9-10 report. Code completion.] | |||
* [http://ematirov.blogspot.ru/2017/08/gsoc-week-11.html Week 11 report. Code completion and bug fixing.] | |||
* [http://ematirov.blogspot.ru/2017/08/gsoc-week-12.html Week 12 report. Polishing features.] | |||
== Future work == | |||
There is some work remaining related to implementing various customization options for building and linting; but all of these features are rather simple - mostly related to GUI handling and passing parameters to console tools. | |||
Because of that such improvements can be a good tasks for average Google Code-In students (or a Junior Jobs for everyone else) - they would be rather simple in implementing on one hand; but they provide ability to became familiar with working with GUI in KDE projects and overall process of submitting patch on the other hand. | |||
Latest revision as of 15:36, 23 August 2017
Go language support in KDevelop
I'm working on Go language support in KDevelop. KDevelop is a cross-platform IDE with awesome plugins support and possibility to implement support for various build systems and languages. The Go language is an cross-platform open-source compiled statically-typed language which tends to be simple and readable, and mainly targets console apps and network services.
My project aims on improving overall stability of Go support, making it to cover more specific scenarios and making user experience more pleasurable. That consist of providing building (via go build), launching, formatting (via go fmt) and linting (via gometalinter) support.
More information is available in my proposal.
Code
Work reports
- Week 3 report. Why test coverage of parser matters?
- Week 4 report. DU-Chain time!
- Week 5 report.
- Week 6-7 report. Launching!
- Week 8 report. Formatting and linting.
- Week 9-10 report. Code completion.
- Week 11 report. Code completion and bug fixing.
- Week 12 report. Polishing features.
Future work
There is some work remaining related to implementing various customization options for building and linting; but all of these features are rather simple - mostly related to GUI handling and passing parameters to console tools.
Because of that such improvements can be a good tasks for average Google Code-In students (or a Junior Jobs for everyone else) - they would be rather simple in implementing on one hand; but they provide ability to became familiar with working with GUI in KDE projects and overall process of submitting patch on the other hand.