51

(495 replies, posted in Juicebox-Pro Support)

I am more thinking like playback YouTube movies, a nice HTML5 video player

52

(495 replies, posted in Juicebox-Pro Support)

I would like to play small webmovies in Juicebox

53

(495 replies, posted in Juicebox-Pro Support)

Thanks for your reply, once I had found web browser add-in for jpeg2000 support but that was a long time ago and only for IE.
There is a MS jpeg2000 plugin for Photoshop and it is part of Windows Media Photo. So there is a codec for it. I have found an article of 2006 that Apple and Adobe are blocking any webbrowser support of JPEG2000 because of license payments

Jpeg is not the best quality format for pictures, it is limited to 8bit and sRGB colorprofile. I was hoping that is was possible to build it in Juicebox.

Steven wrote:

@arachnid

Support for JPEG2000 file format

As far as I am aware, none of the major browsers (Chrome, Safari, Firefox, Internet Explorer and Opera) natively support JPEG2000. They cannot display a JPEG2000 image directly or in a <img> tag within a web page without a plugin (at least on my Windows PC). Unfortunately, until browsers support JPEG2000, Juicebox will not be able to display JPEG2000 images.
Also, it looks like JuiceboxBuilder-Pro will not be able to process JPEG2000 images as it is an Adobe AIR application. Adobe AIR uses Adobe Flash Player as its runtime environment and according to this web page, Adobe Flash does not seem to support JPEG2000.

@Martina

Is this already something that can be done?

No. This is not currently possible. Thank you for the suggestion.

54

(495 replies, posted in Juicebox-Pro Support)

Support for JPEG2000 file format

Custom theme is fine.
I prefer a black background color. It is working fine in Chrome and Firefox. Fullscreen is working in Opera Next but background-color : #000000; has no effect. Safari is making a mess of the gallery presentation.

arachnid wrote:

Hi Steven,

Is my custom theme a good location or must it be a separate CSS file after the juicebox scripts?

kind regards

Hans

Steven wrote:

This is due to your gallery's backgroundColor being 'transparent' and each browser having a different deafult background color when the Fullscreen API is used. Firefox uses a black background whereas Chrome uses a white background. See the 'Styling it all' section on this web page.

Firefox applies this by default along with background-color: black

To set the default background color to white for Fullscreen API mode in all browsers, use the following CSS in the web page containing your gallery:

#jb-glry-dlg:fullscreen {
    background-color: #ffffff;
}            
#jb-glry-dlg:-moz-full-screen {
    background-color: #ffffff;
}            
#jb-glry-dlg:-webkit-full-screen {
    background-color: #ffffff;
}

Please note that the code above does not set a new gallery background color for Fullscreen API mode. (The gallery's own background color will still be used.) It simply sets a default background color which will show through if the gallery's own background color uses transparency.

I have notified the developers of this inconsistency.

Hi Steven,

Is my custom theme a good location or must it be a separate CSS file after the juicebox scripts?

kind regards

Hans

Steven wrote:

This is due to your gallery's backgroundColor being 'transparent' and each browser having a different deafult background color when the Fullscreen API is used. Firefox uses a black background whereas Chrome uses a white background. See the 'Styling it all' section on this web page.

Firefox applies this by default along with background-color: black

To set the default background color to white for Fullscreen API mode in all browsers, use the following CSS in the web page containing your gallery:

#jb-glry-dlg:fullscreen {
    background-color: #ffffff;
}            
#jb-glry-dlg:-moz-full-screen {
    background-color: #ffffff;
}            
#jb-glry-dlg:-webkit-full-screen {
    background-color: #ffffff;
}

Please note that the code above does not set a new gallery background color for Fullscreen API mode. (The gallery's own background color will still be used.) It simply sets a default background color which will show through if the gallery's own background color uses transparency.

I have notified the developers of this inconsistency.

Hi Steven,

Thanks, I shall follow your advice.

regards
Hans

Steven wrote:

This is due to your gallery's backgroundColor being 'transparent' and each browser having a different deafult background color when the Fullscreen API is used. Firefox uses a black background whereas Chrome uses a white background. See the 'Styling it all' section on this web page.

Firefox applies this by default along with background-color: black

To set the default background color to white for Fullscreen API mode in all browsers, use the following CSS in the web page containing your gallery:

#jb-glry-dlg:fullscreen {
    background-color: #ffffff;
}            
#jb-glry-dlg:-moz-full-screen {
    background-color: #ffffff;
}            
#jb-glry-dlg:-webkit-full-screen {
    background-color: #ffffff;
}

Please note that the code above does not set a new gallery background color for Fullscreen API mode. (The gallery's own background color will still be used.) It simply sets a default background color which will show through if the gallery's own background color uses transparency.

I have notified the developers of this inconsistency.

Thanks!

Why is in useFullScreenExpand mode the background in Firefox black and in Chrome White?

Steven wrote:

If showExpandButton is set to 'TRUE, the Expand Button will be displayed on the Button Bar.
When a gallery is expanded (via the Expand Button), the gallery will (by default) fill the user's browser window.
However, if useFullscreenExpand is set to true, the gallery will fill the user's entire screen (not just the browser window) but only in browsers which support the Fullscreen API.
Please see these pages for more information on the Fullscreen API:
http://www.w3.org/TR/fullscreen/
https://developer.mozilla.org/en-US/doc … creen_mode

For a list of browsers which currently support the Fullscreen API, please see here.

Is it possible to configure the look-and-feel of the useFullScreenExpand page?

An expanded gallery (whether useFullscreenExpand is used or not) uses the same configuration options as the gallery in normal (unexpanded) mode.

What is the difference between showExpandButton and useFullScreenExpand?

Is it possible to configure the look-and-feel of the useFullScreenExpand page?

I can't get useFullScreenExpand working on an Ipad (Chrome) or Android phone (Chrome and Firefox)
It works fine on a desktop/laptop

60

(5 replies, posted in Juicebox-Pro Support)

Hi Steven,
Sorry that I have bothered you with this non-issue. The browsers are only loading the custom theme.
But yesterday after I have changed it to the custom theme juicebox did load both CSS files and I don't understand why.

61

(5 replies, posted in Juicebox-Pro Support)

Hi Steven,
Sorry to tell you but at my website Juicebox is loading the custom Theme and the Classic theme. Please check www.delosgaia.nl with firebug or F12 developer tools.

Tell me what I have done wrong,

regards
Hans

62

(5 replies, posted in Juicebox-Pro Support)

I am using a custom theme for media queries (font-size) and it is working. I have noticed that Juicebox is first reading my custom theme and then the classic theme.

Does this mean that I only have to put the changed CSS settings in my custom theme?

63

(495 replies, posted in Juicebox-Pro Support)

I am using baseURL in the juicebox script but have to edit the SEO content and full.html manually to get them working. Would like to see that this can be set in the JuiceboxBuilder Pro

64

(495 replies, posted in Juicebox-Pro Support)

I would like to see a responsive font-size and line-height based on width of gallery and device. By default the font-size and line-height is set in theme.css for all devices.
The best would be a font-ratio and line-ratio with a minimum and maximum device-width

65

(8 replies, posted in Juicebox-Pro Support)

I had the same problems and have solved it. See http://www.delosgaia.nl/ how I have done it. Real responsive is not possible except when working with an iframe or full page with only one DIV. Do not define a gallerywidth and galleryheight in percentage but use px.

regards
Hans


DaveOzric wrote:

Hello, didn't find this topic or don't know how to word it correctly in a search.

Basically I would like to make a slider for a HTML website that is the size of the images and responsive. No thumbs or nav or buttons. Just a set of images that fade and repeat. I have this part working already.

When I create one that is responsive it seems to have to be 100% width and height. That however fills the screen.

If I make the gallery a fixed size it works but is not responsive.

Am I missing a setting that makes both these possible?

Thanks

66

(495 replies, posted in Juicebox-Pro Support)

or disabling. It will solve many of my web development problems.

dlydiard wrote:

it would be nice to have the hashtag url's be configurable.

so instead of getting site.com/#1 , site.com/#2 etc.
if can be site.com/#name-of-some-picture

perhaps the hashtag url can be set in the xml config file.

I have tested your advice; $(document).ready(function () {}) but it don't work.

I have tested many more and removing javascripts. No succes, I haven't tested google maps and translate but will do this later.

I am surprised that Juicebox is using JQuery 1.7 as the build-in JQuery library.

O ja, IE9 is also effected.

Hi Steven,
Thanks for testing and confirming. I shall test your suggetion. I'll keep you informed.

For your information, IPad 3 with Safari is showing the same problem. theme.css is not loading. Safari for Windows don't have the problem.

kind regards
Hans

Yes, IE8 mode in IE 10 is working fine but this is a quirk mode of IE10 and not truly IE8. For a long time I was using the IE9 and IE8 quirks mode in IE10 for testing till last week. I was last week by a customer of mine who is still using XP and IE8 (for how long) and noticed that Juicebox is not displaying.

Go to http://www.microsoft.com/en-us/download … x?id=11575 and download a Windows 7 VM with IE8. This is for testing purposes only. Please, check it yourself.

In my websites I am using a jquery function named $(window).bind('resize load', function(e) for different body width of the webbrowser. This was working fine in IE8 with juicebox 1.3 and earlier.
With juicebox 1.3.1 is isn't working anymore, the gallery is not visible in IE8. After a long research and troubleshooting i have found that IE8 and sometimes IE9 isn't loading the themeURL.
I have placed the call to the themeURL in new juicebox but without succes.

new juicebox({baseUrl: 'design4/header/madagascar/',themeUrl: 'resources4/jquery/jbcore/classic/theme.css', containerId: 'box_slideshow',galleryWidth: '917px',galleryHeight: '273px',backgroundColor: 'transparent'});}

What did help is the following

<link rel="stylesheet" type="text/css" href="resources4/jquery/jbcore/classic/theme.css" />

Examples: next page is working with IE8 (don't use IETester, this program is buggy)
http://afrika.delosgaia.nl/visit_to_madagascar.htm
This page is working with IE 10 but not with IE8
http://afrika.delosgaia.nl/visit_to_mad … narivo.htm

71

(7 replies, posted in Juicebox-Pro Support)

It 1.3.1 is working fine.

Do you support IE7/8 with Juicebox. jQuery 2.0 doesn't

72

(7 replies, posted in Juicebox-Pro Support)

Steven wrote:

Yes, this is the solution but I see this is a problem with 1.3. I have used this all the time with the previous Juicebox.net. I am using a local cdn named data.delosgaia.nl and this is working fine for all my javascript and CSS files.

It looks like there is a cross-domain/subdomain issue with loading fonts...
Please see the accepted answer to the question in this forum thread for a possible solution...

OK, thanks for the info. I'll keep your informed

73

(7 replies, posted in Juicebox-Pro Support)

Steven wrote:
Hans wrote:

How can I turn this option completely off

This is not possible. Juicebox-Pro now enables the # identifier automatically to allow social sharing of a specific image.

OK, fine, no problem. But please make it unique and not just a number. example: #juicebox1

74

(7 replies, posted in Juicebox-Pro Support)

Great, I love this

75

(7 replies, posted in Juicebox-Pro Support)

Yes, this is the solution but I see this is a problem with 1.3. I have used this all the time with the previous Juicebox.net. I am using a local cdn named data.delosgaia.nl and this is working fine for all my javascript and CSS files.

Steven wrote:

The first problem is likely to be due to your gallery's 'jbcore' folder being hosted on a different subdomain to the page containing your gallery's JavaScript embedding code. All gallery files should be on the same domain or subdomain as the JavaScript embedding code. Try hosting the 'jbcore' folder on your http://afrika.delosgaia.nl subdomain.

My page is rendering perfectly it has a horizontal slider (Coda-slider) and #2 is page two. But I have changed it from #2 into #b. The page has three parts, when you click at the text Verslag you will get three options.

#a ==> autoplay gallery
#b ==> juicebox gallery
#c ==> google map

Yes, this is the solution but I don't like this at all, Juicebox variables are interfering with the other functions in my website. I don't use the backbutton URL and I am not interested in direct linking.

How can I turn this option completely off


With regard to the second image being the first one displayed, the link you provided has a #2 at the end of it signifying that Juicebox should go directly to the second image.

When viewing your web page, I sometimes see only a slim AutoPlay Juicebox gallery.
Other times I load your page, I see a completely different Juicebox gallery with thumbnails.
Another time, both galleries were displayed with a map at the bottom of the page (same computer, same browser, same monitor).
Your web page is not being rendered consistently and, as I cannot always view the gallery in question, it is difficult to try to determine the problem.