Project Description
MVC Controls Toolkit is a complete set of advanced server controls for
MVC 2-4 ranging from a templated edit-on line datagrid to date-picker and custom formatted textboxes, supporting client validation and
globalization. MVC Controls Toolkit makes it easier to define new complex controls for MVC without defining custom binders to read back the input from the Controls because each
control enables the MVC engine to call its own handler to bind properly the input to the view model. Thus, there is no need to adapt the controller to a
control or to define ad hoc controllers.
Main object of the project
Enabling MVC programmers to implements rich user interfaces without renouncing to the separation of concerns between the View Model that defines just What data to display and the View that defines
How to display those data: in particular in no case the choice on how to display data in a View must force the programmer to change the View Model.
ATTENTION the current 2.2 release is compativle wit Mvc4 RC. A new version compatible with Mvc4 RTM will be releaed in a few days
|
NEW TO THE MVC CONTROLS TOOLKIT?
- See a video of the fothcoming "Data Moving" Plugin here,
- See the list of all Tutorials
here .
- Download complete examples here
- See the installation procedure
here. Avaliable also NuGet packages:
- See full documentation
here.
- See Releases History here.
- Read about the theory that is behind the Mvc Controls Toolkit
here.
|
FEEL FREE TO CONTACT US:
|
(2012-07-04) The new 2.2 release is available for download. Documentation has been updated! For a quick start on the new features please
refer to
this tutorial. Below the list of changes:
- Added
- Modified all Mvc4 related features to conform with the Mvc4 RC.
Attention: the Mvc4 version requires full thrust, due to an RC version check performed by the dll. This limit will be removed in the Mvc4 RTM version.
- Now all items controls accept any IEnumerable<T>(before just List<T> were accepted by most of controls)
- retrievalManager class that retrieves automatically data from a data source whenever it catchs events triggered by filtering, sorting, and paging controls
- move method to the updatesManager to move one child objects from a father to another. The move operation can be undone like the insert, update and delete operations
- Now an updatesManager can be decalred as child of itself, and in general circular references are allowed in the father-children graph. This way it is possible to handle any relation structure, and in particulare transitive relations like the recursive
task-subtask relation.
- Fixed
- A bug in the updatesManager that appeared whenever the user inserts at least two children of a newly inserted father
- A bug in the knockout server side error handling functions that prevented to show the original server side error string in an error label(* or other constants worked, but the original sever side string not)
- TypedTextBox "flashed" in some mobile browser when a value was provided through javascript
- Other minor bugs
Mvc Controls Toolkit Features:
- All controls and validation attributes support culture
globalization of dates and numbers, and support both server-side and client-side validation (see
Validation Settings section).
- Compatible with both Mvc 2 and Mvc 3;
- Client side ViewModell automatically synchronzed with the server ViewModel that can be bound to UI elements. See here.
- Client-Side Templates for creating rich UI at a low BandWidth price,
See here
- Support for Theming. See here.
- Complete set of server controls (no need to write any javascript) that handle both the rendering and the binding of the input to the View Model :
- Items Controls
- Collections Support Controls
- Layout Manipulation Controls
- Simple Controls
- Client Side javaScript functions
- Data Annotations and Validation Attributes with full support for client side validation and globalization
See here.
- Action Filters and View Results
See here.
- Controls code appears only in the Views not in the Controllers, thus keeping separation of concerns between View (How to display) and controller (What to display)
- When possible multi-parts controls are not rendered as a single piece, but the View designer has the freedom to display its parts separately whererever he prefers. Moreover, the View designer has the possibility to render only the parts
it needs, if this makes sense.
- Defining new controls with the same features of the pre-defined controls is straightforward, see here.