@Alex
This is a valid concern. I happen to side with Andy Clarke, who fervently advocates designing for the best features out there. He wrote a whole book about it. But just in the last couple months I’ve seen more examples of 3D transforms popping up. So I know as a collective, we web designers are certainly ready to start using them – because people are already doing so.
But our early steps have been a bit misguided. all the of 3D object (mostly cube) demos, not one of them resolve the pixelation issue. In Mr. Clarke’s published book, his card-flipping demos suffer from the multiple-vanishing-point issue I discuss in this article. I felt like now was a great time to jump in and try to explore these issues while the subject is still fresh.
@Benjamin
Ooooooo, this is neat. If I understand you correctly, the carousel should rotate around the viewer, and not around a point behind the visible cell. For issues like this, I always start sketching so I can better understand what I’m going for. Take a look
In the Carousel 1 example we would reverse how we’re applying @transformZ@ values. Each panel would be pulled in in 3D space, @transformZ( -288px )@ and the carousel would be pulled back @transformZ( 288px )@ The tricky part is figuring out how many cells you’ll need to so that the center point of the carousel is behind the viewer. Best of luck!
The tricky part is figuring out where the viewer is in 3D space.
David DeSandro
@Malte
You might be thinking of how GPU acceleration is triggered in Chromium. I haven’t had a chance to verify this. Yes, I am sure about the Safari hardware acceleration.
@Alex
This is a valid concern. I happen to side with Andy Clarke, who fervently advocates designing for the best features out there. He wrote a whole book about it. But just in the last couple months I’ve seen more examples of 3D transforms popping up. So I know as a collective, we web designers are certainly ready to start using them – because people are already doing so.
But our early steps have been a bit misguided. all the of 3D object (mostly cube) demos, not one of them resolve the pixelation issue. In Mr. Clarke’s published book, his card-flipping demos suffer from the multiple-vanishing-point issue I discuss in this article. I felt like now was a great time to jump in and try to explore these issues while the subject is still fresh.
@Benjamin
Ooooooo, this is neat. If I understand you correctly, the carousel should rotate around the viewer, and not around a point behind the visible cell. For issues like this, I always start sketching so I can better understand what I’m going for. Take a look
In the Carousel 1 example we would reverse how we’re applying @transformZ@ values. Each panel would be pulled in in 3D space, @transformZ( -288px )@ and the carousel would be pulled back @transformZ( 288px )@ The tricky part is figuring out how many cells you’ll need to so that the center point of the carousel is behind the viewer. Best of luck!
The tricky part is figuring out where the viewer is in 3D space.