Open quinkennedy opened 7 years ago
@quinkennedy The current mechanism instantiates the new prefab and destroys the old view object. The framework doesn't make assumptions as where the views are located so implementing this in a generic way is not easy. That said, as with everything, you could implement it yourself.
Is the Router and Middleware included meant as a bare-bones example of how those items work, and the expectation is that extra functionality should be handled by writing custom Router/Middleware?
I noticed that the current Router also never pushes views to the history. Should I add that and submit a pull request, or is it expected that users will implement their own routers/middleware to add these kinds of functionality?
Is there a way to define smooth transitions between views? For instance, when using router.Goto() I'd like the new view to slide in from the right, and the old view to slide off the left.