[wp-hackers] WordPress 2 and Client Side Scripting

[Aaron Brazell]

While I don't know the answer to this, I might point out that WordPress
opted NOT to use the "common" XML-RPC libraries and by doing so, avoided
having thousands of blogs vulnerable to an exploit a few weeks ago.  Mob
tendencies, while often nice for developers, aren't always a good thing.

Aaron

On 11/25/05, Theodor Ramisch <theodor_ramisch at hotmail.com> wrote:
>
> Hi there,
>
> I just tried out the WordPress 2 Beta 1 and the new
> interface style looks very nice. :)
>
> Then I looked a little bit around in the source code
> to figure out how the AJAX request and fade effects
> were realized.
>
> Unfortunately I had to see that you are using custom
> classes to do such "common" effects. That makes
> plugin development harder if you have to deal
> with them on plugin options pages for example.
>
> Why not rely on well known, stable libraries
> like script.aculo.us and prototype? There are
> a lot of developers who already worked with
> them and adapted to functions like "$" which
> replaces the document.getElementById.
>
> So it would be very nice if future versions
> of WordPress ship script.aculo.us and
> prototype with them.
>
>
> Best regards,
>
>   Theodor Ramisch
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>



--
--
Aaron Brazell
Editor/Writer
http://www.technosailor.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://comox.textdrive.com/pipermail/wp-hackers/attachments/20051125/0793469e/attachment.htm