New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Did WOOTHEMES kill FlexSlider? #725

Closed
ghost opened this Issue Jun 9, 2013 · 10 comments

Comments

Projects
None yet
3 participants
@ghost

ghost commented Jun 9, 2013

Ever since the acquisition of FlexSlider by WooThemes, it did not get any update 馃憥

The version 2, which was released a year ago, was a generous contribution offered by Tyler Smith, but beside that, WooThemes did not actually take over the project at any point.

Buying a software to bury it and leave it die slowly by just letting its obsolescence take over is a very bad ethical practice. It is not a secret from anyone that WooThemes purchased FlexSlider in order to get referrals from its users base. WooThemes never wanted FlexSlider at the first place, they wanted its popularity, nothing else. Therefore I recommend against buying any WooThemes software or services.

Many alternatives have came up ever since that are now much better than FlexSlider, just to name a few: iosSlider, bxSlider, ResponsiveSlides.js, LayerSlider, Revolution Slider, etc. which all support more browsers, more input types, more devices, more effects, more callbacks, more options, more flexibility, and are lighter! how come!

FlexSlider is dead. WooThemes killed it.

@mattyza

This comment has been minimized.

Show comment
Hide comment
@mattyza

mattyza Jun 9, 2013

Member

@wtfigo - We certainly didn't kill FlexSlider. :)

Please see all the activity in the "develop" branch, as well as the regular comments by our team, which shows activity. We are currently working on FlexSlider 2.2.0, which will support many features that have been requested by users such as variable width carousels and IE10 touchswipe support.

Chiefly, FlexSlider is 2 things:

  1. A lightweight slider.

FlexSlider doesn't have a bunch of different transition effects... intentionally. The script is intended to be light and simple to apply, without having a bunch of options presented when attempting to set it up. I believe we've stuck to this mantra well.

  1. A community project.

Above all, FlexSlider is driven both by WooThemes and by the users of the script. This is a public repository on GitHub and pull requests are always welcome (encouraged and regularly audited to ensure quality of the code).

If you see a feature you'd like to include in FlexSlider, we encourage you to submit pull requests. WooThemes facilitate the pull requests- a certain amount is up to the community as well.

I hope this sheds some light on the subject. :)

Thanks and regards,
Matty.

Product Manager at WooThemes

Member

mattyza commented Jun 9, 2013

@wtfigo - We certainly didn't kill FlexSlider. :)

Please see all the activity in the "develop" branch, as well as the regular comments by our team, which shows activity. We are currently working on FlexSlider 2.2.0, which will support many features that have been requested by users such as variable width carousels and IE10 touchswipe support.

Chiefly, FlexSlider is 2 things:

  1. A lightweight slider.

FlexSlider doesn't have a bunch of different transition effects... intentionally. The script is intended to be light and simple to apply, without having a bunch of options presented when attempting to set it up. I believe we've stuck to this mantra well.

  1. A community project.

Above all, FlexSlider is driven both by WooThemes and by the users of the script. This is a public repository on GitHub and pull requests are always welcome (encouraged and regularly audited to ensure quality of the code).

If you see a feature you'd like to include in FlexSlider, we encourage you to submit pull requests. WooThemes facilitate the pull requests- a certain amount is up to the community as well.

I hope this sheds some light on the subject. :)

Thanks and regards,
Matty.

Product Manager at WooThemes

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Jun 9, 2013

The develop branch is totally idle since 4 months.

There are actually 25 pull requests waiting, most of them don't have any comment/reply.

'just saying

ghost commented Jun 9, 2013

The develop branch is totally idle since 4 months.

There are actually 25 pull requests waiting, most of them don't have any comment/reply.

'just saying

@mattyza

This comment has been minimized.

Show comment
Hide comment
@mattyza

mattyza Jun 9, 2013

Member

@wtfigo - The develop branch is idle because we're waiting for the community to test the IE10 touch in the "feature-" branch. This is discussed in an issue here as well.

We'll do our best to keep better tabs on the pull requests and issues.

In terms of resolving the majority of the issues (which seem to be support requests), the community has a role to play here as well (not only WooThemes). :)

Member

mattyza commented Jun 9, 2013

@wtfigo - The develop branch is idle because we're waiting for the community to test the IE10 touch in the "feature-" branch. This is discussed in an issue here as well.

We'll do our best to keep better tabs on the pull requests and issues.

In terms of resolving the majority of the issues (which seem to be support requests), the community has a role to play here as well (not only WooThemes). :)

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Jun 9, 2013

Of course Support Requests isn't the topic here, you can't offer free support eternally for a free product, I'm only concerned about FlexSlider itself which seems abandoned, and which misses real support for the sliding effect: not working on IE10, not working with the mouse. Basically you can only slide on touch-enabled devices with a webkit browser, that's very restricting for a slider.

Thanks for your reply and I hope that FlexSlider development will get more active, as only you guys can merge pull requests, that is why the community is powerless without your involvement.

ghost commented Jun 9, 2013

Of course Support Requests isn't the topic here, you can't offer free support eternally for a free product, I'm only concerned about FlexSlider itself which seems abandoned, and which misses real support for the sliding effect: not working on IE10, not working with the mouse. Basically you can only slide on touch-enabled devices with a webkit browser, that's very restricting for a slider.

Thanks for your reply and I hope that FlexSlider development will get more active, as only you guys can merge pull requests, that is why the community is powerless without your involvement.

@ghost ghost closed this Jun 9, 2013

@mattyza

This comment has been minimized.

Show comment
Hide comment
@mattyza

mattyza Jun 10, 2013

Member

Thanks for your feedback, @wtfigo. We'll do our best to see FlexSlider shine.

Member

mattyza commented Jun 10, 2013

Thanks for your feedback, @wtfigo. We'll do our best to see FlexSlider shine.

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Jul 1, 2013

I'm reopening this issue as there was zero commits since your reply last month.

I'm the first to be disappointed and sad from this, but I feel like I have the responsibility to warn newcomers that FlexSlider is a dead project with no future whatsoever, as it doesn't even cover present basic and essential features like jQuery 1.9 compatibility, cursor-swiping (not only finger), IE10 support (which gains popularity every single day), etc.

WARNING: FlexSlider is a dead slider, don't rely on it for your own project, it lacks basic browser support (latest IE not supported, Firefox Mobile not supported, etc.) and wasn't updated for more than a year now 鈥 logic says that after a year of unsolved issues, you shouldn't expect any improvement whatsoever of the situation.

ghost commented Jul 1, 2013

I'm reopening this issue as there was zero commits since your reply last month.

I'm the first to be disappointed and sad from this, but I feel like I have the responsibility to warn newcomers that FlexSlider is a dead project with no future whatsoever, as it doesn't even cover present basic and essential features like jQuery 1.9 compatibility, cursor-swiping (not only finger), IE10 support (which gains popularity every single day), etc.

WARNING: FlexSlider is a dead slider, don't rely on it for your own project, it lacks basic browser support (latest IE not supported, Firefox Mobile not supported, etc.) and wasn't updated for more than a year now 鈥 logic says that after a year of unsolved issues, you shouldn't expect any improvement whatsoever of the situation.

@ghost ghost reopened this Jul 1, 2013

@mattyza

This comment has been minimized.

Show comment
Hide comment
@mattyza

mattyza Jul 1, 2013

Member

Please re-read my response above.

FlexSlider is by no means a dead project.

Please also see the regular responses to new issues that are being listed... even to issues that don't end up being related to FlexSlider at all. We want to help.

Please also see my comment that FlexSlider is an open source project. This means that we are open to pull requests from the user community and welcome them with open arms.

Pull requests that are currently open will be tested and merged or closed prior to FlexSlider 2.2.0's release.

Thank you, again, for your passion for FlexSlider. It is very much appreciated and your feedback has been received. :)

Thanks and regards,
Matty.

Chief Product Officer at WooThemes

Member

mattyza commented Jul 1, 2013

Please re-read my response above.

FlexSlider is by no means a dead project.

Please also see the regular responses to new issues that are being listed... even to issues that don't end up being related to FlexSlider at all. We want to help.

Please also see my comment that FlexSlider is an open source project. This means that we are open to pull requests from the user community and welcome them with open arms.

Pull requests that are currently open will be tested and merged or closed prior to FlexSlider 2.2.0's release.

Thank you, again, for your passion for FlexSlider. It is very much appreciated and your feedback has been received. :)

Thanks and regards,
Matty.

Chief Product Officer at WooThemes

@mattyza mattyza closed this Jul 1, 2013

@mattyza mattyza reopened this Jul 1, 2013

@llahnoraa

This comment has been minimized.

Show comment
Hide comment
@llahnoraa

llahnoraa May 19, 2014

I agreed with @ghost (just now deleted user, not sure why). I'm more concerned about Flexslider and the future updates. Any progress since it's been almost a year?

I agreed with @ghost (just now deleted user, not sure why). I'm more concerned about Flexslider and the future updates. Any progress since it's been almost a year?

@mattyza

This comment has been minimized.

Show comment
Hide comment
@mattyza

mattyza May 19, 2014

Member

We are currently in the process of planning out FlexSlider version 2.3.0. Development on this version will begin as soon as possible. :)

If you spot items you'd like to see included, please log issues or contribute pull requests. :)

Matt Cohen
Chief Product Officer at WooThemes

http://woothemes.com/
http://matty.co.za/

On Monday 19 May 2014 at 9:58 PM, Aaron Hall wrote:

I agreed with @ghost (https://github.com/ghost) (just now deleted user, not sure why). I'm more concerned about Flexslider and the future updates. Any progress since it's been almost a year?


Reply to this email directly or view it on GitHub (#725 (comment)).

Member

mattyza commented May 19, 2014

We are currently in the process of planning out FlexSlider version 2.3.0. Development on this version will begin as soon as possible. :)

If you spot items you'd like to see included, please log issues or contribute pull requests. :)

Matt Cohen
Chief Product Officer at WooThemes

http://woothemes.com/
http://matty.co.za/

On Monday 19 May 2014 at 9:58 PM, Aaron Hall wrote:

I agreed with @ghost (https://github.com/ghost) (just now deleted user, not sure why). I'm more concerned about Flexslider and the future updates. Any progress since it's been almost a year?


Reply to this email directly or view it on GitHub (#725 (comment)).

@jeffikus

This comment has been minimized.

Show comment
Hide comment
@jeffikus

jeffikus Feb 27, 2015

Member

Just a further update - I am the active Senior Developer on the project now. You will be seeing regular updates to the script in the coming weeks, we've already pushed out 2.3.0 and 2.4.0 will go out within the next few days.

Member

jeffikus commented Feb 27, 2015

Just a further update - I am the active Senior Developer on the project now. You will be seeing regular updates to the script in the coming weeks, we've already pushed out 2.3.0 and 2.4.0 will go out within the next few days.

@jeffikus jeffikus closed this Feb 27, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment