mbritton / responsive-page-system Goto Github PK

Hi Mike,

I forked and did a bit of work on this, which I've checked in on my fork, but ultimately, I think a better mechanism should be used than the PageProxy. I was going to try and remove all references to the AppConstants and BottomNavView from it but ultimately this should be combination of business logic in Commands working with a Mediator, similar to the way the StateMachine works. It is a view contraption. The history could be stored in the data property of a framework proxy instance, but the Proxy shouldn't be doing a lot of stuff that at its heart is view mechanics. That's for the other tiers.

Also, I noticed that the PageProxy defined a bunch of data for pages which I don't see when I check out the demo. On the demo I see grids with rows and each page's grid is a slightly different shade of grey. What's up with that? Vestigial remains of a previous approach?

-=Cliff>