Jamie Lentin

The data side of this is done, the visual appearance is going to be dealt with at some other stage.

Yes, this is pretty simple nowadays. The following is enough to make the "Hide panel" button in museum display a "toggle full screen" button, at least in FF/Chrome. Looks like...

There's the enticingly-named https://github.com/OneZoom/OZtree/pull/687 (Remove treebuild), but looks like Yan got side-tracked. ``./OZprivate/ServerScripts/SQL/create_db_indexes.sql`` and ``OZprivate/ServerScripts/Utilities/partial_install.py`` should definitely stay in OZtree. The rest is probably unused

The actual sizing is fairly easy, using ``transform: scale(..)``. As the scale gets applied post-layout, this gets us the overlap too. Nice. The problem is element ordering / stacking. By...

Another issue here is the transition, the easiest thing is to shuffle them and let the z-index update at the end, but it's a slightly implausible jump---everything moves, then suddenly...

That example only has one active item, so isn't very interesting. Like I said above, the sizing that parallax offers isn't the hard problem to solve. We have an arbitrary...

@hyanwong b6a4a9d attempts this. It's a bit clunky and not all the elements are sized yet, but it's a lot closer to something working. The reason for the jumpy animation...

> In some cases the images are all the same size when the page loads for the first time Yes, you've spotted this bodge: https://github.com/hyanwong/OZtree/commit/413ef51293a33384f8c8a33b9f7c6f32e10dfc9d#diff-e926f4476fdb03d0714ad2b7c90f75aaR104 itemshown doesn't trigger as UI-Kit...

You have a point, but over 4 years I'm sure the few days taken to notice it needs verification could be forgiven. If we move the update then there's potential...

Yeah, I do kind of agree. ``record_url``() should be leaving all querystring parameters it doesn't understand, and then the UI would be free to add ``pop=ol_12345`` as it needs. This...