The "app in app" approach worked well to get it up and running, but creates some issues:
The parent app owns all child content, including the new UI, so any top level containers, like nav bars, need to be hacked around (using absolute positioning of the child app, etc.).
The app uses an iFrame for loading tasks into child windows , as configuring routing for a child "app in an app" is tricky, and would have to be reconfigured when the app is moved to the top level.
It might be better to create another front-end project project within the spiff-arena repo and move development there, these things will become harder to unwind over time.
The "app in app" approach worked well to get it up and running, but creates some issues:
The app uses an iFrame for loading tasks into child windows , as configuring routing for a child "app in an app" is tricky, and would have to be reconfigured when the app is moved to the top level.
It might be better to create another front-end project project within the spiff-arena repo and move development there, these things will become harder to unwind over time.