Whats the word on the Safari progress?? on the web site you say:
"Safari has some limits that goes beyond the editing features and that are key things to make the editor work. For now, I’m stumbling across one of the most important limits: it is not possible to load scripts dynamically (used for custom configurations, plugins and the editor code itself). I've reported this problem to the WebKit developers."
But the new (nightly) builds of safari work corectly using the "LoadScript" files you provided when you submitted the bug.
So with that problem behind you where are we at??
"Safari has some limits that goes beyond the editing features and that are key things to make the editor work. For now, I’m stumbling across one of the most important limits: it is not possible to load scripts dynamically (used for custom configurations, plugins and the editor code itself). I've reported this problem to the WebKit developers."
But the new (nightly) builds of safari work corectly using the "LoadScript" files you provided when you submitted the bug.
So with that problem behind you where are we at??
RE: Safari progress?
1. the loading problem - IIRC, this had to do with script elements not having an onload event or an onreadystatechange event. as you say, this could be fixed in Safari, but even in the old Safari, it could be overcome by adding a "hey! this is loaded!" function call at the end of each dynamically loaded script (hard work, though...).
2. range selects. At the moment, Konqueror does not properly support range selects - you can get the text content of a range, but there is no easy way to figure out where in a document the selection came from. This can be overcome with a lot of code based around tracking where the mouse was clicked and where the drag ended, but again, this is a monstrously large job. I have submitted a bug for this to the KDE team, but there doesn't seem to be any rush for this one from them (they're probably too busy with more important things).
3. contenteditable. Konqueror does not support this atm. I bet Safari doesn't either. There is ongoing discussion about this, though. I expect there will be a push for it, once the major work of upgrading the KDE core from 3 to 4 is done. However, as KDE4 is due in November, that means that contenteditable will not be available until at least then.
In short - "can't be done yet".
Kae
RE: Safari progress?
But if the ability to work with selections and ranges doesn't work with Safari then I can understand that only a very little subset of the current functionality of FCKeditor (at least the interesting part) would be available in Safari.