Pseudo 3D Effect with Texturemapping

[Thorsten Kiefer]

Hi,
I coded a little effect :
http://www.tokis-edv-service.de/index.php/javascript

Best Regards
Thorsten

 

[SAM]

Le 8/11/09 11:23 AM, Thorsten Kiefer a écrit :

Hi,
I coded a little effect :
http://www.tokis-edv-service.de/index.php/javascript

a little slow in my Fx.3
better in my Sarari.3

where is the tutorial ?

 

[Jorge]

Le 8/11/09 11:23 AM, Thorsten Kiefer a écrit :


a little slow in my Fx.3
better in my Safari.3

Look at this 3-D CSS animations (in Safari 4) : (!)

http://webkit.org/blog-files/3d-transforms/poster-circle.html
http://webkit.org/blog-files/3d-transforms/morphing-cubes.html

http://webkit.org/blog/386/3d-transforms/

 

[SAM]

Le 8/11/09 2:30 PM, Jorge a écrit :

Look at this 3-D CSS animations (in Safari 4) : (!)

Unlovely, not yet installed Safari 4
I'm a little lazy (having versions 3 and 4 running together)

And My iCab.4.6.1 is also too old (or not yet ready ?)

 

[Jorge]

Le 8/11/09 2:30 PM, Jorge a écrit :



Unlovely, not yet installed Safari 4
I'm a little lazy (having versions 3 and 4 running together)

And My iCab.4.6.1 is also too old (or not yet ready ?)

Here's a video :

http://jorgechamorro.com/cljs/3DCSS/

 

[Hamish Campbell]

Here's a video :

http://jorgechamorro.com/cljs/3DCSS/

Went to a talk about the web-kit animation stuff. It's groovy, but
very iPhone-centric, and not a lot of use outside of that platform.
You also have to be careful to keep your animations limited to those
properties that Apple decided to hardware-accelerate for the iPhone.

Makes sense tho - there is a strong case that certain UI animations
handled by JavaScript could be better handled by CSS animations.
Animated highlighting, for example, would be great as a CSS feature.

 

[Jorge]

Went to a talk about the web-kit animation stuff. It's groovy, but
very iPhone-centric, and not a lot of use outside of that platform.

Well, <canvas> was Mac-widgets-centric, and had not a lot of use
outside of the Mac OSX platform, but now it's built into FFs, Chromes
and Operas too.

The web can't and won't move forward if it sits waiting for the w3c
(OMG) to come up with the next great thing(s), that's why we need
experiments like this (and most of HTML5's, and Mozilla's, and
Google's), that might eventually be ~ widely recognized as a "good
thing", and implemented in most browsers. At that point in time, they
become a standard (at least a de-facto one).

You also have to be careful to keep your animations limited to those
properties that Apple decided to hardware-accelerate for the iPhone.

There are things lacking any importance, that, instead, when
developing for the iPhone become important. For example, a page with a
setInterval() when left open on the iPhone could easily drain the
battery in an hour, while the same page without the timer could be
left open ~ forever. You would not care about a timer's power
consumption in a desktop browser, as the power supply is not a
concern. The point being that each and every additional cpu cycle
spent in a job costs battery life, -which is not a good thing on a
mobile phone- and things like e.g. fading out an element via CSS
via .style.opacity=x; with a timer in a loop in JavaScript code are
more expensive in terms of power than a browser-native hardware-aided
alternative. On top of extended battery life, you get a smoother fade-
out effect too.