From Optflux
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 35: | Line 35: | ||
AIBench is a lightweight, non-intrusive, MVC-based Java application framework that eases the connection, execution and integration of operations with well-defined input/output. This basic idea provides a powerful programming model to fast develop applications given that: | AIBench is a lightweight, non-intrusive, MVC-based Java application framework that eases the connection, execution and integration of operations with well-defined input/output. This basic idea provides a powerful programming model to fast develop applications given that: | ||
| − | + | ||
| + | |||
*The logic can be decoupled from the user interface. | *The logic can be decoupled from the user interface. | ||
*The interconnection of operations can also be decoupled based in the idea of "experiments". | *The interconnection of operations can also be decoupled based in the idea of "experiments". | ||
| Line 43: | Line 44: | ||
The AIBench platform was conceived to facilitate the development of a wide range of applications based on generic input-process-output cycles where the framework acts as the glue between each task. The framework manages three key concepts that are constant in every AIBench application: operations, data-types and views that realize the MVC design pattern. The developer only needs to focus on how to separate and structure the problem specific code into objects of these three entities. The framework will carry out the rest of the work to generate a completely executable final application, including: | The AIBench platform was conceived to facilitate the development of a wide range of applications based on generic input-process-output cycles where the framework acts as the glue between each task. The framework manages three key concepts that are constant in every AIBench application: operations, data-types and views that realize the MVC design pattern. The developer only needs to focus on how to separate and structure the problem specific code into objects of these three entities. The framework will carry out the rest of the work to generate a completely executable final application, including: | ||
| + | |||
*Automatic generation of a GUI, where the user is allowed to select and execute the implemented functionality; | *Automatic generation of a GUI, where the user is allowed to select and execute the implemented functionality; | ||
| Line 109: | Line 111: | ||
**PERSONAL PLUGINS: Here you put your operations, classes of your data-types and custom views. This is the level where the OptFlux plug-ins are developed. In fact, the entire OptFlux workbench is nothing more than a very powerful set of AIBench plug-ins. | **PERSONAL PLUGINS: Here you put your operations, classes of your data-types and custom views. This is the level where the OptFlux plug-ins are developed. In fact, the entire OptFlux workbench is nothing more than a very powerful set of AIBench plug-ins. | ||
| − | [[Image:aibench_plug.png]] | + | [[Image:aibench_plug.png]] |
In summary, the Operations programmer builds this type of artefacts: | In summary, the Operations programmer builds this type of artefacts: | ||