## page was renamed from ImageGallery Include better support for managing Images within MoinMoin. We already have: * Attachments * Links to images * Links to attached images Possible new features * Thumbnails * Descriptions * Navigation Avoid * Pages with lots of images on it = Current Implementations = [[MacroMarket/Gallery]] * uses the attachments directory * views: thumbnails, webnails, original * simple annotation and navigation * rotate Thanks to those who have contributed to this page. I have used ideas from here and from AdamShand in the building of this macro. - SimonRyan [[MacroMarket/ImageLink]] [[ParserMarket/Gallery2]] = Other Implementation ideas = == Gallery Processor == * simple language ("imagename: description") * shows table with thumbnails * thumbnails are automatically created and attached to the page. * shows upload link if image is not present * thumbnails are * links to the images (simple solution) * links to image navigation actions * navigation * action that gets text as form parameter * next, previous, up ---- Perhaps this could just be an macro. It uses the *Gallery page as a source of information and caches the parsed data (as with *Dict pages). Markup yould be a bit more complex: {{{ * IMAGENAME: short Title Text for this image up to the next * IMAGENAME: another title More descriptions }}} The ImageGallery macro would display a specified set of the gallery as thumbnails (+ titles) and navigation controls (prev/next) as seen with MonthCalendar macro. Clicking on an image brings up the full scale version of the picture and all information for this picture plus navigation controls (prev/next/overview). Parameters are passed via the query string, as it is done with MonthCalendar. The macro autogenerates thumbs for pics that have none. Thumb size could be either given as dict on the *Gallery page or as parameter of the macro. -- OliverGraf <> I generally don't like this "magic pages" idea. But we already have two (Categories and Groups) so that anotherone wouldn't do much damage. But I don't understand why we need a second page. This case is exactly what processors were made for. -- FlorianFesti <> So instead of a magic page plus a macro to display it on another page, one would just embed the gallery part into his page using a special hash-bang to call the gallery processor? Should work the same way. I have a feeling the the magic page way is a bit more flexible when it comes to reuseability of photos, but I don't have a good example where this would be of any advantage (will the processor make trouble with cached pages?). -- OliverGraf <> You can use the Include macro if you want to use the galery multiple times. Caching is not a problem as every macro, processor, ... can deside itself if it wants to be cached or not. -- FlorianFesti <> {{{#!wiki blue/dotted Currently we do refactor all the Gallery2 staff http://hg.moinmo.in/moin/1.7-extensions/ for 1.7. The new name of the project is arnica. I have decided to change the Gallery2 name because the old name confused many users. -- ReimarBauer <> }}} ---- CategoryFeatureRequest