Releases: neomjs/neo
housekeeping
- component.Base: added ´async waitForDomRect()´
- dialog.Base: fixed an edge case, where drag, hide, re-show lead to a broken show() animation
Smarter theme inheritance for run-time changes
examples.grid.nestedRecordFields
Getting the Grid closer to feature parity with the Table implementation.
Online Demo Grid:
https://neomjs.com/examples/grid/nestedRecordFields/
Online Demo Table:
https://neomjs.com/examples/table/nestedRecordFields/
data.RecordFactory: re-added support for data.Model based record default values
data.RecordFactory: optionally tracking modified record fields
To activate the optional feature, you need to set trackModifiedFields: true inside your related data.Model
Example of modifying a record inside your console:
Inside your tables, you can now use:
viewConfig: {
highlightModifiedCells: true
}
Online demo:
https://neomjs.com/examples/table/nestedRecordFields/
list.Base: afterSetFocusIndex() honor the mounted state
form.field.ComboBox: when showing the picker, the list focus & selected index should be in sync
data.RecordFactory: performance boost for creating records
old version:
new version:
While it is definitely not "best practises" to create massive amounts of records inside your UI at once (you would pull ranges from a backend), a framework should handle it as fast as possible.
To get the numbers up this drastically, I needed to move the fields creation outside of the record constructor and into the class generation. The API for records is the same as before, however the internal structure how data gets stored did change.
For nested data, you can change specific leaf nodes without overriding other siblings (it will get merged):
record.set({user: {firstname: 'Tobias'}})
You can also still trigger bulk updates => multiple fields getting into the same update cycle:
record.set({user: {firstname: 'Tobias', lastname: 'Uhlig'}})
You can still use the shortcut around the set() API to change root level fields, but this can no longer work for nested fields directly. Examples:
record.country = 'Germany'; // Internal setter, will trigger a change event like before
// No longer supported!
record.annotations.selected = false; // this shortcut syntax did work in previous versions, but no longer matches the internal structure
// Instead use the API:
record.set({annotations: {selected: false}})
// In case you want a direct field access to trigger the field change event, you can also use this shortcut (outside the API):
record['annotations.selected'] = false;
Records now provide a JSON export:
To see the editing inside an example app:
https://neomjs.com/examples/table/nestedRecordFields/index.html
Smarter vdom update aggregation for colliding updates
- See: #6244
- Portal App polishing
