🌍
English
Announcement
- [2025-03-12] Piwigo 15.5.0 : batch manager gets more stable
- [2025-02-21] Piwigo 15.4.0 : SEO improved, load reduced, bugs fixed
- [2024-12-20] Piwigo 15.3.0 : same as 15.2.0 but compatible with PHP 7
- [2024-12-19] Piwigo 15.2.0 : better user activation and many fixes
- [2024-11-11] Piwigo 15.1.0 : small fixes and what's new popup
#1 2015-03-11 20:47:02
- Serge D
- Member
- US
- 2014-07-15
- 385
[CORE FEATURE] Handling of picture metadata and template embedding
Hi
I want to open discussion on the following
today PWG relies on the picture.tpl to create/manage picture metadata like description, EXIF, tags, comments, etc
problem is that content is hardcoded into template and any extensions to add new tabs from any plugin would constitute parsing of page template content prior to rendering and injecting custom smarty code.
because theme could introduce its own layout and how metadata content is organized, there is no unified way to find place for injection of new content and or format of metadata tab content
I did play around and actually implemented within my theme an event driven model where plugin developers can register their own handlers and then add specially formatted content which in turn would allow theme to build tabs based on this information at the time of the rendering.
Also this method allows to create special PWG admin area where user can show/hide tabs. While I do not have implementation for that specifically, it is easy logical extension
it is not necessarily a model WordPress is using to manage plugins on their end, but it is close
would you be interested in making this approach common and available in the core?
Please note that this approach backward compatibility as it does not preclude plugin developers from using previous "prefilter" method
Last edited by Serge D (2015-03-11 20:50:59)
Offline
#2 2015-03-11 22:01:52
- flop25
- Piwigo Team
- 2006-07-06
- 7037
Re: [CORE FEATURE] Handling of picture metadata and template embedding
Serge D wrote:
Hi
I want to open discussion on the following
hi
always a pleasure to discuss on such thing
Serge D wrote:
problem is that content is hardcoded into template and any extensions to add new tabs from any plugin would constitute parsing of page template content prior to rendering and injecting custom smarty code.
because theme could introduce its own layout and how metadata content is organized, there is no unified way to find place for injection of new content and or format of metadata tab content
the core information of a picture is hardcoded but for metadata that's http://piwigo.org/dev/browser/trunk/the … e.tpl#L310 so such general label/value that any theme can customize
the rest of the message suggest that you want something like the menu with blocks of metadata?
To get a better help : Politeness like Hello-A link-Your past actions precisely described
Check my extensions : more than 30 available
who I am and what I do : http://fr.gravatar.com/flop25
My gallery : an illustration of how to integrate Piwigo in your website
Offline
#3 2015-03-11 23:33:31
- Serge D
- Member
- US
- 2014-07-15
- 385
Re: [CORE FEATURE] Handling of picture metadata and template embedding
flop25 wrote:
the core information of a picture is hardcoded but for metadata that's http://piwigo.org/dev/browser/trunk/the … e.tpl#L310 so such general label/value that any theme can customize
theme can customize content of existing tab and use internal variables like $INFO_AUTHOR, $INFO_POSTED_DATE, $rating.USER_RATE, ...
but this is exactly a problem. There is so much stuff around it and format is not unified.
ideally content should be simply some sort of <div> element with content inside.
then format of container could be changed without affecting the content of the tab.
but more importantly, there is no unified boxing model for tabs and navigation between
possible solution is to define each tab as some sort of template with metadata describing ID, Sort Order, placement target (could be used to place tab content in various areas of the theme layout), Title, content in form of some structure and aggregated as collection
then theme takes this collection, enumerates, and construct metadata content layout to match the theme.
3rd party plugin simply adds to collection when new metadata content is published
Also it would be now easier to add extra information to specific tab, because it structure is well defined.
as I said earlier expanding existing collection could be done traversing registered events with trigger_change
flop25 wrote:
the rest of the message suggest that you want something like the menu with blocks of metadata?
yes, this is correct
I call it tabs, because it is easier to visualize, but the same collection could be used in menu, side bars, header and footer of the layout
Offline