Evolutility

Evolutility only works with data stored in MSSQL and MySQL databases, but it greatly simplifies the process of writing code that interfaces with these two.

Evolutility was created for building very interactive applications, usually for dashboards, administration panels, application backends, data grids, and so on.

The framework is basically a collection of utilities and best practices that provide quick tools that you can add to your project and support various database operations much easier, cutting down development time and rolling out CRUD capable data components in much quicker time spans.

Under the hood, Evolutility uses XML files to define data mapping patterns and the user interface, letting developers build pluggable components for their applications, easy to configure and adapt to the managed data.

Support is included for a variety of GUI elements and editing patterns, along with the possibility to automatically generate charts out of the database's data, and support have the interface translated into various languages.

Users can also export selected data to various formats, can fine tune their search queries, update multiple records at once, and even protect their data with login credentials.

Evolutility can be quite a useful component for your data, is easy to install, and also comes very well documented.

By default, Evolutility is open sourced, but commercial licenses are available for closed source projects.

This is the original version of the Evolutility framework coded for ASP.NET. A newer version, updated for more modern technologies like JavaScript and Backbone is available as well as the Evolutility.js project.

What is new in this release:

• Evolutility 4.1 is a maintenance release focused on bug fixes and UI improvements.
• Evolutility now uses NicEdit (instead of TinyMCE) for rich text editing.
• It also provides better internationalisation (especially for Japanese language) and improved cross-browser compatibility.
• Bug fixes:
• Modes confusion after export.
• Validation message not showing correctly in old IE versions.
• Problem with integer fields validation in Japanese.
• Problems w/ DB objects names in Japanese.
• Export filename not handled properly in Japanese w/ IE.
• Support for multiple LOV's on the same child table.
• Datepicker icon not always fully shown in details list edit.
• Invalid format validation for decimal values in Italian (and some other languages).
• Boolean fields should use value 0 instead of null.
• Panel Labels not displaying correctly w/ IE.