codevise / pageflow-linkmap-page Goto Github PK

On twitter, there has been the suggestion to allow changing the panorama background image when a hotspot is hovered. That way gallery-like effects could be created, where initially only parts of multiple images are visible and individual images can be "expanded" by hovering a hotspot.

Some things to consider:

• While everything that can be achieved with the current form of hover images (which are only displayed inside the hotspot area) could also be done with the suggested technique, the current approach requires downloading only two images instead of one per hotspot. Therefore (and also to preserve backward compatibility) this should be an additional option that can be used side by side with the current hover image. Hotspots with custom background images would not display the configured hover image of the page.

• On touch devices, the hover image is currently displayed by tapping a hotspot. The hotspot stays active until the user either taps another hotspot or the panorama background. If the background image changes when selecting a hotspot, only part of the image would be visible on small viewports. The current behavior would allow looking around. To prevent hiding the alternative background image by accident, one could consider keeping the alternative background until another hotspot is selected.

Hello dear Pageflow team,

i recently configured the hotspot feature to my pageflow installation but it seems that it does not work properly. I guess im doing something wrong.

I uploaded a panorama image and a hover image with highlighted hotspots. But when i hover over the hotspots, nothing happens.

Is there something i am forgetting?

I have found this error in my browser console:

Access to Image at 'http://my-bucket-name.s3-website.eu-central-1.amazonaws.com/main/image_files/processed_attachments/000/001/473/v1/panorama_large/my_project_intro_hover.JPG?1538666545' from origin 'https://pageflow.daad.de' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://pageflow.daad.de' is therefore not allowed access.

Thanks in advance and best regards,
Ronald

I cannot edit this translation it seems. Backgrund needs to be Background.

Hello.

I tried to install this plugin but get stuck with an error:

Could not find gem 'pageflow-linkmap-page (>= 0) ruby' in the gems avaiable on this machine

This appears after I changed all the files (Gemfile, pageflow.rb, js, css, etc) and run 'bundle install'

I also run 'bundle update pageflow' to get the newest version (0.9.1), but nothing worked.

Is there some magic we have to do in order to get it running?

Strange thing: this gem has no known version on github, could this be?

Regards, Johannes

Once pageflow-support is available via Rubygems, running exec/rspec should generate a dummy app and run the test suite. We should rename the script to bin/rspec to follow standard conventions.

When I try this plugin I get this error:

ActionView::Template::Error: Mysql2::Error: Table 'storyboard_production.pageflow_sites' doesn't exist: SHOW FULL FIELDS FROM `pageflow_sites`

I can't find the migration quickly. Is it somewhere else?

We've been working with this awesome plugin. It opens up a ton of possibilities for Pageflow stories.

Is it possible/easy to add an atmo audio for each individual area? In some cases we would like background audio to start playing on hover.

It seems all the building blocks are there in principe, it's just a matter of wiring them together?

When I click the 'Adjust Field of View' button for an external site thumbnail, nothing happens and this is shown in the console:

TypeError: this.model.getFilePosition is not a function. (In 'this.model.getFilePosition(this.options.propertyName,"y")', 'this.model.getFilePosition' is undefined)

It's clear to me why output of tagline, title and subtitle is not included in the linkmap page. These have fixed placement and this can interfere with the hotspots.

However we find ourselves wanting to include text to guide the visitor inside the page. It's not elegant to have to do this on a page before the hotspot page.

I propose this solution:

• render tagline, title and subtitle inside the page type
• default to display: none
• include the page ID in a wrapping div so the titles can be targeted using CSS
• allow theme developers to display and position the titles on a case by case basis

Thoughts?