Skip to main content

Working on CMS & Conditional Visibility

I'm back on track with the CMS today.

After getting text from a CSV back to work again linked to a text component in the skin, I got the following cool things to work:

  1. Image url from CSV to load in as a dynamic image in the skin
  2. Boolean/checkbox (true or false) from CSV to show or hide a skin component
  3. Update a CSV with a new CSV with option to merge (check if it already exists, if so, then update that thing otherwise create a new thing)
  4. Dates from CSV

Currently working on Conditional Visibility. First just in skin components, then also for hotspots.

Why is Conditional Visibility awesome?

It means that you can only show products/information points/projects or whatever your 360° tour is about based on dates for example and keep the tour up-to-date.

Only show this hotspot if the date of the hotspot is before today

This stuff I get paid very well for in 3DVista projects for enterprise clients setting up skin cms combined with complex javascript code. And now it will be just a part of 360Crafter without the javascript and without skin cms.

I know for some people this might sound very complex. Because most of us are not used to think in terms of data and conditional logic. But once you get it, you get it. And that opens up lots of ideas 😁

I will set up meetings to go through some examples and make tutorials of course 🤓 👨‍🏫

Working on CMS & Conditional Visibility

Peter Heerink

Sounds very good, for the escaperooms expierence we could implement similar for conditions set. Like number of items found etc. A hint showing after a certain time etc

Ronald

Haven't thought about it like that yet, but yes indeed! I will think more of that