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 >