 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
General Overview | |
Liquid is all about handling data dependencies for you and letting you concentrate on WHAT happens when data changes instead of loosing time reflecting those changes everywhere that data affects your other code.
Notify, signal, synchronise
Liquid is the swiss knife of intra and inter process communications allowing you to use it MANY different ways. Use it to connect two parts of data which must stay in sync (like a ui label and some data in an object), use it to create a signaling engine, where changing data alerts other parts of your code.
Adding connect and tcp messages to a liquid's routines, you can easily cause data to reflect on a server or database whenever it changes.
Validation
Validation is an integral part of the system, supporting two levels of validation. The first level is mostly concerned with system wide data integrity, and the second, is meant for tweaking data destination compatibility, and is handled by each user of a data element.
Totally dynamic:
Liquid is dynamic in EVERY aspect. Add or remove liquids to an object, connect or deconnect to new or old data flow pipes at will, if you want, you can even change validation routines on the fly.
Even better, you don't have to even care if any other part of your software is using a value, cause, every user of data must handle its own view of the data.
Economies of scale:
Liquid rapidly pays off for a project where the usage of data is not completely quantifiable when it is created. an example is a property page of a ui. You never know when creating an object, when the user will decide to open a property page for it... with Liquid you don't care, cause the property page will update itself automatically and vice versa, if you connect things correctly.
The larger the application is eventually going to be, the better off you are using liquid at the project's onset.
Adding components to a liquified application, does not neccessarily mean increased maintenance. Each component stays shielded from the others, by the mere useage of liquid. That's liquid's main responsability... to manage relationships between data, so you don't have to.
Possibly a simple neural network core...
Liquid could be a usefull basis to implement run-time learning and reflective A.I. abilities. Because you can add, extend and connect any liquid object at run-time, this means that you can add new reactions to existing data stimuly. You can also add derived or compound knowledge which is validated by analysis of context, connections, past experiences and more.
last updated: 8-Jul-2004/1:13:59-4:00
