Skip to content
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

Drag Issue #10

Closed
cgrobb opened this issue Mar 16, 2013 · 6 comments
Closed

Drag Issue #10

cgrobb opened this issue Mar 16, 2013 · 6 comments

Comments

@cgrobb
Copy link

cgrobb commented Mar 16, 2013

When running the Popcorn demo on my Galaxy Tab 10.1 with ICS and the latest Chrome browser...

Selecting a movie that's currently unselected by dragging it requires way more touch travel than what's expected. I expected that if I started a drag in the center of an unselected movie and moved my finger to the center of the demo's UI, that the movie would be selected. Instead it required significantly more touch travel past the center.

At first, I thought this might be typical drag lag, but it seems like it's a bug in the design/implementation of the demo.

@francoisfrisch
Copy link
Contributor

Yes, you are right, this is a known issue. What we need to do is a reverse
projection from camera (the plane where the touch is happening) to 3d
space. We have some prototypes but nothing concrete yet.

At the moment we have a fixed ratio between amount of touch
horizontal travel to the translation along the 3d path.

On Saturday, March 16, 2013, ungerrtb wrote:

When running the Popcorn demo on my Galaxy Tab 10.1 with ICS and the
latest Chrome browser...

Selecting a movie that's currently unselected by dragging it requires way
more touch travel than what's expected. I expected that if I started a drag
in the center of an unselected movie and moved my finger to the center of
the demo's UI, that the movie would be selected. Instead it required
significantly more touch travel past the center.

At first, I thought this might be typical drag lag, but it seems like it's
a bug in the design/implementation of the demo.


Reply to this email directly or view it on GitHubhttps://github.com//issues/10
.

@cgrobb
Copy link
Author

cgrobb commented Mar 17, 2013

Thanks for the explanation, Francois.

It still looks great, btw!

@cgrobb
Copy link
Author

cgrobb commented Apr 6, 2013

Upon more thought, every similar web UI I've used also has this issue, so I'd consider this aspirational.

The performance and visual fit and finish of the demo is extraordinary!

I do have one additional question. How difficult would it be (for a dev) to adapt this demo to a more complex (ie, one that also moves in the z-axis direction) 3d filmstrip? For example, this filmstrip,

http://www.tauntonfilmsociety.co.uk/images/2007filmstrip_small.jpg

@francoisfrisch
Copy link
Contributor

It is the Flow component that is doing the heavy lifting here.

It is displacing the tiles in 3d space along a defined path. I have rotated the camera element in the Web Inspector to highlight the role of the flow in the scene.
Path
The film strip is then a flat overlay that matches the perspective of the path, giving the impression of a reel of film.
top

What I'm really pointing out here is that the path is 3-dimensional in this example. Any path that is possible to define as a bezier curve is possible to use with the Flow component.

In the example these are the sections that might be of interest.
3D Path
Camera Properties
The knots are being programmatically calculated here so that we could adjust the radius of the circle to suit the design, but it should be possible to export the values for the knots and handles from cad software.

@cgrobb
Copy link
Author

cgrobb commented Apr 8, 2013

Thank for the additional background, Francois. I now have to hack on this!

@cgrobb
Copy link
Author

cgrobb commented Apr 24, 2013

For posterity...

I was able to edit existing and create new knots for the flow component used in the Paparazzi demo. It worked as expected. Of course, without additional logic, none of the objects were rotated to follow the path, they always faced directly forward.

For the curvy filmstrip path I was imagining, the flow component isn't a fit. Making the bends realistic would require very small-width images.

I'll post some additional thoughts about the flow component in an GitHub issue for it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants