[wp-hackers] Let's make Buttonsnap fully obsolete

[Stephane Daury]

Yup same feeling here, but I think I'll wait for 2.6 to stop  
supporting versions prior to 2.5.

---
Stephane Daury - http://tekartist.org/



On Apr 02, 2008, at 17:38, Viper007Bond wrote:

> On the backwards compatibility front, I'm actually seriously  
> considering
> just dropping pre-2.5 support for all of my plugins. Users are  
> welcome to
> use older versions of my plugins, but the amount of duplicate code is
> getting rediculous.
>
> For example, in my Video Quicktags plugin, I have to add buttons THREE
> different ways -- one for WordPress 2.0, one for TinyMCE 2, and one  
> for
> TinyMCE 3. Then for the BBCode (aka shortags), if I want to switch  
> to using
> the much easier and more robust shortags API in 2.5, I'd still have to
> maintain the old regex code for previous versions.
>
> It's kinda like once you start coding for PHP5 and using the new  
> features,
> it's hard to keep supporting PHP4 (although I will as that's not  
> nearly as
> bad).
>
> On Wed, Apr 2, 2008 at 2:22 PM, Stephane Daury <wordpress at tekartist.org 
> >
> wrote:
>
>>
>> Argh, now that I spent all that time integratiing with it and  
>> TinyMCE 2
>> and 3?!? :p
>>
>> Kidding, it's a great idea.
>>
>> Still gonna mean one more thing to support for plugins who want to be
>> backward compatible, but it's a good decision for the future,  
>> methinks.
>>
>> ---
>> Stephane Daury - http://tekartist.org/
>>
>>
>>
>>
>> On Apr 02, 2008, at 1:14, Viper007Bond wrote:
>>
>> For those who don't know, Buttonsnap is a PHP class that allows for  
>> super
>>> easy adding of buttons to the non-RTE editor and used to allow for
>>> adding
>>> buttons to TinyMCE as well.
>>>
>>> Source:
>>>
>>> http://svn.wp-plugins.org/vipers-video-quicktags/trunk/resources/buttonsnap.php
>>>
>>> Buttonsnap was made partially obsolete with WordPress 2.1 which  
>>> forced
>>> us
>>> plugin authors to write full fledged TinyMCE plugins to add  
>>> buttons. (No
>>> complaints from me really, just stating the facts).
>>>
>>> I propose we make it fully obsolete by introducing an API into the  
>>> core
>>> for
>>> adding (and even modifying?) the buttons in the non-RTE. I know  
>>> TinyMCE
>>> is
>>> the "preferred" editor of choice these days, but I absolutely hate  
>>> the
>>> thing
>>> and I don't think everyone else uses it. Not to mention there's  
>>> still
>>> the
>>> "HTML" aka Code tab that even TinyMCE users have access to.
>>>
>>> One solution would be to do quicktags.js -> quicktags.js.php and  
>>> make it
>>> dynamically generated (i.e. hooks and filters), but then we may  
>>> run into
>>> caching issues (although no-cache headers would fix that). Another
>>> solution
>>> would be one similar to how Buttonsnap works and just manually add
>>> buttons
>>> to the container.
>>>
>>> Any thoughts on this? Anyone else actually think it's a good idea?
>>>
>>> I for one would love to have to stop bundling Buttonsnap with my
>>> plugins.
>>> It's a great class, but it's time for it to retire and take it  
>>> easy in
>>> the
>>> code retirement home.
>>>
>>> --
>>> Viper007Bond | http://www.viper007bond.com/ | http://www.finalgear.com/
>>> _______________________________________________
>>> wp-hackers mailing list
>>> wp-hackers at lists.automattic.com
>>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>>
>>
>> _______________________________________________
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>
>
>
>
> -- 
> Viper007Bond | http://www.viper007bond.com/ | http:// 
> www.finalgear.com/
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers