RTIM-UI

version 2

goals

what we set out to do...

  • alleviate tech debt
  • remove auto-save
  • better nested views
  • component structure
  • forward looking
  • take baby steps

why not keep using v1?

  • over-engineered
  • architecture based on Angular internals and auto-saving
  • half baked nested view handling
  • relies on relational model baked into our RESTful API's
  • large-ish learning curve
  • poor tests
  • upgrade path unsure

component structure

SRP (Single Responsibility Principle)

  • cleaner
  • easier to read  and maintain
  • more testable
  • scalable

components

single component

hurdles?

  • getting v2 to work in a subdirectory (v2) with respect to the build
  • configuring v2 to currently work with v1 directives and services
  • template management
  • translations

profit

  • an architecture that is flat and easily testable
  • has an upgrade path to Angular 2 if we want
  • template caching (performance boost)
  • easier learning curve

possible next steps

  • move to its own GIT repository
  • create a separate build (perhaps RTIM-UI)
  • new asset build system (gulp/webpack)

code

thanks!

Ian Quattlebaum

References

Copy of RtimAdmin - Angular2

By ianqueue

Copy of RtimAdmin - Angular2

  • 573