Hello :) I'm HyeSoo Park. I'm happy to know Clojure community. I'm 3rd year undergraduate student. I would like to apply GSoC 2017 Clojure project based on idea "Add cool features to KLIPSE" from (http://clojure-gsoc.org/project-ideas.html). I am familiar with GitHub workflow as I did open source project in Rails Girls Summer of Code 2016 with Hoodie desktop app project. I self-studied Clojure/Script and quite familiar with JavaScript. I really like Clojure and want to learn more Clojure.
I wrote a proposal for KLIPSE project. Could anybody check out and give me feedback? I am happy and open to listen any advice or ideas. Thank you very much. Have a happy day :) [Proposal] >>Community benefits: >From my personal experience of learning om.next from an interactive tutorial made using KLIPSE(http://read.klipse.tech/om-next-interactive-tutorial/), I know this project will hugely benefit people who tries to learn Clojure/Script or related library/frameworks. KLIPSE is a great tool for helping people to learn Clojure/Script by doing. Feature updates I promised on the synopsis will enhance the learning experience even more by providing IDE-like features. Even without installing any IDE/Text Editor/REPL, you can try interactive tutorials from everywhere with internet connection and web browser. Which will definitely benefit Clojure community to grow even larger. >>Deliverables: What quantifiable results should your project produce? By the end of summer, at least 3 features will be implemented, which by the way are in the KLIPSE backlog(https://github.com/viebel/klipse/issues). Specifically the most important goal to me is the code completion feature(https://github.com/viebel/klipse/issues/198). Then I will work on integration with github gist(https://github.com/viebel/klipse/issues/205) and implement pretty printing in KLIPSE app(https://github.com/viebel/klipse/issues/202). Then optionally, I will tackle bugs such as expressions with comment returning nil(https://github.com/viebel/klipse/issues/222). After finishing mentioned priorities, I will work on more issues if time allows, I am also eager to write an interactive tutorial for a self-host compatible cljs library in blog format like om next interactive tutorial I mentioned. >>Schedule Before May 30 (Before the official coding time): Before the actual coding period starts, I will be in touch with my mentor (Yehonathan Sharvit, https://github.com/viebel, kindly agreed to be my mentor for this project) and the Clojure community. I will communicate on Clojurian Slack and Mailling lists to gather improvement ideas and advices. I will read documentations and source code to familiarize myself with KLIPSE and related projects that I can use to achieve my goals (mostly projects whose github link mentioned below). Also as I already did with few PRs, I will improve and contribute to the documentation or source code whenever I find a way to do so. All weeks considers the time taken to write documentation and have code reviews, for example discussing on PRs, -Week 1-2: Study an example source code of Clojure code auto completion from https://github.com/jaredly/reepl, and plan how to use it in KLIPSE. -Week 3-4: Implement code auto completion using the mentioned example. Namespace ‘klipse.ui.editors.cljs’ has the UI implemented using om.next, I will inject ‘reeple’ functionality into the UI. -Week 5: Study implementation details of pretty printing from https://github.com/kkinnear/zprint. And plan how to integrate it with KLIPSE. -Week 6-7: Integrate zprint with KLIPSE, enabling pretty print. Namespace ‘klipse.ui.outputs.js’, is where the component for showing what you printed is shown. The component queries ':evaluation-js’ from the app-state. When rendering textarea in the component I can implement pretty print there. -Week 8-9: Study Github Gist API (https://developer.github.com/v3/gists/) to plan integration with KLIPSE. -Week 10-11: Integrate KLIPSE with github GIST. User will be able to save gist directly from KLIPSE with just one click. -Week 12: Write a cljs library interactive tutorial on blog using KLIPSE. The library should be self-host compatible cljs library such as core.match, clojure.spec and om.next. -Week 13: No requirement for this week to use the time to compensate any unpredictable delays in previous weeks. Although if everything went as planned or better than planned, I will use this week to fix a minor bug such as https://github.com/viebel/klipse/issues/222 about evaluating expressions with comment. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
