...
View file |
---|
name | UI improvements.xmind |
---|
height | 250 |
---|
|
Rough effort estimation
About 300 story points
Below can be found a table with description and coarse estimates of the possible further steps (time-wise* and priority-wise**).
...
Advanced Tables - Table Plus |
---|
columnTypes | ,,F |
---|
enableHeadingAttributes | false |
---|
enableSorting | false |
---|
autoTotal | true |
---|
enableHighlighting | false |
---|
|
New features Name | Description: | Estimate SP | Depended upon by Resurface? | Delivery |
---|
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 Jira |
---|
server | Magnolia - Issue tracker |
---|
serverId | 500b06a6-e204-3125-b989-2d75b973d05f |
---|
key | MGNLUI-4439 |
---|
|
13 | No | Validate foundation, APIs before next major. Ship with new major of REST Client any time. | Cross-field | validation interaction 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. User benefit: - See only relevant values in form fields. Make fewer mistakes and fill the form faster.
- Populate and validate the options in one field based on what the user chooses in another field.
Timebox to 13 SP, possible followed by smaller efforts. Jira |
---|
server | Magnolia - Issue tracker |
---|
serverId | 500b06a6-e204-3125-b989-2d75b973d05f |
---|
key | DEV-920 |
---|
|
Enables: Jira |
---|
server | Magnolia - Issue tracker |
---|
serverId | 500b06a6-e204-3125-b989-2d75b973d05f |
---|
key | MGNLUI-2542 |
---|
|
| 13 | No | Before 6.0 because new APIs are introduced. | 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 User benefit: - View and manipulate data from REST sources directly in a Magnolia app. Save time and effort.
- Easily configure apps that operate on REST sources. Avoid 4-6 weeks of Java development.
- Faster integrations. See Light Integration Stories
Jira |
---|
server | Magnolia - Issue tracker |
---|
serverId | 500b06a6-e204-3125-b989-2d75b973d05f |
---|
key | MGNLUI-4439 |
---|
|
| 13 | No | Validate foundation, APIs before next major. Ship with new major of REST Client any time. | Forms with alternative layout | Ship 1-2 alternative ways to layout forms | (the API's . The APIs are in place, even some implementation has started | ). User benefit: - Usability: Set address fields visually apart from other fields. Related controls are easier to identify.
- Make it easier for people to focus on smaller and more manageable groups.
- Reduce visual clutter and only show relevant information.
- Progressive disclosure: Defers advanced or rarely used features to a secondary screen, making applications easier to learn and less error-prone.
Jira |
---|
server | Magnolia - Issue tracker |
---|
serverId | 500b06a6-e204-3125-b989-2d75b973d05f |
---|
key | DEV-983 |
---|
|
| 8 | Maybe | DEV-983 Before 6.0 | Validation within composite fields | Re-use 'validation bubble' effort from the past, try to provide universal validation/description UI regardless of the layout. User benefit: - Pinpoint which sub-field in a more complex field has invalid entry, so the user knows what to fix.
Jira |
---|
server | Magnolia - Issue tracker |
---|
serverId | 500b06a6-e204-3125-b989-2d75b973d05f |
---|
key | DEV-992 |
---|
|
| 8 | Yes, consider | Ideally in 6.0 | [optional] Master-detail | sub-appsubapp | Test the flexibility of the new UI framework views and combine browser and detail in one | sub-app subapp (should be as easy as binding the pre-created form to the current selection in e.g. tree view) User benefit: - Select an item in an app and edit it immediately.
- Make small edits quickly without having to jump from one subapp to another.
- For example, scheduling many events. Several small edits.
Jira |
---|
server | Magnolia - Issue tracker |
---|
serverId | 500b06a6-e204-3125-b989-2d75b973d05f |
---|
key | DEV-991 |
---|
|
| 3-5 days5 | No | after 6.0, independently | [optional] Filterable columns in Grids | The PoC solution contains column renderer which allows to filter tree grid by path. Consider productising such feature and see how would it be possible to incorporate it into configuration and implementation of the content views. User benefit: Search content by title, creation date, author, duration, rank, or any combination of properties. - (Find Bar does a full-text search and serves a different use case.)
- Find items faster.
Configure searchable properties for an app so that they are relevant for users.
Jira |
---|
server | Magnolia - Issue tracker |
---|
serverId | 500b06a6-e204-3125-b989-2d75b973d05f |
---|
key | DEV-993 |
---|
|
| 1-2 weeks | 8 | No | after 6.0, independently |
Essential features Name | Description | Estimate SP | Depended upon by Resurface? | Delivery |
---|
Multi-value field UI Chooser dialog | Jira |
---|
server | Magnolia - Issue tracker |
---|
serverId | 500b06a6-e204-3125-b989-2d75b973d05f |
---|
key | DEV-974 |
---|
|
| 1-2 weeks | Multi-value field UI | 8 | No | 6.0 | Multi-selection support in browser | ValueContext needs generalisation (to conveniently cover the single vs multi selection cases) Jira |
---|
server | Magnolia - Issue tracker |
---|
serverId | 500b06a6-e204-3125-b989-2d75b973d05f |
---|
key | DEV-999 |
---|
|
| 8 | No | 6.0 | 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 Jira |
---|
server | Magnolia - Issue tracker |
---|
serverId | 500b06a6-e204-3125-b989-2d75b973d05f |
---|
key | DEV- |
---|
|
| 9761 week | | 13 | No | ideally 6.0 | Chooser dialog | Migrate more fields | Jira |
---|
server | Magnolia - Issue tracker |
---|
serverId | 500b06a6-e204-3125-b989-2d75b973d05f |
---|
key | DEV-974 |
---|
|
| 13 | No | 6.0 | Migrate more fields | 9783 weeks (can be parallelised tho) | Port more column renderers | Jira |
---|
server | Magnolia - Issue tracker |
---|
serverId | 500b06a6-e204-3125-b989-2d75b973d05f |
---|
key | DEV-977978 |
---|
|
| 21 | No | 6.01-2 weeks (can be parallelised) | Harden JCR browsing implementation | (remaining DS Remaining JCR data source configuration, full-text search support | etc)f1-2 weeks | Multi-selection support in browser | ValueContext needs generalisation (to conveniently cover the single vs multi selection cases) | 3-5 days | in lists etc. Jira |
---|
server | Magnolia - Issue tracker |
---|
serverId | 500b06a6-e204-3125-b989-2d75b973d05f |
---|
key | DEV-1000 |
---|
|
| 13 | No | 6.0 | 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. Jira |
---|
server | Magnolia - Issue tracker |
---|
serverId | 500b06a6-e204-3125-b989-2d75b973d05f |
---|
key | DEV-1006 |
---|
|
| 8 | No | ideally in 6.0 but could be later | Port more column renderers | Jira |
---|
server | Magnolia - Issue tracker |
---|
serverId | 500b06a6-e204-3125-b989-2d75b973d05f |
---|
key | DEV-977 |
---|
|
| 8 | No | 6.0, grid doesn't know about the old renderers. Compatibility wrapper is an alternative. | 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 | Jira |
---|
server | Magnolia - Issue tracker |
---|
serverId | 500b06a6-e204-3125-b989-2d75b973d05f |
---|
key | DEV-1002 |
---|
|
| 5 | No | can be after 6.0 but some work must be done before 6.0 | Keyboard shortcuts 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. | Jira |
---|
server | Magnolia - Issue tracker |
---|
serverId | 500b06a6-e204-3125-b989-2d75b973d05f |
---|
key | DEV-1005 |
---|
|
| 8 | No | 6.0, otherwise keyboard shortcuts won't work. Can be timeboxed to 5 SP.1-2 weeks | Implement Vaadin 8 - based inline row editing | Grid/TreeGrid has in-built editor API, which can play together with parts of the from framework improvements that we introduced (binders/propertysets etc). Add support for inline editing in Grid/TreeGrid 1-2 weeks Jira |
---|
server | Magnolia - Issue tracker |
---|
serverId | 500b06a6-e204-3125-b989-2d75b973d05f |
---|
key | DEV-1003 |
---|
|
| 8 | No | 6.0, basic inline editing capability is required. Enhancements can come later. | Migration strategyName | Description | Estimate | Resurface | Delivery |
---|
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). Jira |
---|
server | Magnolia - Issue tracker |
---|
serverId | 500b06a6-e204-3125-b989-2d75b973d05f |
---|
key | DEV-989 |
---|
|
| 8 | No | 6.02-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. Jira |
---|
server | Magnolia - Issue tracker |
---|
serverId | 500b06a6-e204-3125-b989-2d75b973d05f |
---|
key | DEV-990 |
---|
|
| 1-2 weeks |
Configuration8 | No | ideally 6.0 | Migrate bundled content apps to new APIs | With 6.0 we would want to ship our own apps that are already based on the new API's. Ideally we'd just migrate the configuration and deprecate the current ones. Jira |
---|
server | Magnolia - Issue tracker |
---|
serverId | 500b06a6-e204-3125-b989-2d75b973d05f |
---|
key | DEV-1010 |
---|
|
| 21 | No | ideally 6.0 |
Configuration simplificationsUsers expect simpler configuration with the new UI framework. Consider using the improvements we get from content types effort and type references. We use type references for fields today but the mechanism can be used also elsewhere. Name | Description | Estimate | Resurface | Delivery |
---|
Name | Description | Estimate |
---|
Content type powered config | Requires content type solution to be available. Would be nice to shave some config parts off the detail sub-app and form dialogs. | 1 week (once content types are in) |
---|
Apply the type references where possible | New UI improvements do not make the descriptors any leaner as is (in order to not make the configuration less powerful). With type references for whatever possible we could mitigate this fact. Jira |
---|
server | Magnolia - Issue tracker |
---|
serverId | 500b06a6-e204-3125-b989-2d75b973d05f |
---|
key | DEV-798 |
---|
|
| 13 | No | after 6. | 2-2.5 weeks |
Actions0 | Content type powered config | Requires content type solution to be available. Would be nice to shave some config parts off the detail sub-app and form dialogs. Jira |
---|
server | Magnolia - Issue tracker |
---|
serverId | 500b06a6-e204-3125-b989-2d75b973d05f |
---|
key | DEV-1007 |
---|
|
| 8 | No | ideally in 6.0 but technically can be later |
Actions Jira |
---|
server | Magnolia - Issue tracker |
---|
serverId | 500b06a6-e204-3125-b989-2d75b973d05f |
---|
key | DEV-959 |
---|
|
Name | Description | Estimate | Resurface | Delivery |
---|
Re-start async action effort | Use Java 8 instead of Quartz. Try to ship the asynchronous-ness as a trait/mix-in of an action, not as some base abstract class User benefit: - Asynchronous actions may improve the perceived performance of the UI. Actions don't hang the UI.
- Triggering actions from a REST endpoint, without having to click the UI.
- Knowing when a command is done. Today, you execute a command and it doesn't come back and tell you when done.
Jira |
---|
server | Magnolia - Issue tracker |
---|
serverId | 500b06a6-e204-3125-b989-2d75b973d05f |
---|
key | DEV-816 |
---|
|
| 21 | No | Can be done after 6.0, should probably postpone.2 weeks |
MiscName | Description | Estimate | Unit testing | The effort is almost not covered by unit tests (the state of the API and implementation was fluctuating too much so far) | 3 weeks (+ maybe more since we'll need even more tests before final release)Resurface | Delivery |
---|
UI tests | See if it would be possible to re-use the UI tests for our own apps when they are ported to the new framework . Port the UI tests so they work with the newly migrated apps. Jira |
---|
server | Magnolia - Issue tracker |
---|
serverId | 500b06a6-e204-3125-b989-2d75b973d05f |
---|
key | DEV-1009 |
---|
|
| 21 | Yes, possibly. Resurface may introduce style name changes that break the UI tests. | 6.0 if we migrate all our own apps to the UI framework by release date2 weeks | UI push support | finally Finally incorporate Vaadin's push support . Replace poll with push. User benefits: Jira |
---|
server | Magnolia - Issue tracker |
---|
serverId | 500b06a6-e204-3125-b989-2d75b973d05f |
---|
key | DEV-797 |
---|
|
| 8 | No | Can be done after 6.01 week | Unknown unknowables | There are probably bugs in the new UI implementation, maybe there will be potential blockers even. I can't estimate that, but I'd add at least 2.5-3 weeks for that on top of the total estimate. | 21 | Yes, Resurface may cause bugs | 6.0 |
|