Print

[Αndré]

This is a simple panorama viewer. It uses HTML to prevent large images breaking your website design. If you upload an image with the extension '_360pano.jpg', the script will loop the image. <- the string is configurable since plugin version 1.4

It's tested only with my preferred settings yet. Please report any messy behavior.


Version 1.4 adds a configuration interface:

Panorama detection (+ corresponding Value)

• By picture width - The panorama viewer code is just applied if the picture's width exceeds a fixed pixel value
• By picture ratio - The panorama viewer code is just applied if the picture's width is at least x times the picture's height
• By file name - The panorama viewer code is just applied if the picture's file name contains a fixed string
• Always - The panorama viewer code will be applied to all pictures

360° panorama file name string - If the picture's file name contains that string, it will always be looped (ignores above settings)

[Pascal YAP]

Great :-)
Is there an example online right now ?

[Αndré]

I just created this for you

[Pascal YAP]

Thanx for all users :-)
Very interresting ! Stunning !!!

[SaWey]

This is a great plugin, unfortunately it doesn't seem to work in Chrome and IE.
I think it has something to do with the 'table-layout' style attribute.

[Αndré]

it doesn't seem to work in Chrome and IE.

Yes, that's why I said

It's tested only with my preferred settings yet.

= Coppermine settings and my firefox 3.0  

In my first version (0.1.0) I used a fixed image width for setting the scroll bars. This should work for all browsers, but I try to prevent the fixed width.
I'm no css pro. Maybe someone knows how to do that within our table design that works with all/most browsers


I released this plugin and added it to the svn to show that I'm working on such a thing.

[Αndré]

I think it has something to do with the 'table-layout' style attribute.

Problem is caused by

Code: [Select]

$template_display_media = <<<EOT
        <tr>
                <td align="center" class="display_media" nowrap="nowrap">
                        <table cellspacing="2" cellpadding="0" >
                                <tr>
                                        <td align="center" style="{SLIDESHOW_STYLE}">
                                                {IMAGE}
                                        </td>
                                </tr>
                        </table>
                </td>
            </tr>
            <tr>
                <td>
                <table width="100%" cellspacing="2" cellpadding="0" class="tableb tableb_alternate">
                                <tr>
                                        <td align="center">
                                                {ADMIN_MENU}
                                        </td>
                                </tr>
                </table>


<!-- BEGIN img_desc -->
                        <table cellpadding="0" cellspacing="0" class="tableb tableb_alternate" width="100%">
<!-- BEGIN title -->
                                <tr>
                                        <td class="tableb tableb_alternate"><h1 class="pic_title">
                                                {TITLE}
                                        </h1></td>
                                </tr>
<!-- END title -->
<!-- BEGIN caption -->
                                <tr>
                                        <td class="tableb tableb_alternate"><h2 class="pic_caption">
                                                {CAPTION}
                                        </h2></td>
                                </tr>
<!-- END caption -->
                        </table>
<!-- END img_desc -->
                </td>
        </tr>

EOT;
If I change

Code: [Select]

<table cellspacing="2" cellpadding="0" >to

Code: [Select]

<table cellspacing="2" cellpadding="0" width="100%">it works in all browsers (see my demo page).


Is the missing width attribute intended or can it be added to svn?

[Αndré]

As the table in the next table row has a width of 100%, I added the missing width attribute to the table in the first table row.

[Phill Luckhurst]

Very nice work.

[SaWey]

Maybe when you have some time to spare, you can fix the slideshows for panorama pictures

[Αndré]

Maybe when you have some time to spare, you can fix the slideshows for panorama pictures

Fixed in revision 6134 (plugin version 0.2.1).

[Joachim Müller]

Nice plugin.
Recommendation for plugins version numbering is to use only two digits, not three. I suggest to drop the usual modest leading zero that is often meant to indicate the alpha or beta stage. I suggest releasing the next version as 2.2. Just a recommendation though, you're of course free to continue using your version numbering scheme.

[Αndré]

I introduced the third digit because I often made just some small changes and released every new version on the appropriate plugin announcement thread.
This was before I had access to the svn. Maybe I can drop the third digit and re-release all my cpg1.5.x plugins when cpg1.5.x and this board becomes public.

Thanks for your hint.

[SaWey]

Nice plugin.
Recommendation for plugins version numbering is to use only two digits, not three. I suggest to drop the usual modest leading zero that is often meant to indicate the alpha or beta stage. I suggest releasing the next version as 2.2. Just a recommendation though, you're of course free to continue using your version numbering scheme.

[semi ot]
For the new plugin repo, I required 3 digits (major.minor.revision release), I thought this was the most common use of version numbering?
[/semi ot]

[Αndré]

For the new plugin repo, I required 3 digits (major.minor.revision release), I thought this was the most common use of version numbering?

IMO it's useful to have 3 digits:

• 1st - code rewrite or big changes
• 2nd - new features
• 3rd - bugfixes, typos, etc.

Of course the first digit is incremented rarely (or never ), but it should be there to have the possibility to show the users that there has been much improvements/changes or if a mod is converted to a plugin. That avoids to release a new version with a name like "Better version of foo (ng)" or "foo - the plugin version".


For the moment I will stay at a three digit version numbering.

[Joachim Müller]

From the docs: http://coppermine.svn.sourceforge.net/viewvc/coppermine/trunk/cpg1.5.x/docs/en/dev_plugin_writing.htm#plugin_writing_core_files

# $version
The version of your plugin - usually starting with 1.0 (although you're welcome to come up with any other numbering scheme as long as the difference between versions will be obvious).

Code: [Select]

$version = '1.0';

So, there is nothing mandatory, but personally I'm not fond with the modest version number scheme that many FOSS apps use that have three digits, as end users are not used to that - the more digits a version number has, the less serious users seem to take new releases. That's why I'm not fond of the version numbering scheme of cpg and suggested to drop it in favor of two-digits (similar to Ubuntu for example), which was turned down in a poll we held then (don't remember the thread out of the back of my head). Since 99% of all plugins hardly evolve that much in my eyes two digits should be enough for that as well. Three digit releases look very nerdish to end users in a world where people are used to new software versions having brand new names (think of the naming scheme that Microsoft has chosen for their top product "Windows").

[batabe]

hi André,

i've installed the latest version of the panorama viewer, but the panoramas are not shown as discriebed
http://www.balatonparty.com/displayimage.php?album=75&pid=5276#top_display_media

tried IE, Opera (win7), Firefox (linux)

if you open the links above, is it oK? or is there any issue with the 1.5.6 and panoviewer?

thanks

[Αndré]

Please disable the Lightbox plugin (and maybe others, too) and try again.

[batabe]

after disabled lightbox, the structure of site was right, just image was scrollable, but displayed imageheigt was at about 100px, so it looks now ugly, so i'm using lightbox instead

[Αndré]

image was scrollable, but displayed imageheigt was at about 100px, so it looks now ugly

Can you elaborate please (screenshot or set up a second test gallery to show the output)? Please give us the chance to improve our plugins