Kat wrote:What i tried achieve in the panel - did in firebug :
Yup. That would of course require us to have multiple CONTEXT modules available to create/edit from the panel, which could easily get frustrating for any user (context1, context2, context3 etc?) . Furthermore, CONTEXT is not the same as CONTENT ... Content is the main custom content/html element INSIDE context, which also includes optional elements like title, description, date, images_amount, folders_amount etc. It makes sense to stack these items into the CONTEXT module, as in 99.99% of cases, you want these elements grouped together anyway ... You can set order if items within the context-module, from the context tab.
If anything, we would likely just add a setting to the gallery module
[content after gallery], which would be a basic input field for any html.
Kat wrote:Just thinking... calling the gallery module first in this way ?
Not sure about this ... You are aware that you can already SORT the order of elements in MODULES, so for example to call the gallery before context? Also, as mentioned, context is not the same as content so it's easier said than done to just imagine "injecting" the gallery module in the middle of "content".
Also, not sure why you would add html for pagination like that? If added, it will for sure be a programmatic feature with settings in the gallery module. Not sure what X3 should do with what you add to the html anyway. Amount of pages will depend on the device, layout and total amount.
Kat wrote:This is why, among others content, i wanted add a context module after gallery and one can decide when to split they gallery.
How you gonna decide "when" to split the gallery? You want to see X for amount of images before pagination appears? Of course, that means you have no control if a gallery row will just stop in the middle of a row or not. Also, I am not sure what adding a context module AFTER gallery has to do with pagination. Even if context module is BEFORE the gallery, the pagination would always appear AFTER the gallery. Pagination would also NOT be set from your CONTENT ... How is that supposed to work? Pagination is a complex feature function, where the page links will need to be calculated and rendered based on the all the variables (max_amount, layout, device, total_amount) ... and the links obviously need advanced behavior to inject a new "batch" of images when they click a page.
Actually, I am strongly opposed to "pages", and I believe I expressed this view earlier. Why not use some infinite scroll method, or [Load More] button, both which simply APPEND more images below the current scroll point? This is how all top image services work (for example google, flickr, pinterest, instagram etc). Furthermore, what will a page-link in pagination link to? yourdomain.com/gallery/page2/ etc? No visitor and no SEO will have any benefits from that.
Kat wrote:It would be the same principe as the top Nav which allows to navigate between pages.
Not quite sure what you are referring to here in top nav, or how that would be similar to any page nav. You mean the carousel?
Anyway, thanks for feedback!