On Monday this week Simon spent hours converting hexadecimals into RGBA values for the 140 colors supported by all modern browsers and creating a color file in Codea. He used the w3schools color map available at https://www.w3schools.com/colors/colors_groups.asp and an html color codes converter http://html-color-codes.info/
Some of the color names were quite exotic (like Chartreuse or Bisque ), and we looked those up together in the dictionary. We also took a very close look at the relation between red, green and blue values and found out that red was added every time to make colors lighter, even in shades where you would not expect any red.
Simon later made a nice design pattern in Codea using the color file:
On Tuesday, Simon was following another tutorial by Derek Banas, this time on UML Class Diagrams, and thought it would be fun to draw the diagrams in a new app he downloaded: ClickCharts. He tried to understand the relations between classes, abstraction, dependence, inheritance and constraints. The examples used illustrate design patterns in Java.
Principle of inheritance:
UML stands for Unified Modeling Language, it is a general-purpose, developmental, modeling language in the field of software engineering, that is intended to provide a standard way to visualize the design of a system. A diagram is a partial graphic representation of a system’s model. There are two types of diagrams in UML 2: static (or structural) and dynamic (or behavioral). Simon was studying class diagrams, which belong to static (structural) diagrams.
In software engineering a class diagram is a type of static structure diagram that describes the structure of a system by showing the system’s classes, their attributes, operations (or methods), and the relationships among objects.
The class diagram is the main building block of object-oriented modelling. It is used both for general conceptual modelling of the systematics of the application, and for detailed modelling translating the models into programming code. Class diagrams can also be used for data modeling. The classes in a class diagram represent both the main elements, interactions in the application, and the classes to be programmed.
Here Simon turned the Factory Pattern into actual code:
Simon has been studying Java Design Patterns with Derek Banas. Some he tries to build (videos below), some he gets stuck with, but the topic has kept him excited for days.
Simon was training to build console applications with Derek Banas’ tutorial on design patterns. At the end of the third video, Simon says yes to my question if the console app could also be displayed on a webpage. After we stopped filming he corrected himself: Java is never used for websites, he said, but the same techniques he learned today can be useful for Android apps.