plg wrote:

* by default the click on the zoom icon open the HD 1:1, I think it's better to open it "fit to screen" by default, see [Forum, topic 17727] usability: lightbox picture size sequence

In fact, I think it's a config paramater in gally themes. You havec the choice between fit and zoom.
It should be a config option in stripped too, but it's not...

The "fit to screen" first and only then "HD 1:1" makes more sense.
(it's just not what I need but I use HD pictures in a very specific way (only for panoramic images))



For the "5mb" file, it really depends on the size of the HD picture... it's possible to have good quality hd pictures with a limited filesize.

Zaphod wrote:

In fact, I think it's a config paramater in gally themes. You havec the choice between fit and zoom.

Yes, you're right. Then I think the default option should be "fit on screen".
Default zoom size
This option sets the display type used by default when a high definition image is loaded

[✔] Actual size (if image doesn't fit on the screen, it's possible to scroll horizontally and vertically)
[] The image is resized to be fully displayed on the screen

flop25 wrote:

you were talking about fitting or not the hd first, but an user had a better idea used by many cms and gallery for "less advanced" users : having different size of the same image (see [Forum, post 122819 by nicksan in topic 17693] Piwigo thoughts after a few weeks...)
We can implement it with a php page for resizing by Get arguments (including a token), and a menu with links to some sizes (auto or/and set by the admin, and also to the original size)

I consider the "multisize" feature as another subject. A far more complex subject actually. rvelices had told me he would like to work on it.

I agree that multisize would be great in the future, but in the nearer future, let's consider we just have thumbnail/websize/HD :-)

flop25 wrote:

well you know I love science fiction ^^

No, it's not SciFi. Piwigo will implement this feature I hope. Maybe not for version 2.3 (depending on rvelices availability and problems he may encounter while implementing it) but maybe for 2.4 !

plg wrote:

grum, do you see any technical problem for implementing it in core themes?

From a technical point of view, I don't see any problem to implement this kind of features in the core.
To implement something like this, you just have to use some javascript and apply few modifications on templates&css files.

The only problem are:
- with IE6, you have more chance to hang up, but I think we can consider that we don't have to do effort to provide a default template working with IE6 (even if this browser is always used in big compagnies like banks, Microsoft officialy recommand not to use anymore IE6 ; we can see other website's like Facebook or Google mail, in the same way, they don't support it anymore).
- for some themes based on default template but having specific .tpl files or javascript, it's not garanted that after upgrading the default theme they'll work again



After, I'm not sure to understand very what you're meaning by "do you see any technical problem for implementing it in core themes".
Are you thinking about an implementation of the Gally's JS in the core ?
As it, it's not possible because the Gally's JS file (in this case, the gallyjs-tpp.js file) provide functions for many Gally's features and depends of the Gally's config file.
But everything is coded in separate functions, so I think it'll be not very difficult to get and modify the Gally's JS for the default piwigo template  (zaphod did it for the stripped theme, based on the default piwigo template so it'll be probably easier to start from stripped's JS).