Comments on: script.aculo.us morph effects http://mir.aculo.us/2006/11/21/script-aculo-us-hits-1-7-beta/ Just another WordPress weblog Thu, 11 Mar 2010 13:18:22 +0100 http://wordpress.org/?v=2.9.1 hourly 1 By: Tobie Langel http://mir.aculo.us/2006/11/21/script-aculo-us-hits-1-7-beta/comment-page-1/#comment-12 Tobie Langel Tue, 21 Nov 2006 09:36:00 +0000 http://mir.aculo.us//2006/11/21/script-aculo-us-hits-1-7-beta#comment-12 Greeeeeaaaaat!!!!! Happy I teased you about it...! ;-) Out of curiosity, what is the rationale behind passing the styles as a string, rather than an object? Performance? In any case, this is great! Greeeeeaaaaat!!!!!

Happy I teased you about it…! ;-)

Out of curiosity, what is the rationale behind passing the styles as a string, rather than an object?

Performance?

In any case, this is great!

]]> By: Tobie Langel http://mir.aculo.us/2006/11/21/script-aculo-us-hits-1-7-beta/comment-page-1/#comment-13 Tobie Langel Tue, 21 Nov 2006 09:36:00 +0000 http://mir.aculo.us//2006/11/21/script-aculo-us-hits-1-7-beta#comment-13 My question regarding performance was related to using a string rather than an object for passing the style, not to the overall performance of the morph effects... And yes... I'd much rather pass an object than a string, it's way more consistent with the way <code>setStyle</code> is handled in Prototype. OT: why not extend Prototype to have a <code>capitalize</code> string method... I've seen instances of <code>s.charAt(0).toUpperCase() + s.substring(1)</code> pop up just about everywhere lately... ;-) My question regarding performance was related to using a string rather than an object for passing the style, not to the overall performance of the morph effects…

And yes… I’d much rather pass an object than a string, it’s way more consistent with the way <code>setStyle</code> is handled in Prototype.

OT: why not extend Prototype to have a <code>capitalize</code> string method… I’ve seen instances of <code>s.charAt(0).toUpperCase() + s.substring(1)</code> pop up just about everywhere lately… ;-)

]]> By: John Nunemaker http://mir.aculo.us/2006/11/21/script-aculo-us-hits-1-7-beta/comment-page-1/#comment-14 John Nunemaker Tue, 21 Nov 2006 09:36:00 +0000 http://mir.aculo.us//2006/11/21/script-aculo-us-hits-1-7-beta#comment-14 Just read your comment about css class support. Guess I should have read all the comments before posting. :) Just read your comment about css class support. Guess I should have read all the comments before posting. :)

]]> By: th0fu http://mir.aculo.us/2006/11/21/script-aculo-us-hits-1-7-beta/comment-page-1/#comment-15 th0fu Tue, 21 Nov 2006 09:36:00 +0000 http://mir.aculo.us//2006/11/21/script-aculo-us-hits-1-7-beta#comment-15 Tobie: Great that you like it. Performance: it uses the script.aculo.us effects backend, so generally the performance is great. Object/string: for now it's strings, but I guess I'll add something to it that allows it to use object-based style definitions too. Also in the works: support for CSS classes. Tobie: Great that you like it. Performance: it uses the script.aculo.us effects backend, so generally the performance is great. Object/string: for now it’s strings, but I guess I’ll add something to it that allows it to use object-based style definitions too. Also in the works: support for CSS classes.

]]> By: John Nunemaker http://mir.aculo.us/2006/11/21/script-aculo-us-hits-1-7-beta/comment-page-1/#comment-16 John Nunemaker Tue, 21 Nov 2006 09:36:00 +0000 http://mir.aculo.us//2006/11/21/script-aculo-us-hits-1-7-beta#comment-16 Thomas, This is pretty cool. My only aversion to this is that now we are using javascript for css. I haven't really thought it through, but is there anyway to morph between the current styles and a css class instead of putting in all the css selectors? Then one wouldn't have to maintain their presentation in two places (js and css) instead of one (css). Just curious. Thomas, This is pretty cool. My only aversion to this is that now we are using javascript for css. I haven’t really thought it through, but is there anyway to morph between the current styles and a css class instead of putting in all the css selectors? Then one wouldn’t have to maintain their presentation in two places (js and css) instead of one (css). Just curious.

]]> By: Tobie Langel http://mir.aculo.us/2006/11/21/script-aculo-us-hits-1-7-beta/comment-page-1/#comment-17 Tobie Langel Tue, 21 Nov 2006 09:36:00 +0000 http://mir.aculo.us//2006/11/21/script-aculo-us-hits-1-7-beta#comment-17 @ Thomas: <a href="http://dev.rubyonrails.org/ticket/6666">patch for capitalize</a> @ John: Thomas wrote the following in the comments above: <blockquote>Also in the works: support for CSS classes</blockquote> Looks like your mind had been read... @ Thomas: <a href="http://dev.rubyonrails.org/ticket/6666">patch for capitalize</a>

@ John: Thomas wrote the following in the comments above:

<blockquote>Also in the works: support for CSS classes</blockquote>

Looks like your mind had been read…

]]> By: Tobie Langel http://mir.aculo.us/2006/11/21/script-aculo-us-hits-1-7-beta/comment-page-1/#comment-18 Tobie Langel Tue, 21 Nov 2006 09:36:00 +0000 http://mir.aculo.us//2006/11/21/script-aculo-us-hits-1-7-beta#comment-18 Come to think about it, if morph included an <code>initialStyle</code> option, couldn't most effects be rewritten as calls to morph? For example: <pre><code> Effect.Highlight = function(element) { element = $(element); new Effect.Morph(element, { initialStyle: { backgroundColor: '#f00' }, finalStyle: { backgroundColor: element.getStyle('backgroundColor') } }) } </code></pre> Come to think about it, if morph included an <code>initialStyle</code> option, couldn’t most effects be rewritten as calls to morph?

For example:

<pre><code>
Effect.Highlight = function(element) {
element = $(element);
new Effect.Morph(element, {
initialStyle: {
backgroundColor: ‘#f00′
},
finalStyle: {
backgroundColor: element.getStyle(‘backgroundColor’)
}
})
}
</code></pre>

]]> By: th0fu http://mir.aculo.us/2006/11/21/script-aculo-us-hits-1-7-beta/comment-page-1/#comment-19 th0fu Tue, 21 Nov 2006 09:36:00 +0000 http://mir.aculo.us//2006/11/21/script-aculo-us-hits-1-7-beta#comment-19 The other effects have some additional features that might not be doable with effect.morph, but basically, yes some of them can be rewritten to use it (i _love_ patches!). <code>.capitalize</code>: please submit a tested patch (that also updates the occurences...) :) The other effects have some additional features that might not be doable with effect.morph, but basically, yes some of them can be rewritten to use it (i _love_ patches!).

<code>.capitalize</code>: please submit a tested patch (that also updates the occurences…) :)

]]> By: Chris http://mir.aculo.us/2006/11/21/script-aculo-us-hits-1-7-beta/comment-page-1/#comment-21 Chris Tue, 21 Nov 2006 09:36:00 +0000 http://mir.aculo.us//2006/11/21/script-aculo-us-hits-1-7-beta#comment-21 I suppose you heard it a few times, but: You (and Scriptaculous) rock! I suppose you heard it a few times, but: You (and Scriptaculous) rock!

]]> By: Pat http://mir.aculo.us/2006/11/21/script-aculo-us-hits-1-7-beta/comment-page-1/#comment-22 Pat Tue, 21 Nov 2006 09:36:00 +0000 http://mir.aculo.us//2006/11/21/script-aculo-us-hits-1-7-beta#comment-22 the effects are really choppy, and i have a 1.0GHz G4, not some old machine. compared to moo.tools this is garbage. the effects are really choppy, and i have a 1.0GHz G4, not some old machine. compared to moo.tools this is garbage.

]]>