Jānis BebrītisCreditAttribution: Jānis Bebrītis commented
Status:
Active
» Postponed (maintainer needs more info)
good question, i`ve seen nested galleries used somewhere indeed. hardest part - how to implement (where to display) this feature in the way that it doesn`t confuse casual user?
What exactly do you mean with how to display? The backend (creating nested galleries) or the frontend (showing the nested galleries)? I'd like to think about it a bit more. I would need this feature to move from my selfwritten gallery, which uses image nodes but a self-made php module to display taxonomy terms as galleries, to prog_gallery.
I think sooner or later everyone needs this feature. Imagine having 100 galleries all listed _unsorted_ on the same page.
Let's discuss this. Regarding the logic, I think there are two possibilities:
b) be able to browse the galleries by taxonomy and replicate a tree structuring by attaching taxonomy terms to gallery nodes
\ there could be a page that lists only nodes of the gallery type
Concerning the front end, I think the nested galleries could either only be shown on the gallery overview, or in the gallery itself with some kind of block above or below the images.
Jānis BebrītisCreditAttribution: Jānis Bebrītis commented
The first thing I thought about was: how should it look when you add gallery. What sees the user.. eg there`s a Gallery title field now, but where should relationship manager be placed?
What would be the least complicated way to display such option to user when he creates gallery, and we have to keep in mind that this feature will be used in 10% of galleries or so.
Also - what thumbnail will be shown for this nested gallery set in "galleries" or "galleries/my" page, because I think it definately needs some.
I think the least complicated way would be a "Parent Gallery" Dropdown Box on the Gallery creation page. I will play around a bit with different display options in my sandbox.
Okay..
I'm interested in this also..
What come into my mind is that since Gallery is a node, then we could use nodereference which reference "Parent Gallery".
For the "Parent Gallery", maybe we could take a look at nodereferrer to look for the "Child Galleries". I haven't tested nodereferrer yet, it's not yet released for Drupal 6, however a patch is on the way.
Sounds logical to me. We should probably even introduce buttons on the gallery page to create a new subgallery, which will prepopulate the reference field. But as I said in #3, I think the bigger issue is the UI. Both of the possibilities I mentioned in #3 are easy to implement, perhaps even easier than using the node reference field. :)
Is there some roadmap for this module or the author opinon about priority of this issue?
I really love this gallery, but currently I am using gallery2 with drupal (really slow) and I have two top level albums:
1.) the first is album where are user's album
2.) the second top level album is Photos from our events (created by admin, it has about 100 albums inside and some of them have another subalbums)
this is the reason, why I can't move to this gallery for now, although I really want to do it.
I need to maintain the album structure what we have on our site.
it can't be done without subalbums/nested galleries.
Comments
Comment #1
Jānis Bebrītis CreditAttribution: Jānis Bebrītis commentedgood question, i`ve seen nested galleries used somewhere indeed. hardest part - how to implement (where to display) this feature in the way that it doesn`t confuse casual user?
Comment #2
Jānis Bebrītis CreditAttribution: Jānis Bebrītis commentedThis feature is postponed for brainstorming.
Comment #3
scroogie CreditAttribution: scroogie commentedWhat exactly do you mean with how to display? The backend (creating nested galleries) or the frontend (showing the nested galleries)? I'd like to think about it a bit more. I would need this feature to move from my selfwritten gallery, which uses image nodes but a self-made php module to display taxonomy terms as galleries, to prog_gallery.
I think sooner or later everyone needs this feature. Imagine having 100 galleries all listed _unsorted_ on the same page.
Let's discuss this. Regarding the logic, I think there are two possibilities:
a) model a real tree in the gallery database
\ this could be a parent / child relationship or a Nested Set (http://en.wikipedia.org/wiki/Nested_set_model)
b) be able to browse the galleries by taxonomy and replicate a tree structuring by attaching taxonomy terms to gallery nodes
\ there could be a page that lists only nodes of the gallery type
Concerning the front end, I think the nested galleries could either only be shown on the gallery overview, or in the gallery itself with some kind of block above or below the images.
Comment #4
Jānis Bebrītis CreditAttribution: Jānis Bebrītis commentedThe first thing I thought about was: how should it look when you add gallery. What sees the user.. eg there`s a Gallery title field now, but where should relationship manager be placed?
What would be the least complicated way to display such option to user when he creates gallery, and we have to keep in mind that this feature will be used in 10% of galleries or so.
Also - what thumbnail will be shown for this nested gallery set in "galleries" or "galleries/my" page, because I think it definately needs some.
Comment #5
scroogie CreditAttribution: scroogie commentedI think the least complicated way would be a "Parent Gallery" Dropdown Box on the Gallery creation page. I will play around a bit with different display options in my sandbox.
Comment #6
wuf31 CreditAttribution: wuf31 commentedOkay..
I'm interested in this also..
What come into my mind is that since Gallery is a node, then we could use nodereference which reference "Parent Gallery".
For the "Parent Gallery", maybe we could take a look at nodereferrer to look for the "Child Galleries". I haven't tested nodereferrer yet, it's not yet released for Drupal 6, however a patch is on the way.
Would like to know what others think of this :)
Comment #7
scroogie CreditAttribution: scroogie commentedSounds logical to me. We should probably even introduce buttons on the gallery page to create a new subgallery, which will prepopulate the reference field. But as I said in #3, I think the bigger issue is the UI. Both of the possibilities I mentioned in #3 are easy to implement, perhaps even easier than using the node reference field. :)
Comment #8
wuf31 CreditAttribution: wuf31 commentedHahaha.. It's just an idea.
If it can be made simpler, then let's just do so.. :)
Comment #9
igorik CreditAttribution: igorik commentedHi
Is there some roadmap for this module or the author opinon about priority of this issue?
I really love this gallery, but currently I am using gallery2 with drupal (really slow) and I have two top level albums:
1.) the first is album where are user's album
2.) the second top level album is Photos from our events (created by admin, it has about 100 albums inside and some of them have another subalbums)
this is the reason, why I can't move to this gallery for now, although I really want to do it.
I need to maintain the album structure what we have on our site.
it can't be done without subalbums/nested galleries.
Thanks for the answer and for this nice module
Igorik
http://www.somvprahe.sk