README.md

Circular Language Broader View

[ Draft ]

These are various draft texts that may once describe a story, ideas about how this Circular language might be used in practice.

• Exchangeability

  • The Exchangeability Principles describe things in the area of computer technology, that may traditionally be separate, that might be combined to form one thing.
  • Perhaps the most important goal of the Circular programming language, is to melt together all computer technology disciplines, providing one clear language, that can express anything, and that everybody can understand. The Exchangeability Principles might make a lot of promises about Circular.

• Expression

  • This part of the documentation may cover remaining topics about the diagram expression.

  • The idea behind expression in general is that a program’s systematics might not be described by text code, but text code as well as the diagram notation may be mere expressions of systematics, stored in some other way, for instance a binary way as interlinked objects.

  • The diagram might be fully automatically drawn out. The metrics and positioning of the shapes and lines might get automatically determined. The diagram can be edited, which may result in changes to the stored objects.

  • Text code and diagram expression can be complemented by any other form of expression. Displaying data in tabular form is another form of expression. Expressing data and commands in a graphical windows user interface is also an alternative form of expression of systematics. Furthermore, certain objects have specialized expressions. For instance a sound object may be expressed by playing its sound, but not all objects can be expressed by playing it as sound. All expressions are considered alternative expressions of systematics, just like text code and diagram code.

  • Much of this documentation folder is a mere throw-together of ideas or pieces of text, that came out of previous descriptions of new computer programming languages.

• Extensibility

  • Perhaps the most important goal of the Circular programming language, is to melt together all computer technology disciplines, providing one clear language, that can express anything, and that everybody can understand. The Extensibility Principles may make a lot of promises about Circular.
  • The extensibility principles may cover the techniques that make sure existing software is extensible and make sure, that Circular language may integrate with the rest of the world of computer technology. Circular resources might be accessible to other systems and existing resources on the internet might be accessible in Circular.

• From Spec

  • Topics that may be recognizable from the spec, but then ideas perhaps less to the point but more philosophical.

• Integration

  • Circular language might be a candidate for a different way to operate computers. This folder might contain any documentation about integration modules, that Circular has to offer in order to integrate with the rest of the world of computer technology. Circular is not meant to live on its own, but existing resources on the internet should be accessible, when working with Circular. Each integration module might facilitate two goals: accessing other systems using Circular and the ability to access Circular resources from inside other systems. As such you can access other file systems using Circular, and you can also access Circular resources as if it was a file system. That example might be called File System Integration. As such there might be systems such as Database Integration, SOAP Integration, ODBC Integration, File Types and Module System Integration. Database Integration might allow you to access Circular as if it were relational database, but might also allow you to access relational database systems using Circular. SOAP Integration might expose Circular resources through a SOAP interface, but also allow you to access other SOAP interfaces using Circular. ODBC Integration might make Circular support connecting to it through ODBC, but might also allow you to access relational database resources using ODBC inside Circular. File Types might allow you to export or expose Circular resources as different commonly used file types, but also allows you to access files of such types from within Circular. Module System Integration means, that you could for instance use ActiveX resources, Java, COM, .NET and other module systems using Circular. Also, Circular resources could be linked to as if they were for instance COM or any other module systems. Also, there might be Protocols, which might enable several internet protocols, so that you can access resources that are exposed through those protocols using Circular. Protocols such as HTTP, SMTP, POP3, FTP, etcetera. It is considered quite important, that Circular in the future might give access to all those resources as well as be accessible by other systems through all kinds of different protocols.

• Semantic Modeling

  • May be about how Circular language might be used to express or model meaning from reality, a possible link to artificial intelligence, natural language and generating and manipulating those models.

• Binarals

  • Binarals might be analogous to literals. A literal may be a text representation of an object (for instance a literal number 3 or literal string "Hi!"). A binaral on the other hand, may be compiled computer code, or an object's data in a specific binary layout.

• Debugging

  • Circular is described, but how to go through code step by step or debug it has not been covered yet. This documentation may cover how debugging is implemented inside the environment of Circular. For now it only contains loose ideas about it. Nothing like this has been developed yet.

• Fundamental Principles | Loose Ideas

  • Might contain loose ideas that might once be spread across "Exchangeability", "Extensibility" and "Achievability".

• Macro Recorder

  • Circular should have this button to press, that records all user actions, that are undertaken. Then, when you stop recording, the user actions are recorded as a command, that can be called as a command to be executed in one blow instead of performing all the actions manually. You can also edit the command code, to fine-tune the behavior of the command. This makes it easy to turn manual work into automatic commands and it also makes it easier to program new commands. Other programs have this sort of macro recording, and Circular should also have such functionality in the futures. Macro recording has not been implemented inside existing versions of Circular yet.

• Object Storage

  • Object Storage may turn lists on storage devices into a landscape of digital objects. It might be the binding force between basic data structures on storage devices and the object logic of Circular. It may be about how basic data structures are used to store objects. Not all of these principles might be original, because other systems might use them, but they were isolated here in a single place as a single group of concepts that may be used to turn storage into objects.

  • Perhaps trying to find one way to manage memory allocation, database-like storage and file systems might be a bit ambitious.

  • The documentation might not be finished. An attempt was made to sum up the required concepts trying to turn basic data structures into digital objects.