Thanks for contributing a new module -- It looks attractive in your screenshots.
There are already almost 40 javascript slider/scrolling modules in Drupal contrib. Some of those have been contrasted at http://drupal.org/node/418616 . It would be great if you could add a comparison of your module to that page and to the project page to help people understand why they might want to use it.
I would also encourage you to consider whether your attractive style here can be implemented as a plugin or style for an existing slider module.
Thanks!
Comments
Comment #1
vm commentedthe screenshot is similar to the one used for http://drupal.org/project/scrollable
That said, what is the differences between this module and the module linked above?
Comment #2
ezra-g commentedOne difference is that scrollable can use Views as the source of content in the display, while this module seems to be limited to content of one or more configured types (implementable with Views).
Comment #3
vm commentedgotcha. That makes sense. Thanks.
Comment #4
ezra-g commentedJust a note to say that I'm not the maintainer or author so I was just offering that as an observation ;).
Comment #5
vm commentedno worries ezra-g, I knew that.
Based on the minimal description it's difficult to understand what scrollable_content does that scrollable can't do even though scrollable uses views and filters. Obviously the best way for me to figure that out in total is to install this module in my sandbox and compare the two.
Comment #6
good_man commentedOhh I didn't expect such a quick response!
Okay I've examined most of the modules out there and I didn't find the features I was looking for:
1- Can use a content type or a taxonomy and can also work with Imagecache (the last point is very important for me).
2- Can reduce duplicates in a simple way.
3- Can be displayed as a block.
4- Uses the cool sliding and scrolling capabilities and effects of jQuery Tools Scrollable.
I'm still working on it and my current main goal is to make the code as clean and optimized as possible, after that I'll put it under extensive testing and after that I'll release a stable release, write a full description, compare it with other sliders and a project node for it.
Thanks ezra-g your point is right, the other module (Scrollable) can just be displayed in Views, while mine can be displayed as a block.
Comment #7
ezra-g commentedThanks for your response, @good_man. In response to your points:
1-3: can be implemented with Views
4: can be implemented with Scrollable, which supports Views.
Therefore, it seems like this module duplicates functionality provided by Scrollable. It seems like your hard work would be better spent collaborating with the author of Scrollable.module.
Comment #8
dave reidI agree with ezra-g. This is a very clear case of where cooperation is going to be better than duplication. Especially in an already crowded field. Would you please consider merging your project with Scollable and helping that project instead of continuing yours?
Comment #9
good_man commentedOh I see your point, unfortunately when I start developing it I called it just "Scrollable" and when I wanted to publish it I noticed that a new module called Scrollable just came out (at the time when I start it didn't exist), so I just called mine "Scrollable Content". And another issue I did contact the author of Scrollable cptnCauliflower, to make it into one awesome module but he didn't reply! when you see his Open Issues you got an idea that he wrote it and left ;) (just kidding) if you have any other way than the site's contact form or the issue tracker to reach him, tell me so we can rearrange the whole situation.
Comment #10
Ela commentedHi! I think it's great, since you do not have to have Views to use it.. I believe to use "Scrollable" you need to have views? :) Anyway.. I'm going to give this a try.. Thanks! :)
Comment #11
BenK commentedSubscribing...
Comment #12
kaakuu commentedSubscribing
Comment #13
good_man commentedHi BenK and kaakuu, there are a lot of talking in this issue, what are the things you are subscribing for?
Comment #14
ppblaauw commentedFound this issue because I had an issue in the issue queue of the ddblock module (http://drupal.org/node/731384) where is asked if the ddblock module can do functionality which is better supported by a carousel/scroller module.
I use the scrollable javascript plugin with the ddblock module and views_slideshow_ddblock module (dev versions).
Why I am reacting is that I also tried to work together with other slideshow maintainers and did not get any reaction from other maintainers (I am sure they all have their reasons not reacting) but it is not easy to work together with other module maintainers, or even to get in contact with them.
I just stopped for a long time developing further on the modules I maintained and waited how others would cooperate to merge modules, but it seems nothing really happens. I am starting now again to develop the modules further.
DON'T LET PEOPLE DISCOURAGE YOU, working on and maintaining your module while others don't.
Since working together seems difficult, it's up to the users of contributed modules to find out if a module is well maintained, what the usage statistics are for the module, what functionality they require and match it with a comparison page, etc before they use a module.
In the future I think modules with good maintenance and good usage statics will survive and other will "die" a natural way or don't get a new release for a new Drupal version.
Let time do the job, but not discouragement.
Comment #15
good_man commentedYou are right, especially communicating with maintainers, this is a sad thing, but the good thing is good maintained modules survive while others don't.
Hope we can cover all the scrolling functionality that users want.
I appreciate your comment and your concerns.
Comment #16
good_man commentedThe ultimate goal of this module is to provide the simplest way to display rotating banners/sliding content on your website. Please help me achieve this goal, if you find anything hard, not well implemented report it in the issue queue.
I'm closing this issue now, but will refer to it in the module's page on drupal.org.
Comment #17
good_man commented