Building types in DeepaMehta 4 is creating Type Definitions. But why should you care about, as it says, defining types? Well, that term names already one of what are overall seven terms to be defined in this article helping you to express and build (pretty much) any complex software application exactly the way you see or want it. One idea behind inventing and designing this small vocabulary (7 terms) was to create a structure which enables users to shape the technology they see they need for.
When defining types users decide model their outer world into their database and for such an “application model”, DeepaMehta 4 equips you with a graphical user interface allowing you to enter and edit the databases contents without further work. Now the harder part, creating a so called “application model”, is defining a composition of types and in DeepaMehta 4 one can currently do so through drawing a diagram of nodes and edges.
Let me introduce just one general idea behind this type building toolkit before i start introducing its language: Your diagrams will be part of one or many of so called Topicmaps. Topicmaps always represent some subset of your database and if you throw them away after you finished work (in this case you might’ve been type building) everything you’ve done (created or edited) will be in your database as you would expect. The contents are still available and ready to be revealed in any new or other Topicmap later. In that sense, so called Topicmaps stored in this machine are “views” (as in: certain aspects of your database) and they should be seen as independent from the contents (like e.g. your notes, contacts, mails, type definitions, …) in your database.