-
Notifications
You must be signed in to change notification settings - Fork 54
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove carousel tile from the package core #485
Comments
I think yes... but smoothing the migration could do with some bright ideas |
I agree with the idea too |
Can't disagree here, suggested it in #442 :-) |
Yes. (and also, if it should be of any interest, I started work with tiles for collective.plonetruegallery https://pypi.python.org/pypi/collective.ptg.tile/0.1b1 (worked when I made it, but has never been used on any sites) |
@espenmn feel free to document that on the README file |
Just to log (for those who don't already know) that https://github.com/collective/covertile.cycle2 is a new carousel tile based on the Cycle2 framework. It could do with some review & feedback from any interested party before it's first release |
@djowett we are going to start using it tomorrow; we will let you know. |
Correct me if I'm wrong, but this is not question any more... |
no, I will open a branch later today to address this issue and will move the code of the Galleria carousel to the new package. |
Lately we have had some discussions about many things on the carousel tile and some pull requests have been proposed to offer an alternative solution
There are many solutions for carousels and everybody seems to have their own opinion on which one is the best.
So… should we just spin off the code of the carousel tile out of the core of this package to make it easier to maintain and leave people to choose whatever JS plug-in they want to use?
The text was updated successfully, but these errors were encountered: