Hi,
Excellent module. Now, Im curious (and desperate) to find out, how can I add separate fields outside of title and alt? Say I wanted to add another link or load comments, how can I do that? For the life of me, there isn't a full working module that does this for Drupal 6 and 7. They all have issues, from theming issues to no fields to what not. My guess is, there is about 4 modules trying to do the same thing and are not getting anywhere, or am I wishing for too much?
Just wondering.
Kahenya
Comments
Comment #1
jamesbenison commentedI'm doing some updates on these modules now. Theoretically it is possible to make the images into links. I'll look into it. Comments can be attached to a slideshow as it stands, but I'm not sure if there would be any way to add comments to individual photos.
Comment #2
Anonymous (not verified) commentedHi,
Thanks for responding. Just wondering, is it that difficult to load extra data from a node to a view slideshow?
My Theory of this
I have 4 nodes, each with images via imagefield. Each image is then loaded via galleria. Sweet spot of this module becomes, what else can be loaded in the slide. Can we treat the stage as a stage without predefined items being loaded and even the image is optional when it comes to what is loaded on the slide on the stage. That way, its more flexible to manage and add and easier. The module gains more value then.
Just a thought.
Thanks
Comment #3
jamesbenison commentedI'm not sure if I get it. What would be displayed when there is no image?
Comment #4
Anonymous (not verified) commentedIt was a hypothetical example. Say I wanted to build a view with a list, I can add or remove any field I feel free to. Its my choice and the flexibility is there. I thought you might want to make this that flexible as well and not have predetermined fields. My reasoning is that if the fields are predetermined and someone wanted an extra option, then, they are unable to do much else. Let people have the choice to add their own fields without going code level.
Comment #5
Anonymous (not verified) commentedSorry connection troubles. :(
Comment #6
jamesbenison commentedI am considering this a feature request. I do have a lot of ideas on enhancements that can be made to the module. Galleria actually does support image links out of the box using the 'longdesc' tag. If you can get that attribute added to your images you will have links. You will need to write a little code to make that happen though.
Part of the difficulty in allowing additional fields stems from the fact that galleries can be created from a single node with a bunch of images, a collection of nodes with one image from each node, or a combination of the two. So say you want to add a caption textfield to your view. It's easy enough if you have a collection of nodes with one image from each node, because each node can have one caption. But say now you have 30 images in a node and only one caption field in the node. How would you deal with it? Would the caption go with only the first image, the fifteenth image, or would every image in the gallery utilize the same caption? We lose the one to one parity between fields and images. As it works now, since titles and captions are extracted from image attributes, we always have that one to one parity.
One way you might be able to customize this to your specific needs without writing any code is using panels and more than one view on the same page. Create a view with only a title field that has a jqfx galleria so you can edit your galleria settings. Create another view of unformatted fields that has all the fields you want to add to your galleria. Create a panel page that has both views on it. Using the 'extend' function, 'data source' and 'data selector' options in your jqfx galleria settings, you can extract whatever information you want from the unformatted fields panel on that page to customize how it gets displayed and what it does in the gallery.
For more info check out http://galleria.aino.se/docs/1.2/
This project is not official despite being available for six months. While I have a lot of ideas on things that can improve the module, I'm reluctant to go crazy adding a lot of complex new features until I know that this module isn't going to just die in a sandbox.
Comment #7
jamesbenison commentedGiven that this project is official, I will be moving forward with additional features.
Features will be added gradually. There is much that I would like to do. First priority is working toward having stable release versions.
Comment #8
Anonymous (not verified) commentedThanks. Looking forward to this.
Comment #9
jamesbenison commentedThis has proven to be a bit of an undertaking. Much of it is working, but it still has a ways to go. I had to write the preprocess function to use raw views data instead of the views row plugin in order for the module to properly map the correct fields to their images depending on whether images came from fields in one entity or multiple entities. The other option would have been to write a new views row plugin, but that would have been too complicate for users IMO.
Currently it's possible to map image fields as the images. Regular and html captions can have node titles, node bodies, and fields that utilize the core fields api mapped to them. I have an html captions demo up here.
Adding links to the images requires the image longdesc attribute. The core image module only allows alt, title, width, and height. That means creating a new field formatter. Unfortunately, I haven't had luck coding new image formatters into the jQFX modules. It only seems to work when I create a new field type in a separate module (like Link Image Fields) and using its formatter for the slide images. Unfortunately that creates another module dependency. That might prove to be the best solution though. Galleria would still be able to use any image field mapped to the gallery, not just that field type.
If anyone has any suggestions/comments/criticisms please chime in.
Comment #10
Anonymous (not verified) commentedWow, just saw it and its impressive. As it is, with HTML layer, that works for me very well. It basically covers exactly what I had imagined. I can't quite imagine needing anything else so far. Possibly you want to share some code so that I can help with testing?
Comment #11
jamesbenison commentedThe demo is from the dev version.
You are best off testing the dev version in a fresh install. It's not totally stable and it doesn't update very cleanly from alpha-1 yet. Also, some of the code is fugly and needs an overhaul.
Thanks
Comment #12
Anonymous (not verified) commentedHi,
Will do. Im away on a clients job, should be able to test it by end of the week.
:)
Comment #13
shawn dearmond commentedJust wondering, would you be able to just use Media display types? It includes any and all fields that I would want to add to each image.
Comment #14
jamesbenison commentedI haven't tested it with media types yet. It works with any field that has the field_ namespace. I got as far as adding media to a dev platform but then got sidetracked. If it doesn't work with media now I will get it fixed, but it might not be 'till later this week.
Comment #15
shawn dearmond commentedIt works with media as the images, but I have extra fields on the media type (caption, shutter speed, aperture, iso, date, etc.) that I would like to be displayed on the galleria display, and/or on the lightbox pop-up.
Comment #16
jamesbenison commentedI'll fix it. This week has deadlines looming and it might be a couple days. I have a ton to catch up on.
Thanks for testing.
Comment #17
rv0 commentedNice to see this module is going forward, keep up the good work!
Tested this today, I couldn't seem to get the "body" field in place for the description.
Anyone else got this?
Comment #18
jamesbenison commentedThanks for the heads up on that. I'm not sure why it would be okay for the title and not the body, but I'll definitely check it out.
The field mapping is still pretty early and crude. I'm burning the candle at both ends and hope I can get to it this weekend.
Comment #19
mgifford