Hi gang. Does the title of this post… say it all?
Recently, I have been fascinated by the “feature” of being able to render multiple scenes to same canvas, and how viewports might get involved. AND, I’m still thinking about GUI ViewportControl… but… not important… yet.
Multiple engines to same canvas, too? One engine to multiple canvai? I’m SO confused.
IF we all “dreamed-up” a “branch-app” of the playground… that COULD be a nice “tour-around in THIS series of playgrounds”… what might that interface look-like? Got opinions?
Could we display thumbnail canvases (canvai?) of previous 5 playgrounds and next 5 playgrounds (if available in the PG database)?
Could we keep the GUI… workable for mobile devices… who use two-thumb touch-screening nav? (rather big buttons)
It is unlikely that we could allow “swipe”, because the thumb-nailed scenes need time to load-in and render. Swipe is too fast.
What might “jump forward/backward 10 scenes” GUI controls… look-like? (Try to keep two-thumbing on mobile touch-screen… easy)
I THINK the GUI buttons on this playground… are big enough to do 2-thumb-nav on mobiles… so the GUI from that pg… might be used as a starter. I haven’t tested GUI 2d on mobile devices much at all. A basic 4-borders-of-buttons PG - click here.
BUT… hmm… perhaps HTML controls for the “touring app”? Make the app more webpage than BJS scene? Maybe that’s the way to go. An 11-canvas webpage… one big canvas, 10 thumbnail-sized? I dunno. Thinkin’.
What might we want… IF we COULD plan/install a “tour this playground series” sub-app for our current PG app?
Anyone have thoughts? Thx.