ezsh is just getting started, and we have proposal’s to make, specifications to meet, and code to write.

The Story So Far 

At the time of writing, we have just submitted our project proposal, found here in markdown and found here in Word format. In doing this, we have also:

  1. gotten a supervisor for the project, Dr Stephen Blott.
  2. set up a repository on the DCU School of Computing Gitlab.
  3. commited the above proposal forms to said repository.
  4. set up this hugo blog for our project.

So far, so good. We had no issues in writing our proposal as we are (for now) very much in agreement on the direction in which want to go with this project.

What’s Next? 

In terms of writing code, our project is still awaiting clearance for lift-off. Before we start commiting any code to the repository, our proposal first needs to be approved. This coincides with presentations, which will take place from November 12th onwards. Our presentation should describe the goals of the project, outlining how we aim to achieve these goals aswell as an outline of ezsh’s UI. After this stage, we must submit our Functional Specification. This deliverable will be covered in another post.

What Are We Using? 

Well, before we list off anything else, we are using [git]() as our VCS, with our project’s source code hosted on DCU’s Gitlab instance linked above. We are going to write ezsh in C, making good use of the ncurses library for our interface.

Outside of the actual project, we are also familiarising ourselves with hugo, a static site generator used to generate this site.

We had debated whether or not to pursue Go as a viable language to write ezsh in. It boasts some fantastic UI libraries for the terminal not all that different from ncurses. What helped us make the decision was the sheer amount of documentation ncurses has in comparison to most other alternatives. We felt it as the safer choice because of this.