Suitability of Procedural Languages for Graphical Applications

Procedural Languages are suitable when programming Graphical Applications but they are not the most common languages to use to program Graphical Applications as event driven languages and object orientated languages are more suitable. Event driven languages require an event to happen which is usually a click of a button or a click of a key on a keyboard. Event driven languages usually use graphical applications as the user will probably want a visual display to show a response of the action they did. Object Orientated languages also produce objects that the user can use so you would expect them to use graphical applications for the user to use. Object Orientated languages contain data and functions which will be graphically shown to the user so Object Orientated languages are very suitable for programming Graphical Applications. So even though event-driven and object orientated programming are very suitable for producing graphical applications, procedural are not very suitable. The reasons why procedural languages are not very suitable for graphical applications, is that procedural is about procedures that happen to functions in the code, ie a calculator is mainly procedural programmed as it only requires to show numbers and text and shows the results of functions with text, not graphical images.

As you can see, the example to the left is a binary/hexadecimal converter. As it is a procedural, the code executes line after line. As you can view, there is hardly no graphics at all to this program just three labels and two text boxes. This is a perfect example of why procedural programs are not very suited to graphics and do not need alot of objects in them to function.