Page History
...
| 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. | 2-2.5 weeks |
Actions
| Name | Description | Estimate |
|---|---|---|
| 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 | 2 weeks |
Misc
| Name | 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) |
| 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 | 2 weeks |
| UI push support | finally incorporate Vaadin's push support | 1 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 main estimate.
Overview
Content Tools