Hi Piwigo Community,
I often hear about the "not so perfect" layout of photo informations on the "picture.php" page. I'm talking about that:
This afternoon, I made some test to improve this default display (for core themes I mean: Sylvia, clear, dark). Themes like Simple* or Gally* are not concerned because they alerady have a much better layout for photo informations, in my opinion.
So here is my test:
when you click on "Show information", it then displays:
What's your opinion about it?
Offline
I'm still working on photo information. I have designed a block with tabs. Inspired by Gally* themes.
Offline
Inspired by Gally* themes.
this looks great
Offline
What disturbs me, it is that one must choose to post EITHER information, OR comments.
Personally, I will like to see posted two blocs…
Offline
how to do??i want to show the imfomation like you
Offline
ooooo wrote:
how to do??i want to show the imfomation like you
Work in progress for a futur version of Piwigo.
Offline
Gotcha wrote:
What disturbs me, it is that one must choose to post EITHER information, OR comments.
Personally, I will like to see posted two blocs…
+1
The new proposed designs are nice, but if the second one is chosen, it would be nice to be able to select whether comments are displayed in a tab or below the image properties.
But, that should normally then be an improvement of [extension by gbo] Look_like_Gbo 2.
Anyway it's a nice project :-)
Offline
It must read noël and and noêl. :-)
Offline
Gotcha wrote:
What disturbs me, it is that one must choose to post EITHER information, OR comments
I like the fact that it doesn't show too many information at the same time.
What's important when you post a comment is previous comments, don't you think? then do you really need to read photo informations when you're writing your comment?
Offline
plg wrote:
What's important when you post a comment is previous comments, don't you think? then do you really need to read photo informations when you're writing your comment?
+1
About this new feature, in the next release of Gally (1.3.2) I have implemented something to be abble to display some raw informations in the tabs, allowing to display something like this (cf. picture).
For the plugin AdvancedMetadata, I inject data into the {$metadata} variable, using the metadata structure to displlay info (it works and it looks like piwigo)
For the plugin GMaps (you don't know it because it is not yet published) I inject some special values in the structure of the {$metadata} variable, and add an ugly thing into the template :
{if isset($metadata)} {foreach from=$metadata item=meta key=id} <div id="imageMeta{$id}" class="imageMeta tabPanel"> <div id="imageMetaContainer{$id}"> <div class="imageMetaBg"> </div> {if count($meta.lines)>0 and !array_key_exists('<!--rawContent-->', $meta.lines)} <===== Ugly trick : testing what is in the structure <table id="displaymeta{$id}" class="displaymeta infoTable"> <===== If classic, using classic display {foreach from=$meta.lines item=value key=label name=metaloop} {if ($smarty.foreach.metaloop.iteration-1) % #metaNumCols# == 0} {if !$smarty.foreach.metaloop.first}</tr>{/if} {if !$smarty.foreach.metaloop.last}<tr>{/if} {/if} <td class="label">{$label|@translate}</td> <td class="value">{$value}</td> {/foreach} </table> {else} <===== else if the label equals "<!--rawContent-->" {assign var='empty' value='<!--rawContent-->'} <===== just display data as raw content {$meta.lines.$empty} {/if} </div> </div> <!-- imageMeta --> {/foreach} {/if}
It would be a good thing if in your improvment, you can think about a clean system allowing to do something like this...
:-D
Offline
plg wrote:
Gotcha wrote:
What disturbs me, it is that one must choose to post EITHER information, OR comments
I like the fact that it doesn't show too many information at the same time.
What's important when you post a comment is previous comments, don't you think? then do you really need to read photo informations when you're writing your comment?
YES I need !
1- See "casual people" : they will not see/understand the tabs. they will only scroll and see the info displayed first. So it's not user friendly
2- ALL the people scroll and read the first info displayed, in order to judge the quality/relevance of the page/photo
The blog, the social site and many many site are made on the same template : the comments are under the content to comment and the info on the right or just under the content also ; deviant art ( http://flop25.deviantart.com/#/d2969kb ), flickr (they just have a new structure http://www.flickr.com/photos/journaldugeek/4620624471/ ) .... So a click just to see the comments and one more to see the info without seeing the comments at the same time, we obtain finally a lot of limitation/restriction.
what I suggest : a "show more info" (no show all) -maybe on a menu on one side- and in the admin part, a page to manage what will be displayed, because the use of piwigo are numerous and a photograph will want lot's of info whereas a family wants only few info. Remember that we have many post on the forum about "how hide/showing that" and "In case of conflict, consider users over authors over implementors over specifiers over theoretical purity." ;)
Offline
flop25 wrote:
plg wrote:
I like the fact that it doesn't show too many information at the same time.
What's important when you post a comment is previous comments, don't you think? then do you really need to read photo informations when you're writing your comment?YES I need !
1- See "casual people" : they will not see/understand the tabs. they will only scroll and see the info displayed first. So it's not user friendly
2- ALL the people scroll and read the first info displayed, in order to judge the quality/relevance of the page/photo
+1
flop25 wrote:
what I suggest : (...) in the admin part, a page to manage what will be displayed, because the use of piwigo are numerous and a photograph will want lot's of info whereas a family wants only few info. Remember that we have many post on the forum about "how hide/showing that" and "In case of conflict, consider users over authors over implementors over specifiers over theoretical purity." ;)
+1
Offline