MVVM (Model-View-ViewModel) is a deviation from the classical MVC paradigm, developed by Microsoft, targeted at UI development, and used for Silverlight and WPF (Windows Presentation Foundation).
Vue.js implements some of the basic MVVM principles for JavaScript, improving and cutting down development time for UI-related tasks.
This is done thanks to Vue.js' special attention to building a very easy to use composable component system. This allows developers to build custom components with a few lines of code, and coupled with a easy to use data bindings allows programmers to create UI widgets that respond and react to various inputs.
All in all, Vue.js is a very versatile system that allows developers more control over their UI, while letting them build custom controls and components as well.
What is new in this release:
- New:
- Strict mode
- Improvements:
- Source code refactored for better minification when using module bundlers. See instructions.
- Computed properties now have their values automatically cached, and is re-evaluated lazily only when needed. This avoids expensive computations being re-run multiple times when a dependency changes.
- v-attr now also sets the corresponding property on the element if the property exists. For example, will not only update the attribute, but also set the value property. If the element doesn't have a corresponding property for the bound attribute, it will not be set.
- v-repeat now supports item in array syntax
- props declarations can now specify twoWay: true, which will throw a warning if the prop's binding type doesn't match.
- When providing default value for a prop, you can now provide a function that returns Object/Array values to avoid having the same reference shared across multiple vms.
What is new in version 1.0.10:
- New:
- Strict mode
- Improvements:
- Source code refactored for better minification when using module bundlers. See instructions.
- Computed properties now have their values automatically cached, and is re-evaluated lazily only when needed. This avoids expensive computations being re-run multiple times when a dependency changes.
- v-attr now also sets the corresponding property on the element if the property exists. For example, will not only update the attribute, but also set the value property. If the element doesn't have a corresponding property for the bound attribute, it will not be set.
- v-repeat now supports item in array syntax
- props declarations can now specify twoWay: true, which will throw a warning if the prop's binding type doesn't match.
- When providing default value for a prop, you can now provide a function that returns Object/Array values to avoid having the same reference shared across multiple vms.
What is new in version 0.12.7:
- Introduced a new, more robust directive parser.
- Made sure directives are compiled in the order they appear in the markup.
What is new in version 0.11.5:
- Introduced a new, more robust directive parser.
- Made sure directives are compiled in the order they appear in the markup.
What is new in version 0.9.3:
- New:
- v-with can now be used to bind a parent VM's data property to the child VM with a different key, e.g. v-with="childKey: parentKey".
- Added parent instantiation option. This allows developer to programmatically create nested VM instances.
- Added new VM instance property: $options. This can be used to access custom properties in instantiation options.
- Changed:
- When creating custom directives, the developer now need to explicitly pass in isLiteral: true, isEmpty: true or isFn:true to create literal, empty or function directives.
- Fixed:
- replace: true option causing compiler.el and vm.$el to be pointing to the old, replaced element.
- array.splice(0) now properly empties the array in supported browsers.
Requirements:
- JavaScript enabled on client side
Comments not found