This week, we were assigned our project, and we immediately reached out to our customer. I set up a Google Hangouts call with Travis and Donald, and conducted initial research about CodeMirror, an open-source text editor API that we will utilize in our application

This week I helped define use-case scenarios for our project and researched additional software libraries. I followed tutorials for Angular.JS, which we plan to use for our web framework. I also began our project planning assignment by creating our document template and writing talking points for each subsection.

This week, I helped set up another call with Travis and Donald. We produced a formal set of functional and non-functional requirements, and discussed potential project directions. I researched FirePad, which is an open-source library that integrates Google Firebase and CodeMirror, in order to help us with our code collaboration features. Finally, I worked extensively on our project planning assignment.

This week, we looked over the architecture assignment and began planning. My role was to design the UI. I researched different tools to help facilitate this, and settled on LucidChart. This tool is provides a collaborative environment to put together wireframes and other software charts. I resembled our initial UI off of Google Docs, along with other similar applications. This UI design will help us during our coding of our project. Finally, on Friday, we had a talk with one of the creators of Firepad, a library we are using to help add collaborative features.

During a Google Hangout on 9/25, our customers This week, I looked into some of the web frameworks which we will use to help us for our demo. For example, I followed a Node.JS tutorial that taught me how to deploy an app to Google Cloud Platform (GCP). In addition, I looked at additional Firepad code and began to plan out our demo. I was challenged by the many different JS web frameworks (Angular, React, Vue, etc), and how they all fit together. However, after this week of research and initial coding, I feel ready to go for our increased pace of programming beginning on 10/1. 

This week, we kicked off an increased pace of programming and incorporated our frameworks into our application. I added various elements to our application such as functionality for saving to the cloud, a timestamp that displays when it was updated last, and key bindings such as "CMD + /" to add source code comments. These keybindings match those of Sublime Text. This week was a great week to learn about Angular and become more comfortable about how to use it in an application. 

This week, I worked more with Node.JS and Angular in order to enhance the overall structure of our application. In addition, we were having some issues with our Google Cloud Platform (GCP) deployment process, so I transitioned our service to use Firebase's built-in deployment process. This process is far simpler, as it only requires two commands to deploy from the command line. In addition, our application could only handle one file at this time, so I worked on the ability to create files and toggle between them in the editor. Finally, we registered a new domain for our project: www.cloud-code.net 

This week I dedicated a lot of time to improving the UI of our application. I added functionality for the user to collapse the side file menu, and added night/day mode toggling! I would not consider myself to be a UI expert, however, working with Bootstrap really simplified the UI design process. In addition, I added the capabilities for users to delete files. Finally, we improved our ability to serve files by connecting our GCP storage bucket with our subdomain files.cloud-code.net. Now, users can edit files and render them directly in the browser upon saving

The main task this week was to add a directory structure to our application. I had some troubles working with Firebase and figuring out how to best structure the data within our database. At the end of this week, we can only allow one level of nested directories. However, it is styled great and allows directories to expand / collapse. In addition, I added different editor tabs to allow users to toggle between most frequently edited files right at the top of the editor. 

This week, I was able to fix our broken directory structure from last week, and allow 'unlimited' nested levels of directories. I needed to recreate our file service code to where each file is stored in an array as an object containing metadata such as the file name, a field whether or not it was a directory or file, and the id of their parent directory node. In addition, I added file padding to show the levels of nesting. Next, I added a context menu to where you can right click on a file and it presents a menu to where you can delete that file or directory directly.

This week, along with getting ready for our coding assignment presentation, we were tasked with fixing general UI improvements and bug fixes. For example, I worked on fixing a scrolling issue and adding improvements to our user list. In addition, I worked on fixing our README, source code documentation, and creating our user and admin manuals for our coding assignment. 

This week, we were presented with our twist. Our customers asked for us to add image upload & editing operations. We felt confidently that this was a manageable twist. During this week, we looked for different libraries and software that could help us out. In the end, we found "ngx-image-editor", which is a library for Angular 6 image processing. We began incorporating this into our project.

This was a lighter week, as it was Thanksgiving week. On Tuesday and Wednesday, I continued incorporating the image library into our application. After taking some time off for the holiday, I continued development over the weekend. By Sunday night, our project was in good shape. 

This week, we presented our work on the twist to the customer. Overall, they were satisfied with the work we put in, and they gave us some additional points of feedback. In addition, we presented our project to the Keeping Current Seminar on Wednesday 11/28. This was a wonderful opportunity to not only practice our presentation, but communicate our project to CS faculty! In conclusion, our twist code is in great shape, and we prepared for our final presentation on Monday 12/3.