I don't know how much it would reduce bloat, but what about a 'photo album' item that permanently incorporates a photo into the album? Even though the photo data would still be stored in the database, we'd now have one item instead of 50.
So the only thing I'll point out here is that you can actually observe individual elements on photos. I imagine the syntax would get out of hand if you couldn't pull the photo free to inspect it more closely.
Imagine having to type "look at gun on 3rd photo of 2nd page in album"
I do like the idea. It's certainly better than a briefcase full of photos. Just needs to be implemented well.
If there's a way an album would enhance RP, it's a good @idea.
By label, I mean you would only label the photo album. Like... "Personal photographs" or "Notorious Criminals" or what have you.
1) Cameras are already photo albums.
2) Let pictures get uploaded onto the grid, boom there is your album.
Actually, maybe that's the best (and easiest to code) solution -- just creating an object that is like a camera, but instead of taking photos it scans existing photos. It can print those photos out if you need to look at details.
Call it the NitoKodak Digital Album or something.
Maybe if the in-MOO term object could be used to view an album of photos which are on the grid. A digital rather than print album does make sense, because the cameras are already digital. But I'd like an in-MOO album object which can be passed around and looked at.
I think any half-measures will just delay the much-needed paydata migration and empowerment of Grid 3.0.
