Work Package #52154
Neos UI stability and extensibility
| Status: | Accepted | Start date: | 2013-09-20 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | Rens Admiraal | % Done: | 100% |
|
| Category: | - | Spent time: | - | |
| Target version: | - |
Description
Neos UI stability and extensibility¶
- Target Audience: users of Neos and developers using Neos
- Responsible: Rens Admiraal
- Implemented by: Rens Admiraal, Henjo Hoeksma
- Amount: 10 work days
- Version: could have for 1.0
- Planned Implementation Timeframe: September till December
Motivation¶
Neos should be more extensible in the long run, like for example add the possibility to load extra javascript components.
Goal¶
Add a first conditional loading based on simple feature switches so we, as Neos team, can define that certain features are not fully stable yet, but can be enabled by setting a feature switch. Besides that it will make it possible to load other assets, but this will not be public API on first release as it's not defined well enough how this should work. But at least it should enable us to start building features like for example localization in 3rd party packages which can be merged into master later on.
Deliverables¶
- A configurable loading process enabling the loading of sources from 3rd party packages
- Add feature switches
- Fix stability issues found along the way
History
#1 Updated by Rens Admiraal over 1 year ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
#2 Updated by Rens Admiraal over 1 year ago
- Status changed from Resolved to Accepted
In this workpackage a lot of stabilization issues have been worked on as preparation of the release together with the first steps to replace Ext.Direct and documentation. Most importantly the requirejs inclusion has been opened up so it's now possible to register 3rd party components like editors and validators into Neos