[OWW-SC] fyi: wysiwywiki...

[Bill Flanagan]

There is a current FCKEditor 'autosave' plugin available. This plugin
sends the entire frame back to the server on a periodic basis. The
server application must take responsibility for then updating a
'persistent cache' with the content.

I'll track it down and load it to see how it works. It's not clear how
well it works with the MediaWiki support. I'll submit a request on the
development wiki site to see what they have to say about it.

Talk about killing 2 birds with one stone...

I'll let you know what I hear.

B.



On Nov 15, 2007 10:50 AM, Austin Che <austin at csail.mit.edu> wrote:
>
>     I agree this is great. And there is a preference option under
>     editing to turn on/off the rich text editing and the rich editor
>     tab for using it in some namespaces. I see no reason not to turn
>     it on by default immediately and let whoever wants to disable it
>     manually do so. Only by making it the default will we be able to
>     find and iron out all the bugs with it.
>
>     Also, I think the one remaining absolutely critical feature for an
>     editor is auto-save. This would probably be a separate extension
>     but I would like to see something like the following:
>     When the page is closed without saving (I think javascript can
>     detect page close as some websites pop up bunch of things on page
>     close), the edited text should automatically be sent to the server
>     via an ajax request and stored in a separate table. Upon the next
>     time I try to edit the same page if an unsaved edit is there, it
>     should either ask me what I want to do or bring up a box with my
>     previous edits so I can choose whether I want to restore it.
>
>
> > You can switch back and forth between the two formats. Also, you can
> > tag pages or individual sections/namespaces to use this as the default
> > editor. Although not done yet, you could also allow it to be set as a
> > user preference.
> >
> > On Nov 14, 2007 6:30 PM, Jenny Nguyen <jennytnguyen at gmail.com> wrote:
> >> That so sooooo cooool!!! I love this! Although I do admit, after typing in
> >> wiki-code for so long, converting to a completely wysiwyg format is a little
> >> difficult. It does make the wikicode look strangely formatted too, but I'm
> >> sure these type of bugs can be tweeked.
> >>
> >> Niiiice work Bill. That is really neat.
> >>
> >>
> >>
> >>
> >> On Nov 14, 2007 5:20 PM, Bill F <bill.altmail at gmail.com> wrote:
> >> >
> >> >
> >> >
> >> > I've installed a copy of OpenWetWare's data onto a preliminary version
> >> > of the FCKEdit OpenSource development team's HTML editor/Wikitext
> >> > editor.
> >> >
> >> > This work is NOT a sanctioned activity by the MediaWiki team. The
> >> > project is run by the FCKEdit folks.
> >> >
> >> > Their original integration was not good. With little to no support
> >> > from the MediaWiki developers, they've already created a great set of
> >> > features.
> >> >
> >> > Here's a pointer to OWW running with FCKEdit:
> >> >
> >> > http://www.openwetware.org/fck
> >> >
> >> > It looks pretty useful. But there are a slew of problems with it that
> >> > need to be fixed. Even with this caveat, this is as close to a bona
> >> > fide WYSIWYG editor for MediaWiki as anyone has done to date.
> >> >
> >> > This site is a separate database. Any changes made to it will be held
> >> > in this and not the main database.
> >> >
> >> > The HTML table editor built into it is very good. Images are a bit
> >> > complicated at this point.
>
> --
> Austin Che           <austin at csail.mit.edu>          (617)253-5899
>
> _______________________________________________
> OpenWetWare Steering Committee Mailing List
> sc at openwetware.org
> http://mailman.mit.edu/mailman/listinfo/oww-sc
>