Development of PrograMath

Back to Code

Throughout the short development of PrograMath, I really only used two programs: Notepad++ and Google Chrome. Click on any of the screenshots to view them larger.


Notepad++

Notepad++ is like Notepad, which comes as the default text editor on Microsoft Windows. Notepad++ is a free substitute, with colorful syntax highlighting and many features that will help with coding, and a few for debugging.


Google Chrome (and Developing Tools)

Google Chrome is a fast, simple web browser. It updates often, and always has the newest web standards built. Therefore, I used this to test and debug most of the code.


Biz.nf

To have my website online, I used the free hosting service by biz.nf, which had high reviews.


Other sources

I used many other websites to answer my programming websites, especially StackOverflow, a large Q&A site for programmers.


My Procedure/Documentation:

My development process was simple: plan widgets, write and test them, write an explanation and presentation page. Throughout these seven days in class, my schedule was something like this:

  1. Plan (widget ideas and layout)
  2. Start writing graphing calculator widget.
  3. Finish graphing calculator. Start calculator with similar code to graphing calculator.
  4. Continue calculator.
  5. Finish calculator. Start variable solver. Start presentation/explanation page.
  6. Work on variable solver. Continue presentation/explanation page.
  7. Add quiz, work on presentation/explanation page.

Note how it doesn't say "finish variable solver" or "finish presentation/explanation page". This is because I need much more time to get this website and explanation better: simpler, more concise, more aesthetically pleasing, more fun. Unfortunately, it's a little boring now.
I don't have much for documentation, but a few pictures of the old website and widgets. At the right are the earlier versions of the Graphing and Calculator widgets.
Some problems I faced when working on this project were:

  1. Finishing everything on time
  2. Learning some JavaScript language constructs:
  3. Writing code that did what I wanted to (computers aren't very smart!)
  4. Debugging code. Some errors I encountered: Fortunately, I solved all of these.