is it possible to have all these albums taking there set up details ALL from the same solitary JB Index.html and JB config.xml

No. Each gallery must have its own embedding code and XML file.
However, these text files are relatively small, do not take up much room on a web server, do not take long for browsers to parse and are created automatically in programs such as JuiceboxBuilder-Pro.

ah, i have since thought, that possibly what i am trying to accomplish is better done and possible using Jalbum using the JuiceBox Skin !!!!!

The Juicebox Skin will create a gallery for each folder in your input structure and will link together all the galleries via a navigation tree in a side menu (rather than having a front page with links to all the galleries). Rather than flipping back and forth between the 'links page' and the galleries, the tree is still visible after selecting a gallery and the user can select another gallery without returning to the 'links page'. When viewing any gallery, the viewer can temporarily hid the navigation tree (to allow more room for the gallery to be displayed) by clicking the 'Expand Button'.

Am i correct in thinking, that when using my very own Web Space, to publish my Flickr based Image Galleries using Jalbum, that Jalbum will not cause any problems to my Juicebox galleries that up to now i know perform excellently on an iPhone :)

It is not possible to automatically create Flickr-based galleries using the Juicebox Skin for jAlbum. Manual editing of the album files would be required.

Am i correct in thinking ... that Jalbum will not cause any problems to my Juicebox galleries

... as long as you do not overwrite any existing galleries by uploading albums or galleries to the wrong locations.

5,702

(8 replies, posted in Juicebox-Pro Support)

1) all thumb nails have shrunk to very very small in thumbnail screen

Try adding the following line of code to the <head> section of the HTML page into which your gallery is embedded:

<meta name="viewport" content="width=device-width, initial-scale=1">

2) all OVERLAY buttons or even I set TOP still missing (thus I cannot go back to thumbnail screen any more)

This is a known bug which has been addressed and should be fixed in the next version.

5,703

(498 replies, posted in Juicebox-Pro Support)

@otaku521

This can be achieved by following the instructions in this post.

5,704

(7 replies, posted in Juicebox-Pro Support)

my apologies if i should post these questions somewhere else, please let me know if so.

Absolutely fine here. No problem!

Thank you for providing the additional information and link to your existing galleries.
A couple of global search and replace actions on your gallery XML files should be all that is required to have svBuilder-Pro successfully open them.
Open each XML file in a plain text editor and replace each instance of <name> with <filename> and each instance of </name> with </filename>.
If you have a text editor such as Notepad++, you can open all your XML files at once and a single search and replace action will replace all the tags in all the files in one go.

5,705

(8 replies, posted in Juicebox-Pro Support)

It might be easier if you set your gallery's dimensions to anything other than 100% x 100% (e.g. 99% x 99% or absolute pixel values such as 800 x 600) and then set showSplashPage="NEVER" so that on mobile devices, users are not presented with a 'View Gallery' Splash Page which, when clicked, would display the gallery at 100% x 100%, disabling pinch zoom.

5,706

(8 replies, posted in Juicebox-Pro Support)

You will not be able to pinch zoom if the gallery's dimensions are 100% x 100%. The maximum-scale is set to 1 in this scenario.
You could try using JavaScript to determine the size of the user's browser window and then set the gallery's dimensions to those absolute pixel values instead.

If you like, you could post this suggestion as a feature request in this thread so that it does not get overlooked.

5,708

(2 replies, posted in Juicebox-Pro Support)

The Back Button is available only in Large Screen Mode.
The default value for the screenMode option is AUTO so when the gallery is displayed on an iPhone, Small Screen Mode is used.
You can force the Large Screen Mode to be used on all platforms (which will then display your Back Button) by setting screenMode="LARGE" in your gallery's XML file.
If using JuiceboxBuilder-Pro to create or edit you gallery, this option can be found in the 'Customize -> General' section.
For more information about Screen Modes, please see here.

(The Back Button is marked as a 'Large Screen Mode only.' option on the Juicebox -Config Options page.)

5,709

(1 replies, posted in Juicebox-Pro Support)

This might be a bug. I will investigate further. Thank you for reporting.

5,710

(1 replies, posted in Juicebox-Lite Support)

I am not familiar with the W3 Total Cache plugin.
It may be possible to configure the plugin (via its settings panel) to not cache XML files. (Check with W3C Total Cache support if unsure.) If it is, disable caching of XML files and recreate your gallery. Each new Juicebox gallery created with WP-Juicebox has a unique XML file with a unique name so, with caching of XML files disabled, the new gallery's XML file should not be cached and the gallery may work as expected.
It may also help if I were to see the gallery in action so, if possible, please post the URL to your gallery so that I can take a look.

5,711

(4 replies, posted in Juicebox-Pro Support)

IF i used the Jalbum Web Space the resulting gallery wouldn't be correct on an iPhone

That is correct. jAlbum storage is not like a regular web host. All albums hosted on jAlbum.net (no matter what skin was used to create them) will look identical on an iPhone.
Just upload your album to your own web space and all will be well.

It is not possible to change the image transition type from SLIDE on mobile devices.

Changing enableTouchZoom will toggle the ability to pinch zoom on mobile devices and has nothing to do with the image transition.

Setting forceTouchMode to FALSE (default setting) will allow Juicebox to be displayed in Mouse Mode in desktop browsers whilst displaying Juicebox in Touch Mode on mobile devices.
Setting forceTouchMode to TRUE will force Juicebox to be displayed in Touch Mode in both desktop browsers and on mobile devices.

On mobile devices, Touch Mode will always be active (this cannot be overridden) and in Touch Mode, the image transition type will always be SLIDE (this also cannot be overridden).

5,713

(9 replies, posted in Juicebox-Pro Support)

I think this problem may also have something to do with your web server (and specifically the way it serves up some files to browsers).
I have used your 'rhodes_gallery.html' and 'config.xml' files in a test gallery, uploaded it to my own web server and the gallery displays fine in IE9 (with my own images) so there is nothing wrong with the code of either of your files.
The default settings on your test web server may be too restrictive.
Are you able to test your gallery on the web server you intend to use permanently? I suspect you will find that it will work fine in IE9 on your other host.

the above code has to go in an html page

Correct.

the page has to be named index.html

Incorrect. The page into which the embedding code is inserted can be called anything you like.
If embedding using the guide here, just watch out in case the 'index.html' file from the gallery folder overwrites an existing file named 'index.html' which you may already have.

Embedding a gallery means to place the gallery in an existing web page alongside other content, rather than simply opening the gallery on a page of its own (though, technically, the gallery's own 'index.html' file still embeds the gallery but with no other content on the page).
Here is a gallery on its own (opened by loading the gallery's own 'index.html' file): http://juicebox.net/demos/lite/full/
Here is a gallery embedded in a web page: http://juicebox.net/demos/lite/embedded/

5,715

(4 replies, posted in Juicebox-Pro Support)

A multi-gallery album generated by jAlbum and the Juicebox Skin displays and functions fine on my iPod Touch iOS 5.1.1.

If you do not like the Splash Page and would like the gallery to initially appear, you can set showSplashPage="NEVER" in the Pro Options text area.

If you like, you could also set screenMode="LARGE" to force the gallery to be displayed as if it were on a device with a larger screen.

If you do not like the way the web page is scaled on a mobile device, you could add the following line of code to the <head> section of your album's 'index.html' page:

<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1">

If you would rather simply create a single gallery like JuiceboxBuilder or the Lightroom, Photoshop or Picasa plugins (rather than a multi-gallery album with a navigation tree menu), then go to 'Album -> Settings -> Advanced' and deselect the 'Process subdirectories' checkbox. jAlbum will then process only those images in the root input folder and a single gallery will be created which will look identical on an iPhone (or any other device) to a gallery created by any other method.

It was a lot easier IMHO following your instructions that the instructions given by Jalbum.

I have now added instructions on how to open the skin directory in the jAlbum instructions.

How can i confirm that i have carried out my task successfully, is there a way of checking the version number or similar ?

Create a test gallery and check to see if the Juicebox badge/link in the bottom-right corner of the gallery is present.
It is always present in a Jucebox-Lite gallery but never present in a Juicebox-Pro gallery.

FOR EXAMPLE i still only have the default style available from the drop down box.

This is a jAlbum setting (not a Juicebox setting) which skin developers can choose to use if they wish. It is not relevant to Juicebox, hence there is only one available setting. Perhaps when Juicebox supports more themes in the future (other than the current 'classic' theme), the jAlbum 'Style' combobox could be used to select the theme.

i suppose i also have to ask where do i find this form ?

Click the leopard-skin icon to open the Juicebox skin settings tab (or select 'Album -> Settings -> Juicebox' from jAlbum's drop-down menu at the top). Now select 'Juicebox' to find the 'Pro Options' text area.

and where do i find the names and values ?

Names and values of all Juicebox configuration options can be found on this page.

5,717

(7 replies, posted in Juicebox-Pro Support)

Is there another place I can vote for the thumbnail grid ??

Please post feature requests in this thread so that they are not overlooked.
Thank you.

The 'jbcore' folder to replace can be found by selecting the Juicebox skin and then going to 'Tools -> Skin Directories -> Open skin directory' from jAlbum's drop-down menu at the top. Now that you are inside the skin directory, go to 'res/juicebox/'. (I've now added this information to the instructions on the jAlbum Juicebox skin download page.)

The Pro 'jbcore' folder you should use to replace the Lite 'jbcore' folder in the skin directory can be found by unzipping the Juicebox-Pro download package and going to 'juicebox_pro_1.0.2/web/'.

5,719

(8 replies, posted in Juicebox-Pro Support)

There is I believe a small bug that is if you enter html code (e.g. <br>) in the title field in Lightroom the plugin hangs.  This also applies if it is in the presets XML options.

Unfortunately, this is a known issue for which there is no known fix. However, if you delete the HTML code from the 'Gallery Title' text field, the Live Preview window should return to normal.

5,720

(2 replies, posted in Juicebox-Pro Support)

The 'Expand Button' will be shown only if the gallery's dimensions are less than 100% x 100%, if the gallery's dimensions are expressed as absolute pixel values or if the gallery is embedded in a web page alongside other content. Otherwise, the gallery will already be displayed as large as possible within the browser window (filling the browser window) and cannot be made any larger so the 'Expand Button' would be redundant and is automatically disabled.
To fill the user's entire screen (rather than just the browser window) the user must press F11.
Currently, in order to use keyboard shortcuts such as F11, the user must first click in the address bar to give focus back to the browser. This is a known bug which has already been addressed and will be fixed in the next version where F11 will work even when the gallery has focus (i.e. the user has clicked somewhere within the gallery area).

When you create a gallery with JuiceboxBuilder, you have a couple of options.

(1) You can ignore the embed code provided and simply view the gallery on its own web page by opening the gallery's 'index.html' page (inside the gallery folder) in a browser.
If you wish to link to the gallery from another web page, it is this 'index.html' page that you should link to.

(2) You can embed the gallery in an existing HTML page alongside other content by using the embed code provided by JuiceboxBuilder and following the instructions here.

so what advantages are there, that using the juice box lite App gives me over using Jalbum ?.

They are simply different ways of creating a Juicebox gallery. There are also plugins available for other programs such as Lightroom, Picasa and Photoshop. Use whichever method you are most comfortable with. Some people already use programs such as Lightroom so having a plugin for Lightroom fits in well with their current workflow.
For those not currently familiar with Lightroom, Photoshop, etc. a plugin is of little use which is why we provide JuiceboxBuilder-Lite (a standalone application dedicated to creating and editing Juicebox-Lite galleries) with the Juicebox-Lite download.
The jAlbum skin has the ability to create multi-gallery albums in a single action (by dragging and dropping an entire folder structure into jAlbum's main window). A Juicebox gallery will be created for each folder/subfolder in your input structure and all the galleries will be linked together by the JavaScript navigation tree. You can also upload the resulting album directly to your web space via jAlbum's built-in FTP functionality.

If you were to purchase Juicebox-Pro, you would gain access to the many Pro Configuration Options which are not available to Juicebox-Lite users and the 50-image per gallery limit would be lifted. Other benefits of Juicebox-Pro over Juicebox-Lite can be found on this page.
You could integrate Juicebox-Pro into the jAlbum skin by following the instructions on this page. Pro Options should be entered into the skin's interface as lines of text, such as:

option1=value1
option2=value2

As a Juicebox-Pro customer, you will also have JuiceboxBuilder-Pro which allows you to create a Juicebox-Pro gallery with all available Pro Options configurable via the interface (without the need to type or copy/paste text). The live preview window also shows you exactly how your gallery looks as you make changes.

The .air file extension signifies that the file should be handled by the Adobe AIR installer.
JuiceboxBuilder requires Adobe AIR v2.0 or later. The latest version of Adobe AIR (v3.3) can be downloaded from this page.
It is safe to install both Adobe AIR and JuiceboxBuilder on your Mac.
Please see the JuiceboxBuilder User Guide for details.

5,724

(7 replies, posted in Juicebox-Pro Support)

i imagine i need that to upgrade my albums to v2?

It would become a two-step process but you could use svBuilder-Pro to first convert your SimpleViewer v1.9 galleries to SimpleViewer v2, then you could use JuiceboxBuilder-Pro to convert your SimpleViewer v2 galleries to Juicebox.

any chance the wonderful grid home page of sv will ever make it to juicebox?

I do not know about the possibility of having a grid of thumbnails but further thumbnail positioning options are currently being considered.

5,725

(8 replies, posted in Juicebox-Pro Support)

There is I believe a small bug that is if you enter html code (e.g. <br>) in the title field in Lightroom the plugin hangs.  This also applies if it is in the presets XML options.

Thank you for reporting. I will log a bug report and hopefully this can be fixed in a future version.