Jump to content

Oomph last won the day on November 27 2016

Oomph had the most liked content!


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by Oomph

  1. Hey thanks for the feedback! Our own js app.min.js actually supports a lot more than is currently made available publicly (e.g. carousels, flipbooks etc) but I totally take in your point, it should be a lot smaller as it's only simple animations right now. Thanks for the pricing feedback too, regarding price points, the Indie plan at $49 covers the usage of most customers. Our current target niche is ads banner creation, the higher plan is only really suitable for those doing much higher volume ads per month. We're working on adding more functionality such as saving to video, better psd templates and more ad types supported (eg expandables) and functionality (more interactivity). Most of this is already actually supported behind the scenes for our clients on the highest plans but not visible yet on the website.
  2. Hey there, just want to share with y'all a simple tool that basically creates html5 animated banners using GSAP by simply automatically converting static images or from psd or pdf The tool is at https://www.adomatic.io You can then download directly for DoubleClick Studio or Adwords usage Looking for feedback! Cheers
  3. For anyone reading this with a similar problem, the solution ended up being manually attaching mouse/touch handling events to the element you create the draggable on, and enabling/disabling any parent draggables from there. Using event.stopPropagation on mousemove (native browser) or onDrag (GSAP) won't work for desktop. Enabling/disabling parent draggables in the onDrag event (GSAP) will work but seems to lag by a few milliseconds (potentially due to the GSAP internal event delegation system, not sure how it works), meaning you'll still see some movement on the parent draggable and it looks pretty bad. The only solution for desktop/mobile is to enable/disable parent draggables in the mousemove event (native browser), eg: var element = document.getElementById('my-child-draggable'); Draggable.create(element, {}); element.addEventListener('mousemove', function() { if (conditionForStoppingPropagation) { parentDraggable.disable(); } }); element.addEventListener('mouseup', function() { parentDraggable.enable(); });
  4. Hi there, I'm developing an application that requires nested draggable objects (draggables within draggables), however I'm running into issues. As far as I can understand from the docs, the linked codepen should work, allowing the child draggable to be dragged independently of the parent. This appears not to work as a result of the draggable events (mousemove etc) being attached to the document rather than the actual draggable element, so stopPropagation has no effect. If I understand correctly though stopImmediatePropagation should still work though based on the event attachment order. I understand one solution would be to enable/disable the parent draggable based on child dragStart/dragEnd, however this doesn't work for me as I need to have a vertical-only draggable grandchild within a vertical-only draggable child within a horizontal-only draggable parent (complicated I know!), and dragging the grandchild horizontally should still trigger the parent draggable, but dragging it vertically should NOT trigger the child draggable. My current solution involves enabling/disabling the parent draggable based on scroll direction, however this results in a small amount of movement in the parent direction before it can be disabled. The reason I'm asking is that this is a responsive app, and mobile is currently working fine as the Draggable code attaches touch events directly to the element, rather than the document, and works perfectly (with no movement of the parent element whatsoever). Is there a way to replicate this on desktop without breaking everything, potentially using stopImmediatePropagation? (I note in the code you've put "//attach these to the document instead of the box itself so that if the user's mouse moves too quickly (and off of the box), things still work.")