-
Notifications
You must be signed in to change notification settings - Fork 0
Version 1.2 Changes
Timothy Chandler edited this page May 14, 2014
·
1 revision
This is a running list of notable changes in Strappy 1.2.
- Added support for complex model objects. get()/set() now support dot notation to get and set complex objects.
- "strappy.mvc.View.bindDOMEvents()" is now automatically called immediately after the the view's "onReady " method.
- Added signal send trait to component.
- All signals are now sent through the component. But controllers can still call "this.sendSignal()".
- Stores, models, views and controllers are now correctly auto loaded.
- Component now waits for all of its stores, views and contollers to finish initializing and then calls "onAfterCmpInit()" on all of it's controllers.
- "Component.setReady()" now only works once.
- Added "Component.getRadioTower()" helper function.
- Added two state helper functions "getPublicState()" and "getPrivateState()".
- Upgraded to use JSKK 1.1.
- Since JSKK 1.1 depends on RequireJS2, Strappy 1.2 also does. This means you should bootstrap your application with requirejs.
- Component dependencies auto load.
- !!EMPHASIS!! - You no longer need to create hundreds of SCRIPT tags. You only need 1 for your entire project.
- Added two new component "my" variables. "fullName" and "childSpace".
- Deprecated the need for a State Store and a State Controller per Component.
- State is now defined in the Core Component file.
- "this.getParentComponent()" has been deprecated in favor of "this.cmp()".
- Components are now flagged as ready by calling: "this.cmp().setReady()".
- Setting and Getting state is now done by simply calling "this.setState()" and "this.getState()" from any class implementing the ComponentConnector Trait (Controllers, Views).
- Component Core now has the following set of events that can be hooked into.
- onConfigured
- onAfterInit
- onBeforeStateChange
- onStateChange
- onBeforeReadyState
- onReadyState
- Strappy no longer has any concept of "config". Instead, it considers private state as config.
- Two step component initiation is no longer required. You can now pass initial state to the Component's constructor.
- The use of "Component.configure()" is deprecated.
- The use of "Component.reconfigure()" is deprecated. Use the new state management instead.