680505_en-US

liliconcom

Re: Interactive HTML - catch problems - Status changed to: AcknowledgedRe: Interactive HTML - catch problems

@dieter_pisot wow, that was fast!
I know other wish list entries which wait since years to get acknowledged

Re: Interactive HTML - catch problems

HI @hogi

 I think i was just scanning the wish list for html5 related items at the time you entered the suggestion. So I quickly moved it over into our backlog

Re: Interactive HTML - catch problems

excellent

Interactive HTML - catch problems

☐ cool new feature
☑ could help many users!

☑ removes a „bug“ (although it's mainly not a Jmp bug

☐ nice to have

☐ nobody needs it

 

 

What inspired this wish list request? 

 

At the moment, when I want to share an interactive Jmp file via Teams or Sharepoint, my colleagues just see:

... and think that there is an issue with Jmp - or an issue with my Jmp file.

 

For them, it's hard to find out that actually it's a Teams / Sharepoint  issue with the interactive JavaScript code.

 

interactive html in Teams Channels 

 

What is the improvement you would like to see? 

 for a future version of Jmp, would it be possible to slightly change the code of the interactive HTML?

Instead of starting right-away with the start animation,  the HTML code could check if Java Code can be executed and if not: show a warning that it's actually the browser or the site which prevents the page to be loaded correctly. Then it could show a suggestion to download the file and open it from the hard drive.

 

Why is this idea important? 

MS Teams, Sharepoint and Onedrive is used in many companies.

Not every Company with Jmp licenses has a Jmp Live Server.

 

Therefore, users share interactive HTML files via Teams and Sharepoint - more and more in the future ....

 

If there are non-functional files, which were generated by Jmp,  this will "fall back" to Jmp.
The new functionality will make sure that users understand the ussue and that they know how to make the files work.

 

Alternative solution:
- Use in interactive HTML a code that is accepted by Teams/Sharepoint

- align with MS how to solve the issue

 

 

 

 

more wishes submitted by  

Sharing and Communicating ResultsRe: Interactive HTML - catch problems

I have updated JMP's Interactive HTML generation code in JMP 19 to detect if the environment where the file is being opened has JavaScript disabled. If it is not enabled, a message will be displayed saying so instead of displaying the loading graphic and trying unsuccessfully to run the JavaScript code necessary to display the interactive graphs and tables contained within.

 

Our code cannot learn enough about the environments in which you share your files to explain how to make web pages requiring JavaScript work in these environments. Typically, the only option is to download the file and open it in a browser with JavaScript enabled. 

 

~John

 

Re: Interactive HTML - catch problems

@John_Powell_JMP , very helpful. Many thanks : )

 

Re: Interactive HTML - catch problems

Maybe with focus on the Teams / sharepoint issue, one could add a vague suggestion to download the file and open from hard drive.

Re: Interactive HTML - catch problems

Hi @John_Powell_JMP , Many , many thanks for this improvement.

 

it will be available in EA4?

EA3:

 

Re: Interactive HTML - catch problems

Hi @hogi ,

 

You're welcome and thank you for the suggestion.

It didn't make it into EA4, but it should be available in EA5.

We're still testing it in different environments. I look forward to hearing that it works in your environment.

 

Thanks, 

~John

 

Re: Interactive HTML - catch problems

ok, perfect. I will check ...

Re: Interactive HTML - catch problems

Hi @hogi , 

 

Thanks for trying this and providing feedback. 

 

The detection of an environment that prevents JavaScript from running isn't specific to Teams or SharePoint. Our Interactive HTML files are being shared in many different ways. Here are a few examples:

 

1. As an email attachment. Previewing HTML files with JavaScript is often disabled for security reasons. 
2. On a web site. It is also possible that this restriction is encountered on a mobile device, where downloading to a hard drive is not meaningful. 
3. On a shared network drive or shared as a zip file, or other media and extracted to a hard drive. If the file is opened in a browser with JavaScript disabled we'll detect that.

We will consider extending the message to offer more advice. The trick is to do it in a way that will not confuse some users. 

 

Thanks, 

-John

 

 

  

Re: Interactive HTML - catch problems

: )

Re: Interactive HTML - catch problems - Status changed to: DeliveredRe: Interactive HTML - catch problems

Thanks : )