So … here we are in a typical TinyMCE WYSIWYG window. *shrug*

This should be a new paragraph; I’ll use it to point to Leo’s post about his WP editor fix , the “Trustworthy” plugin.

Now, let’s see if I can stick this line up closer by changing the paragraph end to a mere line break, i.e. replace </p> with <br />. ( NB : No markup visible in “Code” view. So why ohhh why then is this called code view?!

This remains a real thorn in my side … I don’t need yet.another source of migraine.)

* Mmmmm .. no HR in this menu setup? Gotta tweak that. *

No joy … none at all … <b> becomes <strong>, (Transitional XHTML?), but <br /> disappears, replaced by </p>, and that’s what bugs me most of all.

Bottom line? Mehh! Good news: I was wrong.

Turns out that the plugin’s XHTML settings default to “Disabled”. I toggled that (XHTML transitional) and whoopeee! Toggling back and forth between WYSIWYG and “Code”; editor did notRPTnot blow my markup away!

And yet, even with Leo’s lovely fix, what I wrote on my Codex.WP page still holds, if only as an enhancement:

“ Quick Fix to the Editor Blues ? – Yesterday during WP “Bug Day” I worked through a bunch of “editor” tickets; on the one that seemed to be tracking the problems I suggested a quick fix, i.e.:

since the problem happens when toggling between CodeView *cough* and “WYSIWYG” *nervous giggle* if we’re clever enough to Save or Publish while looking at our code in Source pushes most of what we actually keyboarded.

So I suggested we supply a config option to switch the default … so CodeView would be front … which would mean that hitting Save/Publish directly from there would obviate most of those glitches.”

NB: In WYSIWYG there’s plenty of whitespace between the blockquote and the previous text. When published, the blockquote is smoosched up against the bottom of that text line. Mehh again!! (Working on this.)

* This is a wrap … little things to check out (like how hittin Return twice and backspace once affects the way editor interprets my intention) but basically, bottom line, Editor Blues are gown.gown. gowwwn ! Or is it. Kicking things around, at some point a few of the forced newlines disappeared. Ick, I’m tired.*

Update: at some point this post went <pre>. *blink* I checked config and found it set to “Disabled”. *blink* More later.

Thinking about “silos” … grappling for an over-arching metaphor … references to glasperlenspiel only go so far! ;-)

How about this: Buddy has written a fine short essay on leveraging information. (Or maybe on how children living in poverty is actually criminal assault!) Let’s say Buddy doesn’t know about OpenOffice and has created a M$ .DOC. How does he share it?
Let’s say he creates an HTML version. Then what? He posts it as a page on his site … maybe using the “page” function in WordPress, so he can receive comments. Maybe as a blog post, to the same effect. Maybe as a doc in docs.google … maybe in 1 or several different collab systems. Maybe even as a wiki page. Or maybe he emails it to a list … or a few lists (assuming he’s converted away from DOC). Or maybe he uploads it as a file to yahoo or google groups.

Great! He’s broadcast his work!

But: each one of those is its own silo. (My point: “DAV” is still primitive.)

I’m sure you’ve seen blog posts that have received lots of comments … horrid. Ghastly. With all my surveying I’ve seen a total of 1 blog system that makes any effort to thread those (apart from the threading mechanism at LiveJournal), and that’s the system Jack came up with at EXTJS. But it’s exceptional.

So instead of a solitary document sitting on his HD he has perhaps a dozen versions … each one of them subject to the silo mechanism of whatever platform he has used.

A vast improvement: 12 silos instead of 1.

“Synchronized web” is the newest buzz phrase I’ve found. But the need remains … the holy grail of semantic web … how do we order (i.e. index and access) loosely related documents?

That’s what I’ve derived with my thinking on “ participatory deliberation “: a mechanism to address (c/w on-page discourse) canonical versions of documents.

HeyHo … it’s so much more fun to play with sites like MyBlogLog than to hoe in with the work! *grin*

Also of interest. “ The Awesome Potential of the Semantic Web “, Marshall Kirkpatrick on an interview with BYU Phd student Yihong Ding . see also “ Top-Down; a New Approach to Semantic Web ” at ReadWriteWeb

p.s. http://www.netsquared.org … http://www.techsoup.org … http://openconcept.ca … nice to see folk doing good work.