Good points and comments Rolf. I had no time to extract the parts to create a new fiddle but now it has been done.
http://jsfiddle.net/Fli7e/Stwp7/ Also the Wheel-Support has been added and i reworked some obsolete get() and getProperty() calls. Some of which you mentioned and some other. Why not using other peoples work ... well, i like to learn stuff and using 3rd party "ready steady everything is fine" scripts will just teach me reading the usage docs. Also, as you already pointed out, the kind of slide has not yet been done and i personaly dislike the backjumping slideshows - thats the main reason i started with this script. The KeyEvents ... well, how do i delegate the arrow left/right keys to the slide without harming the general behaviour? wheel is easy because you need to enter the element but keys can be pressed anywhere on the page. even though, what would happen if i add 2 or more sliders on one page .. which slider would take itself responsible for the keypress? Adding / removing the events triggered by another event (mouseenter / leave) on the slider would fix all the questions right in place but if i need to mouse-over i could easily use the wheel as is. Timo On 4 Apr., 21:02, Rolf -nl <plentyofr...@gmail.com> wrote: > like the concept of swapping. I have a never-finished-hacknslash- > version somewhere (even used live I think) that does the same. The > code is not optimized though.. > Why is the newly-developed one that available as a fiddle? ;) the code > is crunched on the semi-dev-in-progress site so that sucks. > > Why are you using setProperty and on the same line get('id')? I'd just > keep it consistent and use set. > This is anal, but I'd also incorporate mootools programming > conventions like the accolades on the same line as the if-statement > and do it like: if (...){ > There's a doc somewhere about this.. but really, it's just details, > but I'm anal about that stuff and I like everything to be the same > hehehe > > Also, add keyboard events. And mouse scroll events.. you call it a > content slider anyway ;)) > > You could also check out Ryan Florence > SlideShow,http://ryanflorence.com/slideshow/ > Great API, last time I worked with it the fx part was a bit overly > complex imho, but I didn't propose another idea so who am I to > "complain".. I always wonder myself: do I need to make another tool, > can't I just use one already there that is pretty advanced. Then > again, yours it with a different concept; swapping the content divs > > Ok, stopping now.. good work > > On Apr 4, 6:19 pm, Fli7e <ultrakr...@googlemail.com> wrote: > > > Good Idea @Arian - already did it on my dev. page (http:// > > gpl.artness.de/) and i like the idea :-) 'll see what i can come up > > with next. > > > Thanx for the feedback > > > On 4 Apr., 14:46, Arian Stolwijk <ar...@aryweb.nl> wrote: > > > > I would make your API easier, with methods like: next, previous, slide(n). > > > > On Mon, Apr 4, 2011 at 2:43 PM, Robert <forpoc...@gmail.com> wrote: > > > > very nice, better usability then ones maddingly scrolling there and > > > > back ;) > > > > > On Apr 3, 1:58 pm, Fli7e <ultrakr...@googlemail.com> wrote: > > > > > A Real-World Example can be found, at the time beeing, on my dev-test > > > > > Webseite under > > > > > >http://gpl.artness.de/ > > > > > > might disappear soon but for now it can be viewed. > > > > > > Timo > > > > > > On 2 Apr., 22:10, Fli7e <ultrakr...@googlemail.com> wrote: > > > > > > > Hi there, > > > > > > > today i sat down and did some content slider class to learn / > > > > > > improve > > > > > > and testdrive my mootools skills. > > > > > > > The Slider itself uses some mechanics to never "jump" back to the > > > > > > beginning but appending the elements left or right to the actual > > > > > > displayed element so there is an endless loop. > > > > > > > Eg. pressing "next" on the last element won't rewind back to 1st > > > > > > element but move the 1st element as next element after the previous > > > > > > last one. > > > > > > > I am doing this by swapping the content of two divs depending on > > > > > > which > > > > > > action has been called and repositioning those divs after the tween > > > > > > has been done. > > > > > > > I setup a fiddle and would like your Opinion and your improvement > > > > > > ideas. > > > > > > >http://jsfiddle.net/rmh2B/1/ > > > > > > > I personaly like what i cam up with but i think there is room for > > > > > > improvements by you pro's ... > > > > > > > Thanx in advance, > > > > > > > Timo
