38 replies to this topic

[Jυra]

Seems very complex and I never had a use for it.

[Noni]

I'm not marching for subalbums necessarily but a way to filter images through the main album.

Subalbums was a suggestions that is already in place
Filters / Filtering (...with mass tagging) is another one which could easily replace subalbums.

[Rimi]

I'm not marching for subalbums necessarily but a way to filter images through the main album.

Subalbums was a suggestions that is already in place
Filters / Filtering (...with mass tagging) is another one which could replace subalbums.

Maybe custom fields for images?

I heard that was a feature in IPG 3.

[Noni]

Anyhow, anyway... there has to be a solution... otherwise, 500 pictures (why not, even 100) in an album won't make any sense without being able to filter them based on some keywords that can be mass added to pictures without hundreds of clicks and scrolling through infinitely long pages such as the ones you get when reviewing the images in an album - this is also annoying, by the way.

Description, copyright and other fields should be visible only if i want them to, because 99.9% of the time any member (including me) just scrolls down to the bottom of the page to click approve and make visible.

[joelle]

I don't have 1000 albums with or without subalbums, nor the majority of us i believe.. And for the handful of communities that do have, you should make a notice and let the admin choose what to do.

Well, my board has over 3100 albums. So I guess that the restrictions make sense even though I don't like the idea.

[Noni]

Well, my board has over 3100 albums. So I guess that the restrictions make sense even though I don't like the idea.

I've just looked over my stats.. i have 812 albums. With 3100 albums, did you notice any problems with the loading of the albums?

I have to mention that from 800 albums, maybe 25-30 albums in my community have subalbums, but these albums are the best motorcycle trips and experiences described. Merging each one of them in one album will make them less user-friendly, less explicit, less attractive to browse (they also have lots of images)

[joelle]

I've just looked over my stats.. i have 812 albums. With 3100 albums, did you notice any problems with the loading of the albums?

Every once in a while I get a white screen. And sometimes it says that you are not allowed to view the image even though the correct permissions have been applied.

[bfarber]

Imagine trying to build a dropdown list "where to move this image to"? That's the initial reason for the more robust album selector tool in current versions of Gallery FYI.

Noni - just to be clear, the upgrader will not merge your albums. It would, however, move a subalbum to the nearest category, which may similarly be confusing (however hopefully not as "destructive" as merging albums).

[Cyrem]

Imagine trying to build a dropdown list "where to move this image to"?

You type their username, then select the album. I don't see an issue?

[Marcher Technologies]

You type their username, then select the album. I don't see an issue?

You don't see an issue only because you look at it from the admin unrestricted level with no deep nesting... the ability for the user to perform the action(any, including viewing) with any one of those albums must be checked, when you have to build the entire tree to do that it is not pretty.... it is an issue because users make these containers, and no matter how few you allow them to make, it stacks up quickly.
You have quite obviously not seen the result of 2k+ forums with complicated nesting on the forum index... that is not pretty either... hence the limitation to the user albums and the pagination of the categories.
IPS seeks to make Gallery scale well, so the things joelle and others encounter do not occur.

[Noni]

Imagine trying to build a dropdown list "where to move this image to"? That's the initial reason for the more robust album selector tool in current versions of Gallery FYI.

Noni - just to be clear, the upgrader will not merge your albums. It would, however, move a subalbum to the nearest category, which may similarly be confusing (however hopefully not as "destructive" as merging albums).

Let me see if i get it clear..
I have a global category in which a member has an album with subalbums

Those subalbums from the members album are moved to the main category? This is not a good approach either in my case. I'd rather move all the images from the subalbums in the members album.

Although... i'm still hoping you will find a way of sorting - filtering through images.

[kotaco]

Other sites seem to be able to pull it off, maybe because they're built like galleries and not forums. Im not a coder, I don't know

[bfarber]

Other sites seem to be able to pull it off, maybe because they're built like galleries and not forums. Im not a coder, I don't know

In actuality, I don't think I've used too many Galleries that allow "sub albums". Most online galleries I've ever used allow you to create an album or an image set, but not create any sort of hierarchal structure to associate multiple sets together.

[ZakRhyno]

In actuality, I don't think I've used too many Galleries that allow "sub albums". Most online galleries I've ever used allow you to create an album or an image set, but not create any sort of hierarchal structure to associate multiple sets together.

Will that fix that so many albums running down the right side of the current gallery?

[Rimi]

I can't think of any galleries that do albums within albums within albums.

Incidentally, that kind of structure is exactly how forums work...

[ZakRhyno]

Maybe one level down not a lot of level down will work.

[Feld0]

I can't think of any galleries that do albums within albums within albums.

Incidentally, that kind of structure is exactly how forums work...

Menalto Gallery allows you to create an unlimited hierarchy of subalbums, features a very slick interface, and has a design that really brings out the images and videos you upload into it. I've seen it and its precursor, Gallery2, in some impressively large deployments; so however it works its magic, it somehow does scale up while retaining a fairly robust feature set.

It is actually my favourite gallery software, but doesn't exactly integrate with IP.Board which makes it rather impractical. The feature list is pretty impressive and there is a great selection of community-contributed modules that add or extend its functionality. You can see a live installation in action on the creator's website, although half the good stuff appears once you log in.

It's worth checking out for some inspiration, as it is an established and rather well-liked project with great UI/UX and functionality alike. IP.Gallery could certainly learn a few lessons from them.

[Rimi]

All I learned from that is that I now highly dislike huge hierarchies since if I'm coming to a gallery for the first time and want to browse a bunch of images at once I actually can't do that since I can only browse album by album...although IP.Gallery overcomes this because currently it includes pictures from sub albums on the global albums page doesn't it?

Well ignoring me and my digressions...I see that this is definitely possible then huh? Look at how perfect the URLs are too. That's the type of URLs I'd love to see in IP.Gallery. Hmmm, really cool. I'm curious to know if they've actually implemented a very clever way of sorting out hierarchies or if they're just ignoring the issues that IPS is avoiding.

[bfarber]

Will that fix that so many albums running down the right side of the current gallery?

The homepage layout is different, so that's irrelevant now.

Menalto Gallery allows you to create an unlimited hierarchy of subalbums, features a very slick interface, and has a design that really brings out the images and videos you upload into it. I've seen it and its precursor, Gallery2, in some impressively large deployments; so however it works its magic, it somehow does scale up while retaining a fairly robust feature set.

It is actually my favourite gallery software, but doesn't exactly integrate with IP.Board which makes it rather impractical. The feature list is pretty impressive and there is a great selection of community-contributed modules that add or extend its functionality. You can see a live installation in action on the creator's website, although half the good stuff appears once you log in.

It's worth checking out for some inspiration, as it is an established and rather well-liked project with great UI/UX and functionality alike. IP.Gallery could certainly learn a few lessons from them.

All I learned from that is that I now highly dislike huge hierarchies since if I'm coming to a gallery for the first time and want to browse a bunch of images at once I actually can't do that since I can only browse album by album...although IP.Gallery overcomes this because currently it includes pictures from sub albums on the global albums page doesn't it?

Well ignoring me and my digressions...I see that this is definitely possible then huh? Look at how perfect the URLs are too. That's the type of URLs I'd love to see in IP.Gallery. Hmmm, really cool. I'm curious to know if they've actually implemented a very clever way of sorting out hierarchies or if they're just ignoring the issues that IPS is avoiding.

I don't think anyone said it can't be done. What we said is it doesn't scale well with user-contributed content. IP.Board allows forums, inside forums, inside forums, and so on. It's not technologically impossible to support nested hierarchies.

The problem with Gallery is that USERS come to the site and create albums. Over the course of a year or two, you could end up with tens of thousands of albums, and building a proper tree to reflect this is resource-intensive. Certain techniques try to work around this (e.g. the node-tree approach attempted with Gallery 4), however the approach was imperfect in practice.

I'm going to bow out of this conversation. I simply wanted to be clear and upfront from the start.