Posted: Fri May 30, 2008 3:50 pm Post subject: Status of next integration version
This is going to be a ramble, but here goes...
New features for the next version include:
A. New image selector. Written from the ground up as a phpBB mod, instead of a universal 3rd party CMS addon like Kirk's image chooser.
new g2image preview [nukedgallery.net]
B. Users have control via the UCP over their own gallery link and profile settings including selecting which images will show in their profiles, if any. Governed by the ACP settings, of course.
C. UCP avatar selection from images within Gallery, if ACP settings allow.
UCP preview [nukedgallery.net]
I thought I was nearing the end for this next version, except for a lingering issue with mooTree and the task of getting some of the integration pages to validate as xhtml 1.0 strict (phpBB mod requirement). BTW, is it just my particular installation or has anyone else noticed that the majority of the Gallery pages, even in stand-alone mode, do not validate? (I'm testing with the matrix theme and the typical download of 2.2.4)
http://validator.w3.org/ [w3.org]
The issue with mooTree is the biggest hangup right now and I can't seem to make it work the way I think it should. Everything works except the last node of a tree branch. When the tree is expanded and the last album of a branch is clicked, the script works and the items are displayed, but the tree collapses to the next higher parent node instead of staying in the album that was selected. I've tried everything I can think of, read the documentation a dozen times and am pretty much ready to give up on it at this point. I suspect it is geared more towards AJAX mode than the way I am trying to use it to simply generate a tree of gallery albums, though it mostly works this way. I don't really want to get into AJAX because, a. I know practically nothing about it, b. Seems to me it would need to work from a framed page which is not the way any phpBB3 pages are written, and c. I don't really want to have to dynamically generate xml data streams from the integration.
This is related to the new image selector mostly, but also to what version/type of lightbox will be used.
The reason for mooTree stems from my decision to use slimbox instead of lightbox and slimbox uses the mooTools js framework, so I thought it made sense to use mooTree instead of dTree that Kirk was using, and it required fewer files and would be more of a departure from Kirk's code.
So here are the options/choices as I see them at this point. Feel free to respond if you have an opinion!
1. Stick with slimbox, forget mooTree and go back to dTree, which I had working at one point.
2. Go back to the original lightbox and dTree. (Don't know why. Slimbox is a drop-in replacement for lightbox, requires fewer and smaller files.)
3. Forget lightbox, slimbox, dTree, mooTree, mooTools and use the YUI js framework.
I've just discovered in the past couple days that the YUI js framework also has the capability to do all this. I've already used this in the UCP profile gallery settings page to show tooltips so that users can see what the settings do. Actually stole the idea from gallery itself. If you've ever hovered over the themes in the gallery admin page, you know it shows a tooltip of what the theme looks like.
I guess I'm leaning toward option 3 at this point since gallery already ships with some of the YUI library. Gallery 2.2.4 does not have all the required YUI files, but Gallery 2.3 is going to have all of them that would be needed. There is always the possibilty I may run into a roadblock with the YUI framework as well, but on the surface it looks like it will work. The drawbacks to this one are, larger served files because the YUI files are fairly large compared to mooTools, but maybe similar to the scriptaculous files used by the original lightbox; and a lot more work for me. I guess we could always go back to option 1 if all else fails.
Posted: Sun Jun 01, 2008 3:33 pm Post subject: Re: Status of next integration version
Ok, figured out the problem with mooTree after all. I was incorrectly assuming it was smarter than it apparently is. I was assuming if I wanted a node open that it would open the tree from the root to that node, but no, it happily opens the node and then buries it in a collapsed tree. I don't remember dTree doing that unless I didn't play with it enough. I thought it was smart enough to know if you wanted a child node open, it would have to open the parent nodes from the root to that node.
Anyways, I just had to build a breadcrumb array from the root through the descendent nodes all the way to the desired child node and specifically set them to open status and it all works now.
Still might give the YUI stuff a try, but can put that aside for awhile.
Also, anyone interested in the lightbox and image effects listed above might find this site of interest - everything is done with css...
http://www.cssplay.co.uk/ [cssplay.co.uk]
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
Forum FAQ
Statistics
Search
Usergroups
I guess we could always go back to option 1 if all else fails.
