[wp-hackers] making the code editor the default view

Jeremy Clarke jer-wphackers at simianuprising.com
Mon Dec 3 16:04:08 GMT 2007

I think it's pretty much an accidental feature, but for me it's
important that the "turn off visual editor" option actually disable
the whole mess completely because at least right now having the whole
thing turned off means that there is less formatting of the post that
goes on. My best example was that even the code view was chewing out
<embed> at savetime but if you turned off the visual editor and used
the old quicktag system the <embed> would survive (i think this was
fixed but there are more bugs floating around that I'd still like to
avoid in some cases).

There's probably a relatively simple way to make the code view use the
same filters as the oldschool view, but I thoroughly appreciate being
able to tell people with no tech background who ask me why their posts
are getting borked to just turn off the setting in their profile and
having that solve the problem 90% of the time.

Aside from that, +1 for remembering where you left it AND for the link
when you switch to your non-default tab, whichever is ready first,
though if we can avoid loading all the TinyMCE wysiwyg js for people
with code default, that would be awesome.

Jeremy Clarke

On Dec 2, 2007 5:17 PM, Johannes Ruthenberg <johannes at bolarus.de> wrote:
> Hi!
> Bull3t wrote on 01.12.2007 14:12:
> > Where would be the point in that? If you want the default view to be code,
> > why not just disable TinyMCE and/or just hit the button every time? I don't
> > understand...
> I'm sure there are a few scenarios for using both editors. I myself like
> to use the code view most of the time, because it's easier and faster.
> But I switch to the visual editor when I insert an image for the simple
> and somewhat ridiculous reason that in the code view the image gets
> inserted as <img src='...'> (as opposed to <img src="...">). Well, it's
> my blog and valid or not, I don't like the single quotes in the HTML.
> ;-) Switching between the editors is usually faster than changing the
> quotes manually.
> John Blackbourn wrote on 01.12.2007 16:20:
> > Find the JavaScript function that is called when you click on the
> > 'code' tab. Write a plugin that calls that function when the post
> > writing screen finishes loading, which should make the editor switch
> > to code view, still leaving the visual tab available.
> Thanks for the idea. That would most probably work. But what bothers me
> a little bit about the visual editor is the time it takes to load. I'd
> like that to be reduced, and switching to the code view with a
> JavaScript function wouldn't help from this point of view. ;-)
> Matt Mullenweg wrote on 02.12.2007 08:26:
> > I disagree, I think it should just remember where you last left it, and start there.
> >
> > Opened 9 months ago:
> > http://trac.wordpress.org/ticket/3978
> That sounds like a great idea. I certainly wouldn't care if I could make
> the code view the default or if WordPress just remembers where I last
> left it. So, what would we need to do to move this along for one of the
> next versions? I'm kinda new to WordPress and not really sure I could do
> this myself. *g* Would be willing to help, though, if that's possible.
> Bye,
> Johannes
> --
> "Life brings hope and pain, but revenge never brings redemption."
> [Highlander: Endgame]
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> http://johannes-ruthenberg.de
> http://www.ammaletu.de
> http://www.bolarus.de
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers

More information about the wp-hackers mailing list