Rich text inline editing

Noah Botimer botimer at
Wed Nov 19 20:06:23 UTC 2008

I'm way behind here, but I have a paranoid question (caveat: I have  
not played with this code)...

How does this start/stop rich text editing play with loading times /  
memory issues?  I'm generally aware of some nasty non-cleanup stuff  
with these editors (leaving script objects and markup hanging  
around), especially as iframes navigate around, especially in IE.  Is  
there anything to worry about here?


On Nov 17, 2008, at 11:37 PM, Steven Githens wrote:

> Hi Again,
> Just had a go playing around with the TinyMCE and FCK versions of the
> Inline Editor from Fluid Trunk.  The FCK one works great as well  
> and I'm
> excited about it being a good transition for existing Sakai  
> Deployments
> that have customized FCK Plugins and it just generally being used  
> in all
> the tools.
> Will these be in Fluid 0.6, or not until 0.7 ?
> Thanks,
> Steve G
> Antranig Basman wrote:
>> Steven Githens wrote:
>>>> I don't see why you couldn't easily plug FCKEditor in as an
>>>> alternative. We can walk you through the process if you're  
>>>> interested
>>> I've been thinking about this too and wanted to vote+=1.  I know  
>>> TinyMCE
>>> is better and being used in all the research for next generation  
>>> Fluid
>>> and Sakai stuff, but I think we'll definately need it to not be  
>>> super
>>> difficult to use this with other Rich Text Editors. ( I think a  
>>> little
>>> difficult would be ok ;)    )
>> We will make it easy to work with everything.
>>> In addition to Lovemore, I know at least a few other groups that are
>>> doing this same thing manually and would probably love to use the  
>>> Fluid
>>> one as soon as it's ready.  For any medium timeline deliverable that
>>> needs to get dropped into Sakai 2.5 or 2.6 and look like the rest  
>>> of the
>>> system, there is a strong likelyhood it will need to be able to  
>>> use FCK.
>>> Also, I don't how easy it is to swap implementations across the  
>>> system
>>> in Moodle (probably a bit easier than Sakai), but their default is
>>> typically HTMLArea, so I imagine they would need to the ability  
>>> to use
>>> that too in order to match the rest of the system.
>>> Mega cheers,
>>> Steve
> _______________________________________________________
> fluid-work mailing list - fluid-work at
> To unsubscribe, change settings or access archives,
> see

More information about the fluid-work mailing list