Build Web sites differently. Mocha presents an object-oriented view of Web site development designed to appeal to hardcore programmers and traditional Web designers alike.

Support my projects by donating bitcoin and letting me know what features are most important to you by opening issues! Please send donations for Mocha to 1MBS9KApgZnYmMhwmK7D7CZwHVhwa9uiQN.

This is the ASP.NET implementation of Mocha, containing the ZeQuaL query language interpreter and compiler, and XquizIT XML compiler to MochaBinary.

Like SQL, Zq allows to write platform-independent (for real, this time) code to access data via the Object Management Server. The syntax is based on S-expressions so it can be easily parsed and extended, while also being easily human-readable.

The main difference between the ASP.NET version and the PHP version (aside from language) is that the ASP.NET version splits the logic between the Web application component (Mocha.Web) and the Object Management Server component (Mocha.OMS). This way we can drop in different OMS implementations depending on our usage needs without having to heavily modify the front-end application. (You could even use it in a desktop application, if you're into that sort of thing.)

Mocha is built on the principle that "everything is an instance". Instances have Attributes, which are themselves Instances (of the Attribute class), and they are connected between each other via Relationships, which are also Instances (of the Relationship class). And, of course, said "classes" are instances of the Class class; the only thing making them "classes" is the presence of the "has sub Class" relationship.

The first time a Mocha instance is accessed, it pulls its data from the database and caches it in memory. Further calls to the same object are based off the in-memory representation. Changes to the object are banged immediately into the database.

• All "Properties" (Properties, InstanceProperties, and PropertyValues XQJS sections) have been removed in favor of Attributes and Relationships. EVERYTHING IS AN INSTANCE!

• Finish migrating all logic from the PHP implementation into the .NET implementation. Currently we can log in and run (built-in) reports, but the communication between the Object Management Server (OMS) and the Web application still presents issues.

• Page Components should be generated through Page Component.has Build Element Method, rather than relying on hardcoded implementations in multiple locations (PagePage, ExecuteInstancePage, and others actually hard-code multiple DIFFERENT and INCOMPATIBLE implementations of Page Components!)

• There should be no real distinction, as there has in the past, between "Objects" and "Instances" (of Objects). EVERYTHING IS AN INSTANCE!