You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I chose to implement OSVR-Config using Angular 1, because Angular 2 is still in beta. However, A2 appears to be approaching release, so we should perhaps evaluate it and determine when to migrate. A1 will stop getting major updates and bug fixes will be slow to get fixed soon after A2 gets a final release.
Migration should obviously happen as soon as possible, as any new UI will need to be modified for A2. But we shouldn't migrate before any major bugs are fixed or breaking changes introduced as this would slow development of OSVR-Config.
A test migration in a branch (or a migration of a subset of the UI, say the RenderManager page) would help evaluate whether migration is feasible.
Things to check:
Can we still use Bootstrap? Currently we're using the angular-bootstrap library to help bridge angular and bootstrap. Do we still need it? Is there an A2 version?
Can we still use gulp for our frontend build? The tutorials on the A2 site all just grab frontend dependencies with npm and build with npm scripts, which I strongly recommend against. Need to determine a way to configure the module loader and/or our gulp build tasks to work nicely together.
Will A2 have a fit if we throw an iframe into the page? That's how we plan on implementing custom plugin configuration pages that are completely isolated from the rest of the app.
The text was updated successfully, but these errors were encountered:
I chose to implement OSVR-Config using Angular 1, because Angular 2 is still in beta. However, A2 appears to be approaching release, so we should perhaps evaluate it and determine when to migrate. A1 will stop getting major updates and bug fixes will be slow to get fixed soon after A2 gets a final release.
Migration should obviously happen as soon as possible, as any new UI will need to be modified for A2. But we shouldn't migrate before any major bugs are fixed or breaking changes introduced as this would slow development of OSVR-Config.
A test migration in a branch (or a migration of a subset of the UI, say the RenderManager page) would help evaluate whether migration is feasible.
Things to check:
angular-bootstrap
library to help bridge angular and bootstrap. Do we still need it? Is there an A2 version?npm
and build withnpm
scripts, which I strongly recommend against. Need to determine a way to configure the module loader and/or our gulp build tasks to work nicely together.The text was updated successfully, but these errors were encountered: