Unifying the View System

Added by Scott Cytacki, last edited by Scott Cytacki on Mar 03, 2008

We are considering unifying the 2 view systems in use: the Pas View System, and the OTrunk View System.

Reasons to Unify

  1. So new steps or views created by developers can be shared between Pas and OTrunk Views.
  2. So developers working on projects that use Pas and OTrunk Views don't have to learn both
  3. So improvements to the system itself benefit both Pas and OTrunk Views.

Current state

OTrunk Views can be embedded as steps inside of Pas. This works when Pas is run using the Pod content model or the OTrunk content model. This means that a developer familar with OTrunk can make new "step" inside of Pas.

Problems with the current state

Paths to Unification

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.