neo

See: https://github.com/neomjs/neo/issues/3276

for hybrid envs, we can now use the mouse and the touch drag&drop sensors in parallel.

since the Neo.Xhr singleton lives inside the data worker, it was a bit tricky to modify default headers from within the app worker scope. a new setter simplifies this one.

See: https://github.com/neomjs/neo/issues/3269

singleton example:

In case you name a class the same way as its base class, the code will obviously break. the createClass program will now recognise it and act in a smart way:

Generating a data.Model will already add one field:

Generating a data.Store will import and use a related data.Model:

The createClass program should run fine within the workspace based scope again.

Similar to view controllers, the program now fully supports auto-generating view models as well as adding them into related views.

creating a view controller will now adjust the related view file:

1. It will import the controller file
2. it will sort the import statements
3. it will add the controller config at the right spot (sorted)

You can now create your own custom main thread addons and import them (combined with the default framework addons) into your apps.

Inside your workspace (created via npx neo-app), you need to drop your addons into src/main/addon.

Inside your neo-config.json file of your app(s), you can add them using a WS/ prefix. Example:

mainThreadAddons: ['DragDrop', 'Stylesheet', 'WS/MyAddon']

See: https://github.com/neomjs/neo/issues/3235

see:
https://github.com/neomjs/neo/issues/3200
https://github.com/neomjs/neo/issues/3201
https://github.com/neomjs/neo/issues/3202
https://github.com/neomjs/neo/issues/3203
https://github.com/neomjs/neo/issues/3204

This release covers a couple of new enhancements:

1. @ThorstenSuckow createClass PR is merged in: https://github.com/neomjs/neo/pull/3193
2. form.field.Text now supports maxLength & minLength validations (on DOM level as well as inside the isValid() method
3. form.field.Number now contains an isValid() method to honor maxValue & minValue
4. data.Model now supports maxLength & minLength validations for fields (logic inside data.RecordFactory
5. data.RecordFactory now registers record namespaces which include model ids, to ensure that record changes will get mapped to the correct data.Store instance