[wp-trac] [WordPress Trac] #12423: Include Bespin as default code editor

WordPress Trac wp-trac at lists.automattic.com
Mon Apr 12 10:30:50 UTC 2010


#12423: Include Bespin as default code editor
-----------------------------+----------------------------------------------
 Reporter:  scribu           |       Owner:                
     Type:  feature request  |      Status:  new           
 Priority:  normal           |   Milestone:  Future Release
Component:  Editor           |     Version:  3.0           
 Severity:  normal           |    Keywords:                
-----------------------------+----------------------------------------------
Changes (by nacin):

  * milestone:  3.1 => Future Release


Comment:

 Replying to [comment:5 c00l2sv]:
 > Also found this: http://shjs.sourceforge.net/

 General thoughts here. By all means, we should identify and test as many
 projects as possible. That said, I don't think we want to repeat mistakes
 made with CodePress in regards to project activity.
 http://shjs.sourceforge.net/ has only one maintainer (as does EditArea and
 countless others) though it also hasn't had a release since 2008.

 It would be naive to think that just because a project supports IE6 now,
 it'll always support every presumably more standards-compliant browser in
 the future (not to mention future standards). Aside from that, inclusion
 in WordPress would reveal existing bugs thanks to a larger userbase.

 Finding an active (and willing) project should be as important an
 objective as finding one that works cross-browser.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/12423#comment:6>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list