And templates/transclusions, at least on the working ones I've looked
at. I think this is a hard problem for any client-side system, since
a true WYSIWYG editor would have to pull all transclusions and their
protection status as well as interpreting all the extension blocks.
The WYSIWYG would have to indicate that if you delete one element,
you lose a whole block of content. It would also have to indicate
that certain things aren't editable by the user.
Jim
On Nov 16, 2007, at 9:44 AM, Dan Thomas wrote:
The dilemma with using FCKeditor is
incompatibility/inaccessibility of
Mediawiki extensions.
On Nov 15, 2007 11:39 AM, David Gerard <dgerard(a)gmail.com> wrote:
On 15/11/2007, Paul Coghlan
<pcoghlan(a)usa.net> wrote:
Looking at the wiki in question I have to say
that the FCKEditor
might
indeed give easier control and a more MS Word-like UI but the
toolbars will
appear daunting to many non MS Office users. I was hoping for
something that
allowed what appeared to be inline editing without the many bells
and
whistles.
Hmmmmmmmmmm ... that makes FCKeditor or something like it sound a
really nice option for corporate intranets. (My current strong
focus.)
- d.
_______________________________________________
MediaWiki-l mailing list
MediaWiki-l(a)lists.wikimedia.org
http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
--
--
Dan Thomas
_______________________________________________
MediaWiki-l mailing list
MediaWiki-l(a)lists.wikimedia.org
http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
=====================================
Jim Hu
Associate Professor
Dept. of Biochemistry and Biophysics
2128 TAMU
Texas A&M Univ.
College Station, TX 77843-2128
979-862-4054