That's a good point. Android apps commonly uses "swipe down" to trigger a refresh. The swipe still physically happens, but there's just a gray background behind it, and it pops back into place and resets.
The main problem seems to be what happens during a swipe. Part of the effect is the feedback of seeing one card move on top of another. After the swipe is completed we can just use regular messages to do whatever. Another swipe effect would be pulling the next card in to fill the space left by the moving card, rather than the next card being stationary underneath. On Thu, Apr 27, 2017 at 10:30 AM, Richard Gaskin via use-livecode < use-livecode@lists.runrev.com> wrote: > Matt Maier wrote: > > > Maybe each card could have a parameter like "swipeTo" which would be > > the id of another card. Default could be nothing, which would disable > > swipe. But if there's a card id in there then swiping would put that > > card "underneath" so it's visible as the current card moves and if > > the swipe gesture completes the stack moves to that new card. > > > > The swipe gesture might be just a scroll that's handled as a swipe > > when the card can't scroll in that direction. Like if you swipe > > up/down the content scrolls, but if you swipe left/right, since > > there's no scroll in that direction, you get a swipe to another card. > > I like where you're going with that. But it also suggests other options > that would be useful, more stuff to think over before submitting a request. > > Rather than a single swipeDestination property to designate which card we > go to during a swipte, ideally we'd want that for each of the four cardinal > directions, e.g. swipeLeftDestination, swipeTopDestination, etc. > > Also, it would be nice to be able to specify the origin threshold, since > sometimes we'd want to initiate a drag from any part of the card and other > times only from a certain edge. > > Hmmm...not so simple once we dive into the full range of use-cases, but I > do think it's worth exploring this here because it would be SOOOOO much > simpler to use LC's card metaphor for modern apps if we had more fluid > transition capabilities. > > -- > Richard Gaskin > Fourth World Systems > Software Design and Development for the Desktop, Mobile, and the Web > ____________________________________________________________________ > ambassa...@fourthworld.com http://www.FourthWorld.com > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
