'Potential'
Do you have problems, concerns or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
Gus, I'm going to save a copy in your site called production_post.php.
I had another thought, please don't run away.
The way WX handles open tags is to fix them, not on saving, but on display. So I will always see what I typed in, but it will generate healthier HTML.
Can we do that, for editing sanity? Including for the hyphenation? Put it in the same area as the quickedit expansion?
Since I always used [www.site.org...] when I was shortening links, I prefer option 1. As ita says, it adds some context.
The way WX handles open tags is to fix them, not on saving, but on display.
Hmm. Where does more processing go? On display, which must be incredibly more frequent than saving, or on saving?
OK, that was loaded. I get your concern, but I worry about the net effect on performance.
Oh, sweet. Go, Gus.
Thanks, Katie.
It will be more processing heavy, and I understand your concern, but even I get fidgety editing my post that's not what I typed in. I think it increases the potential for confusion.
Also, it's kind of a principle thing.
Maybe we should benchmark and see if it's a detectable hit.
t produces a bead of sweat as he fights off the ita lust
Prove the hypothesis experimentally.
t Young. The girl is only young. Ignore the fully rounded frontal lobes.
What does the code for [continued] do when someone adds text during editing?
<Young. The girl is only young. Ignore the fully rounded frontal lobes.>
The eyes are down HERE, buddy.
What does the code for [continued] do when someone adds text during editing?
Right now, if I read the code right, nothing. But the automated code cuts you way shorter than our internally imposed limit, so it shouldn't come up often at all.
t snickers at the geek-lust