Page History
...
| 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 |
Configuration
| 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 |
Overview
Content Tools