Hi,

>    - Integrate in to our sites without requiring CSS tweaks to get it
>    looking correct - this means no iframes.

IIRC gecko can only edit full documents. You need to create an iframe to have 
an area in a page editable.

>    - Produce strict XHTML every time without fail.

FCKeditor does that pretty good - it has some other drawbacks. I do like the 
architecture of FCKeditor. It is far from beeing as elegant as jQuery, but I 
still can easily extend FCKeditor with my own plugins, switch of internal 
functionality and replace it with my plugin-functions, etc.

>    - Be simple to use.

That is a very difficult thing. For me e.g. vi is realy simple to use. I have 
learned the commands and now I feel that most other editors are just 
unusable, because they lack some features I often use. You always have the 
problem that professional users have other needs in usability terms than 
occational users.

>    - Be quick to load and run.

OK, we need a XHTML-Generator for IE (which usually doesn't even produce valid 
HTML, but you can access the DOM), we need a user-Interface that is flexible 
enough to suit occational users as well as professionals, etc.

You simply won't get that in a fiew lines of code and every line of code needs 
to be loaded. 

Maybe you can increase startup-speed by using a package-system like jsPax, 
compress the packages (e.g. with deans packer or with jsquash) and load the 
modules on demand. You can also try to put all the images (toolbar-buttons, 
etc.) in a single file to reduce the number of HTTP-requests at startup-time, 
but then you need to interpret thet on the client side which might increase 
the js-code again.

> http://www.simpleweb-online.co.uk/stage/editor/test.htm

I think you are looking for something like 
http://www.appelsiini.net/~tuupola/javascript/jEditable/ with an extension 
for a rich text editor. I have been thinking of making the whole thing based 
on plugins. I have not had the need and time to really do it:

$.editable.plugins.GaleryEditor = function() {...}
$.editable.plugins.RichTextEditor = function() {...}

$('.editable').filter('.galery').editable({
        type:'GaleryEdior',
        bgcolor:'red',
        ...
}).end().
filter('.richText').editable({
        type:'RichTextEditor',
        inheritStyles:true,
        ...
});

It would be really cool if the RTE could also handle elements wich have 
another editor attached like a block. Like this:

<div id="myPageContent" class="editable richText">
        <p>asdf asdf asdf</p>
        <div id="internalGalery" class="editable gallery">
                <img ...>
        </div>
        <p>asdf asdf asdf</p>
</div>

So you could have a gallery somewhere in a RTE-element and in the RTE-mode you 
only can delete the whole galery, start the galery-editor or leave it. Since 
the RTE needs to copy the elements anyway for the iframe, it should be 
possible to cach all elements with an attached editor.

Christof

_______________________________________________
jQuery mailing list
[email protected]
http://jquery.com/discuss/

Reply via email to