tranferred from Overleaf

.gitignore

@@ -11,7 +11,7 @@
 *.cb
 *.cb2
 .*.lb
-
+build/*
 ## Intermediate documents:
 *.dvi
 *.xdv

chapter/ch2.tex

@@ -0,0 +1 @@
+\chapter{Chapter 2}

chapter/ch3.tex

@@ -1,9 +1,9 @@
-\section{Collecting User Feedback for Syntactic Proposals}
+\chapter{Collecting User Feedback for Syntactic Proposals}
 
 The goal for this project is to utilize users familiarity with their own code to gain early and worthwhile user feedback on new
 syntactic proposals for EcmaScript. 
 
-\subsection{The core idea}
+\section{The core idea}
 
 Users of EcmaScript have a familiarity with code they themselves have written. This means they have knowledge of how their own code works and why they might have written it a certain way. This project aims to utilize this pre-exisiting knowledge to showcase new proposals for EcmaScript. Showcasing proposals this way will allow users to focus on what the proposal actually entails, instead of focusing on the examples written by the proposal author. 
 
@@ -12,7 +12,7 @@ A proposal for EcmaScript is a suggestion for a change to the language. These ch
 
 Further in this chapter, we will be discussing the \textit{old} and \textit{new} way of solving a problem. What we are referring to in this case is whatever set of problems a proposal is trying to solve, if that proposal is allowed into EcmaScript as part of the language, there will be a \textit{new} way of solving said problems. The \textit{old} way is the current status quo when the proposal is not part of EcmaScript, and the \textit{new} way is when the proposal is part of EcmaScript and we are utilizing the new features of said proposal.  
 
-\subsection{Applying a proposal}
+\section{Applying a proposal}
 
 The way this project will use the pre-existing knowledge the user harbors of their own code is to use it as a base, and \textit{apply} the proposal to that base. 
 
@@ -20,7 +20,7 @@ When a proposal is \textit{applied} to a piece of code there are some main steps
 
 Identifying a code snippet where the proposal might be utilized, the problem a proposal is solving allows us to iden
 
-\subsection{Syntactic proposal}
+\section{Syntactic proposal}
 
 A proposal for EcmaScript is a suggested change for the language, in the case of EcmaScript this comes in the form of an addition to the language, as EcmaScript does not allow for breaking changes. There are many different kinds of proposals, one such example is a Syntactic proposal
 
@@ -47,7 +47,7 @@ let c = 200;
 See that in \ref{ex:proposal} the change is optional, and is not applied to the declaration of \textit{c}, but it is applied to the declaration of \textit{x}. Since the change is optional to use, and essentially is just \textit{syntax sugar}, this proposal does not make any changes to functionality or semantics, and can therefore be categorized as a syntactic proposal. 
 
 
-\subsection{Showcasing syntactic proposals}
+\section{Showcasing syntactic proposals}
 
 The application of a proposal on a program will then be utilized as a way of presenting the proposal to developers using EcmaScript(hereby referred to as users). If the code used for the application is already familiar to the user, we can severely limit the amount of time spent to understand the functionality of the initial code used in the application of the proposal. This allows the users more focus on the actual change presented by the proposal, which in turn might present itself in better feedback on the proposal, as well as presenting issues about the proposal earlier in the process. 
 
@@ -57,9 +57,9 @@ This showcase is done by, The user being presented with two pieces of code. One
 This paper does not focus on showcasing and gathering user feedback, however focusing more on the process of applying a proposal to some piece of code, while maintaining its functionality. 
 
 
-\subsection{\DSL}
+\section{\DSL}
 
 In order to match ......
 
 
-\subsection{Using the \DSL with an actual syntactic proposal}
+\section{Using the \DSL with an actual syntactic proposal}

chapter/ch4.tex

@@ -0,0 +1 @@
+\chapter{ch 4 goes here}

chapter/ch5.tex

@@ -0,0 +1 @@
+\chapter{CH 5 goes here}

chapter/introduction.tex

@@ -1,64 +1,9 @@
 \chapter{Introduction}
 
-Natum mucius vim id. Tota detracto ei sed, id sumo sapientem sed. Vim in nostro latine gloriatur, cetero vocent vim id. Erat sanctus eam te, nec assueverit necessitatibus ex, id delectus fabellas has.
-
-Lorem ipsum dolor sit amet, iisque feugait quo eu, sed vocent commodo aliquid an. Minim suavitate dissentiet te eos. Dicunt eirmod adolescens no sed. Esse nonumy melius an mel, mei ut maiorum luptatum. Eu eum iudico scripta, movet option assueverit mel ex, mea at odio noluisse efficiendi. Ad vidisse atomorum conceptam quo, saepe volumus philosophia eos eu, delenit conceptam no usu.
-
-Vituperata sadipscing deterruisset ei mel, at qui nonumy blandit. Delectus dissentiet et sea, ut rebum regione numquam nam, cum ex augue constituto. Te per nihil semper. Posse voluptatum qui an, aliquando democritum disputando id quo, everti perpetua cu vim. Laudem fabellas mei an, eu reprimique quaerendum usu. Quidam prompta fabellas ne est.
+Intro goes here
 
 \section{Background}
 
-Lorem ipsum dolor sit amet, cu graecis propriae sea. Eam feugiat docendi an, ei scripta blandit pri. Nonumes delicata reprimique nam ut. Eu suas alterum concludaturque est, ferri mucius sensibus id sed~\cite{raftAlg}.
-
-We can do glossary for acronymes and abriviations also: \gls{saas}. As you see the first time it is used, the full version is used, but the second time we use \gls{saas} the short form is used. It is also a link to the lookup.
-
-
-\subsection{Listings}
-You can do listings, like in Listing~\ref{ListingReference}
-\begin{lstlisting}[caption={[Short caption]Look at this cool listing. Find the rest in Appendix~\ref{Listing}},label=ListingReference]
-$ java -jar myAwesomeCode.jar
-\end{lstlisting}
-
-You can also do language highlighting for instance with Golang:
-And in line~\ref{LineThatDoesSomething} of Listing~\ref{ListingGolang} you can see that we can ref to lines in listings.
-
-\begin{lstlisting}[caption={Hello world in Golang},label=ListingGolang,escapechar=|]
-package main
-
-import "fmt"
-
-func main() {
-    fmt.Println("hello world") |\label{LineThatDoesSomething}|
-}
-
-\end{lstlisting}
 
 \subsection{Figures}
 
-Example of a centred figure
-\begin{figure}[H]
-    \centering
-    \includegraphics[scale=0.5]{figures/Flowchart}
-    \caption{Caption for flowchart}
-  	\medskip 
-	\hspace*{15pt}\hbox{\scriptsize Credit: Acme company makes everything \url{https://acme.com/}}
-    \label{FlowchartFigure}
-\end{figure}
-
-\subsection{Tables}
-
-We can also do tables. Protip: use \url{https://www.tablesgenerator.com/} for generating tables.
-\begin{table}[H]
-\centering
-\caption{Caption of table}
-\label{TableLabel}
-\begin{tabular}{|l|l|l|}
-\hline
-Title1 & Title2 & Title3 \\ \hline
-data1  & data2  & data3  \\ \hline
-\end{tabular}
-\end{table}
-
-\subsection{\gls{git}}
-
-\gls{git} is fun, use it!

generators/imports.sty

@@ -28,7 +28,7 @@
 \usepackage{amsmath}
 \usepackage{titlesec}
 \usepackage{setspace}
-\onehalfspacing
+\singlespacing
 \usepackage{fullpage}
 \graphicspath{{figures/}}
 

report.tex

@@ -15,8 +15,8 @@
 \setlength{\parskip}{0.5cm plus4mm minus3mm}  
 
 \include{chapter/introduction}
-
-\include{chapter/ch3/ch3}
+\include{chapter/ch2}
+\include{chapter/ch3}
 % Include more chapters as required.
 %%=========================================