hi all
i hope i post this in the right place.
in the last weeks i was working on an improvement of the ssp module.
the key features are:
1. ssp and views integration without hooking the view specifically for ssp - now you just need to check a checkbox to make the view produce an xmk file (and you still get the page and block view). i did it using the menu system instead of the view plugin.
2. you can upload your own presets for the ssp theme as an ssp xml param file. meaning you can manipulate the look and feel of ssp from outside using drupal in an imagecache like gui.
3. integration with imagecache - you can manipulate the images showing on ssp .
4. integration of multiple views as albums + other ssp xml files from other sources using the ssp opml option.
im uploading the files without the fla and the swf (due to legal issues).
please let me know if there is an interest from the part of the community so i can join forces with the maintainer (Alex - i tried to email you but i guess my email never got to you).
im using this module on some of the projects the company i work for develop.
I hope that in the near future ill have a showcase site.
Comments
Comment #1
liorkesos commentedHi,
I'd like to emphasize the importance of this ..
Gavri has been doing a great job in making this a great resource for our internal projects.
And after an initial version has been released he rewrote it to be modeled much more in the direction this module was intially structured.
Our version has imagecache support and we want to continue towards views2 integration and additiona ideas we have.
We really don't want to split this and create another module so please see if we can collaborate here.
I'd be happy if Gavri could co-maintain the module for the greater goods of all companies using this as another great drupal building block and also for the greater good of the community.
best regards
Lior
Comment #2
avolve commentedI am not sure when the last changes were made by the original contributor. As someone who has fully tested the original module, i am interested in the proposed changes.
Comment #3
alex_b commentedI had a quick look. It's very hard to accept whole sale changes. Things would have to come patch by patch. That said, Drupal 5 is over and I am very reluctant to accept big changes to SSP. Also for you guys the return on contributing back (which is a lot of work) will be very low, as most people have moved on to D6 and reviews and additions for D5 will be sparse.
I'd recommend keeping an internal fork of SSP for D5 and/or getting involved for SSP in D6 - #300810: Drupal 6 port
Aside from that, the code in the zip file does not comply with Drupal coding standards - http://drupal.org/coding-standards
Comment #4
alex_b commentedClosed for inactivity.
Comment #5
chrislabeard commentedinteresting