Beginning with this version, the most recent content is served up with the page, instead of hitting the server with Ajax (unless you’re browsing the version history – F2). To keep integration as simple a possible, just like the Javascript initiates itself wherever it finds an element with class="Wiki", so to does the server-side code. By buffering the output and hitting a custom callback function, the server-side code displays the most recent content inside any HTML elements with class="Wiki". There’s no need for any PHP on the page except two lines at the top.
Let me know what you think of this technique. One of the downsides of using a buffer is a bit more work on the server before any content is sent back to the browser. Eventually, I’d like users to have three options to integrate ^edit with their sites. Each method will require using HTML elements with class="Wiki" and a unique id.
As always, all comments are mucho appreciated
I also prepared a "real-world" example for you this time so you can see it can do more than just a two-paragraph page
Demo v0.1.9 (Mozilla/Firefox, IE, Safari)
"Real-world" example (copied from the CBC)
Comments RSS Both comments and pings are currently closed.
I ran across this entry from technorati. It really looks like an interesting technique. But I can’t figure out what you mean from just this blog, and the URL doesn’t give me any hints about ways to get up the directory tree to figure out what you mean. I guess I’ll go try the root URL and see.
Damn, this is starting to work really well.
Thanks for your interest, Terry
I plan to write some documentation any day now, I swear
Essentially, so far I’ve been working on the editor javascript itself and I’m just now moving into the server-side implementation beyond the basic save/retrieval that it does now. I’d like to roll out a release that everyone can download and try themselves by v0.3.
What do you mean by “get(ting) up the directory tree”?
Cheers MrHappy!
[...] the last couple of months, Michael and I have been working on a mash-up of the technology behind my WYSIWYG wiki software, WhyYouShould, Facebook, Live, and Amazon S3. Our goal was to put the power of WhyYouShould towards [...]
[...] make the change, and its done. Jonathan was well on his way to creating the foundation of a real-time Content Management System. In 2006 in response to the increasing need to discover new was to use this exciting new tool, he [...]