Difference between revisions of "DPS909/OSD600 Winter 2018 Lab 2"
(→3. Blog) |
|||
| (17 intermediate revisions by 13 users not shown) | |||
| Line 83: | Line 83: | ||
| Alex Wang | | Alex Wang | ||
| https://github.com/AlexWang-16/vscode | | https://github.com/AlexWang-16/vscode | ||
| − | | | + | | https://wp.me/p9ApzU-O |
|- | |- | ||
| 6 | | 6 | ||
| Line 93: | Line 93: | ||
| Joseph Pham | | Joseph Pham | ||
| https://github.com/jpham14/vscode | | https://github.com/jpham14/vscode | ||
| − | | | + | |https://jpham14.wordpress.com/2018/02/14/lab-2-visual-studio-code/ |
|- | |- | ||
| 8 | | 8 | ||
| Yuriy Kartuzov | | Yuriy Kartuzov | ||
| https://github.com/YuriyKartuzov/vscode | | https://github.com/YuriyKartuzov/vscode | ||
| − | | | + | | https://yuriykartuzov.wordpress.com/2018/02/25/the-world-of-big-code/ |
|- | |- | ||
| 9 | | 9 | ||
| Line 176: | Line 176: | ||
|- | |- | ||
| 24 | | 24 | ||
| − | | | + | |Kelvin Cho |
| − | | | + | |https://github.com/TheKinshu/vscode |
| − | | | + | |https://klvincho.wordpress.com/2018/02/14/lab-2/ |
|- | |- | ||
| 25 | | 25 | ||
| − | | | + | |Abdul Kabia |
| − | | | + | |https://github.com/AbdulKabia/vscode |
| − | | | + | |https://akkabia.wordpress.com/2018/02/18/vscode-the-spaces/ |
|- | |- | ||
| 26 | | 26 | ||
| − | | | + | |Liam Newell |
| − | | | + | |https://github.com/hibyguy/vscode |
| − | | | + | |http://liamnewell.me/blog/editors/Lab-2-Vscode-submission/ |
|- | |- | ||
| 27 | | 27 | ||
| − | | | + | |Simon Inocencio |
| − | | | + | |https://github.com/simon-inoc/vscode |
| + | |https://haxbyte.wordpress.com/2018/02/15/my-first-experience-forking-an-open-source-project-visual-studio-code/ | ||
| | | | ||
|- | |- | ||
| 28 | | 28 | ||
| − | | | + | |Kevin Pham |
| − | | | + | |https://github.com/kqpham/vscode |
| | | | ||
|- | |- | ||
| 29 | | 29 | ||
| − | | | + | |Lucas Verbeke |
| − | | | + | |https://github.com/Micluc/vscode |
| − | | | + | |https://thelucasexcerpt.wordpress.com/2018/02/15/osd600-lab-2-lucas-verbeke |
|- | |- | ||
| 30 | | 30 | ||
| − | | | + | |Michael Kavidas |
| − | | | + | |https://github.com/mkavidas/vscode |
| | | | ||
|- | |- | ||
| 31 | | 31 | ||
| − | | | + | |Vimal Raghubir |
| − | | | + | |https://github.com/Vimal-Raghubir/vscode |
| − | | | + | |https://medium.com/@vraghubir/installing-vscode-as-a-developer-296f51bb0965 |
|- | |- | ||
| 32 | | 32 | ||
| − | | | + | |Michael Fainshtein |
| − | | | + | |https://github.com/mfainshtein2/vscode |
| − | | | + | |https://moderatelyokaydeveloper.wordpress.com/2018/03/01/lab-2/ |
|- | |- | ||
| 33 | | 33 | ||
| − | | | + | |Aleksey Glazkov |
| − | | | + | |https://github.com/alexglazkov9/vscode |
| − | | | + | |https://aglazkovblog.wordpress.com/2018/03/05/getting-started-with-vs-code-users-and-developers-points-of-view/ |
|- | |- | ||
| 34 | | 34 | ||
| − | | | + | |Justin Vuu |
| − | | | + | |https://github.com/jevuu/vscode |
| − | | | + | |https://justosd.wordpress.com/2018/04/23/osd600-lab-2-vscode/ |
|- | |- | ||
| 35 | | 35 | ||
Latest revision as of 15:10, 23 April 2018
Contents
Working on Large Open Source Projects
Working on open source projects means working with large and often complex code-bases, custom build systems and test harnesses, using new technologies and tools, and using new workflows. The more you do this, the better you'll get at it.
We'll work with a variety of large open source projects in order to practice. Today we will begin with Microsoft's open source editor, Visual Studio Code
1. Install Visual Studio Code (as a user)
VSCode is one of the most popular editors in use today. It works on all platforms, and has an excellent set of extensions for solving common development problems. It's also free and open source.
Begin by installing VSCode and set it up as a user. Take a look at the docs and find some extensions to install, and get your settings configured.
Throughout this course, it is recommended that you use VSCode for your work.
2. Install Visual Studio Code (as a dev)
If you want to contribute to VSCode (fix bugs, add features), you have to build the code from source instead of only downloading it. Follow these steps to accomplish this:
- Read the contributing instructions at https://github.com/Microsoft/vscode/wiki/How-to-Contribute
- Fork https://github.com/Microsoft/vscode on GitHub, so you have a copy
- Clone your fork locally
- Add a remote for Microsoft's repo:
git remote add upstream git@github.com:Microsoft/vscode.git - Make sure you can build, run, test, debug VSCode on your local machine
As you follow these steps, keep track of any problems you encounter, steps you follow, and things you learn. We'll use those to blog about our experience later on.
3. Related Technologies
VSCode is a desktop application written using web technologies. It uses a number of popular open source projects, including:
- TypeScript
- Electron
- node.js
- eslint
- tslint
- gulp
- mocha
- sinon
- yarn
Research each of the above, and make sure you are familiar with them. Make sure you have a general knowledge of what each one is about, where to find more information (docs), etc. We will be fixing bugs in this code starting next week, and it's important that you have a working build and general understanding of the technologies involved.
3. Blog
Write a blog post about your experience getting started with VSCode. Some things you could discuss in your post:
- Which extensions did you install? Why did you choose them? What do they do?
- Which settings did you change? Why?
- Did you have an issues trying to get VSCode built from source?
- What about running the tests?
- How about live debugging?
- What did you find out about the related technologies used by VSCode? For example: what are TypeScript and Electron?
Please add a line for your blog in the following table:
