Page History
...
| View file | ||||
|---|---|---|---|---|
|
New features
| Name | Description | Estimate |
|---|---|---|
| Rest integration | Develop an alternative to JCR for browsing and form viewing/editing. See the synergy with the REST client (or use some other approach). Goal - to have easily configurable REST browser and REST-based forms | 2 weeks |
| Cross-field validation support | The field hierarchy is now kept in the form binders, so technically it is available while form is active and could be injectable in the validators and/or fields themselves. Need to see how to better expose such hierarchy and how to address at least some of the issues related to the topic. | 2 weeks |
| Forms with alternative layout | Ship 1-2 alternative ways to layout forms (the API's are in place, even some implementation has started) | 3-5 days |
| Validation within composite fields | Re-use 'validation bubble' effort from the past, try to provide universal validation/description UI regardless of the layout | 1 week (though be trickier) |
| [optional] Master-detail sub-app | Test the flexibility of the new UI framework views and combine browser and detail in one sub-app (should be as easy as binding the pre-created form to the current selection in e.g. tree view) | 3-5 days |
Essential features
| Name | Description | Estimate | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Chooser dialog |
| 1-2 weeks | ||||||||
| Multi-value field UI |
| 1 week | ||||||||
| Migrate more fields |
| 3 weeks (can be parallelised tho) | ||||||||
| Harden JCR browsing implementation | (remaining DS configuration, full-text search support etc) | 1-2 weeks | ||||||||
| Multi-selection support in browser | ValueContext needs generalisation (to conveniently cover the single vs multi selection cases) | 3-5 days | ||||||||
| Harden DS observation mechanism | ContentChangeEvent replacement needs to be hardened: should be memory-leak safe, should be clear, corner-cases should be considered. Observation should also work for the case of the detail sub-app | 1-2 weeks | ||||||||
| Re-instate previews in actionbar | Re-add the feature (should be simple with ValueContext). Question the abstraction of ImageProvider. | 3-5 days | ||||||||
| Shortcuts in the grids and forms | Currently not ported over from the old implementation. Need to see also how to do it better. | 3-5 days | ||||||||
| Port form-dialog | Thanks to the view-contexts and view improvements it is probably possible to make a form dialog implementation that shares most of the code with the detail sub-app, still requires quite some work. | 1-2 weeks |
Migration strategy
| Name | Description | Estimate |
|---|---|---|
| App descriptor migration | Think of a strategy (special sub-app that takes an old descriptor and translates to the new or some hybrid descriptor). Consider migrating whatever is easily migrated (fields, columns etc). | 2-3 weeks |
| Legacy action support | It seems to be fairly sufficient to expose the selection context a set of JcrNodeAdapter to make some UI actions work. See how many we can cover by this and what is needed to cover more. | 1-2 weeks |
Overview
Content Tools