Overview of 1456 object code

Overview of 1456 object code.

William Overington

Many years ago while researching on a broadcasting standard for telesoftware, the invention that produces a remote access computer system by means of the unidirectional cyclic broadcasting of software with no need for a return information link to the central broadcasting computer, I devised an object code which I called 1456 object code (in speech, please say "fourteen fifty-six object code") intended to be a broadcasting standard so that televisions could contain a microprocessor and receive 1456 object code and compile it into the machine code of the local microprocessor, termed "local code" and then obey it. Time went by, the internet became a prominent feature of life, Java was devised and the possibility of Java object code being broadcast to televisions arose as well as Java object code being disseminated over the world wide web. Java, elegant Java, and its object code doing far more than did 1456 object code and doing almost everything for which 1456 object code was designed. Yet 1456 had one feature not present in Java, namely that the object code was entirely representable by 7 bit ascii printing characters, with one or two such characters for each operation code.

So when I learned that one could pass text strings into Java applets as parameters from an HTML page and that one could have the Java decode the parameters as one wishes, I reasoned that 1456 could be updated so as to be an object code that one could write in 7 bit ascii printing characters and place in parameters in an HTML page in the parameters of an applet. The 1456 object code would be interpreted by a specially written Java program, termed a 1456 engine. Once the specially written Java program were available as an applet class, it would be possible for many different HTML pages to be prepared using just a text editor, each containing different 1456 object code programs within the parameters of an applet call. The prospect arose that a person who were not able to program in Java and did not have the facilities to do so could program in 1456 object code, enter the program using a text editor into an HTML file and then achieve Java quality graphics output. The concept arose of placing the 1456 engine in a separate Java class file, Engine1456.class, and using that class in a number of applets termed 1456 applet landscapes, for example, one 1456 applet landscape with two buttons, another 1456 applet landscape with a scrollbar, another with mouse events available, yet another with a combination of various of the above, and so on. All of these 1456 applet landscapes essentially the same except for the collection of components available. The 1456 object code merely needed to provide code at different labels in order to respond to events. For example, please consider a 1456 applet landscape that has two buttons upon it. The 1456 programmer needs to supply code at label 1, expressed as 1: followed by some 7 bit ascii printing characters ending in H (for Halt) as the software to run at start up; code at label 51, expressed as 51: followed by some 7 bit ascii printing characters ending in H as the software to run when the first button is clicked; and code at label 52, expressed as 52: followed by some 7 bit ascii printing characters ending in H as the software to run when the second button is clicked. The 1456 applet landscape would have 1:H 51:H and 52:H already supplied, so that the 1456 applet landscape would work straightaway, starting up with a plain background and buttons that do nothing. It would then be a matter of adding 1456 object code between the : character and the H character in each case in order to achieve a desired result. These different HTML pages could be authored by people who need have no knowledge of programming in Java. Thus, a teacher of free to the end user distance education on the internet could produce Java quality displays by programming in 1456 object code without necessarily knowing how to program in Java. Certainly, 1456 object code is not intended to replace direct Java programming. Rather it has its own domain of applicability, where quite effective results can be produced.

This would mean that 1456 object code could possibly become a type of standard, yet not an international broadcasting standard as such but a standard for people who choose to use it to produce Java quality effects without the need to know Java nor have a Java compiler available.

Yet 1456 object code could also be suitable for use by people who are able to program in Java, simply because 1456 object code can be very convenient to use, particularly where several screen components are being used. The use of 1456 object code by a Java programmer also makes the program portable to other participants in a distance education authoring group who may not be able to program in Java or may not have available the facilities to do so.

The 1456 object code is fairly easy to learn in its simpler usages, as it can be used as just a programmable calculator language if so desired. Yet 1456 object code has a subroutine calling facility and so structured programs can be produced. The 1456 object code system has built into it the eutodraw system which is the system whereby 1456 object code programs produce text and graphics on an applet display. Facilities are comprehensive and include facilities to draw lines, rectangles, ovals, arcs and polygons, together with facilities to define custom colours.

Being totally dependent upon Java for its standardization, 1456 object code can be available in most, maybe all, environments where Java applets can be used. Indeed 1456 object code could be used directly in a Java applet or application if so desired simply by placing the 1456 object code in a string or strings in the Java program and sending it directly into the 1456 engine, as the 1456 engine does not need to be included in an applet in order to work. Various scenarios arise as to why someone might wish to use 1456 object code directly within a program in this way. One use would be to seal into an applet or application the functionality of some 1456 object code which had been developed by someone who were not a Java programmer, without needing to recode the software. Another usage might be to provide a 1456 applet landscape with a subroutine built into it for direct access using 1456 object code. For example, a subroutine at label 101 which provides the zeroth order Bessel function of the first kind of whatever value is in the floating point accumulator of the 1456 engine when the 1456 sequence 101C is reached, where C is the 1456 object code command for calling a subroutine.

1456 object code