This release brings to public some amazing new features. Let's welcome the new dialog system, using floating elements with shadows and cool design. It is a high performance system bringing a nicer user experience, avoiding also the annoying warnings from popup blockers.
FCKeditor now supports document.domain. It means that a web site at http://www.example.com can use FCKeditor from assets.example.com. This is a must have feature for the professional environment.
Performance features are being introduced with the new inline CSS caching system, making it possible to avoid loading skins and styles from CSS files, reducing the number of requests to the server.
We have also a surprising new achievement included on it... let's leave it for the next news announcement
Have fun, with FCKeditor!
Mon, 02/25/2008 - 23:44
#1
Re: FCKeditor 2.6 Beta released
The new dialogs look great!!!
Thank you very much FCKTeam.
Regards,
Koen Willems
Re: FCKeditor 2.6 Beta released
Thank you very much!
I really like the new floating 'windows'
Keep up the great work!!!
Kind regards,
Han Smeets
Re: FCKeditor 2.6 Beta released
I would very much appreciate some documentation on the new dialog system. As far as I can see now, there's no way to reverse FCKeditor to the popup-based dialogs.
So, lots of us users need to rebuild our dialog-based plugins. Just some simple examples would suit fine!
And furthermore I would like to repeat myself: 'Wow, I like those new dialogs!!!!'
Regards,
Koen Willems
Re: FCKeditor 2.6 Beta released
Time for us to renew our "Beta" Donation...
Regards, Oliver
Re: FCKeditor 2.6 Beta released
Attachments:
Re: FCKeditor 2.6 Beta released
I've noticed that in firefox fck dosen't apear:|
And another thing. Earlier version wasn't comatible with opera 9, but I've changed in php code that it returns true and fck was on in opera.
When I'm doing it now fck doesn't apear at all.
ok it's plugin fault - sorry
Re: FCKeditor 2.6 Beta released
Is there any scope for getting the uploading dialog box using this too?
In general, the uploading dialog box needs some rethinking, and in particular needs formal usability testing work done. A lot of users I have come across in different organisations where I have deployed FCKeditor seem to experience exactly the same problems, and I often find myself giving out the same advice in terms of steps to carry out.
Points that immediately come to mind are:
1) The term 'Browse server' is unnecessarily technical. Sometime like 'Select an image/page or add a new one' would be much more outcome-orientated and less technical.
2) It would be good to replace the slightly clunky frames with divs using css overflow set to enable a frames-like feeling.
3) Also, I have often seen people click on the 'Browse...' tab to locate the file but don't realise they have to click on 'upload' which is often at the other end of the screen. I think an explicit instruction such as "Click 'browse' to select a file to copy from your computer to the website, and then click on 'upload' or similar is needed.
4) The location is lost when exiting the dialog and going back to it. Users expect the folder to remain the same rather being reset to the top-level.
5) The picture of the big folder at the top, with an arrow, seems to be button but does nothing.
6) Thumbnails would be very useful (though I realise there is a commercial competitor to this)
7) When a new file is added, it's not always easy to find it in a list. Perhaps the sort of fade effect used in Wordpress etc would work, so that the just-uploaded file is given a yellow background which then fades out back to white as normal.
8) On the API side, there remains a need for clash control, e.g. when the same filename is uploaded. I have submitted a patch for that for the PHP one. Ditto the need for regexp checking of the filename, e.g. to make users stop uploading files with spaces in etc.
9) Probably the biggest usability problem is that the uploading portion very easy to miss. I would recommend moving it to the top, with a clear '+' sign indicating 'Add a new item'.
I would suggest an explicit prototyping exercise to sort out the only really problematic section of the system.
I hope these are useful and constructive suggestions.
Re: FCKeditor 2.6 Beta released
Re: FCKeditor 2.6 Beta released
As many have already said - Very nice touch with the floating image/link insertion windows .
It seems, though, that when inserting images the "end tag /" has been omitted. It is in the small, I know, but it shows up as an error, when trying to validate my pages, where content is written using FCKeditor 2.6.
This is what W3C validator tells me:
You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".
This was not a "problem" in 2.5
Re: FCKeditor 2.6 Beta released
Re: FCKeditor 2.6 Beta released
Frederico Knabben
CKEditor Project Lead and CKSource Owner
--
Follow us on: Twitter | Facebook | Google+ | LinkedIn
Re: FCKeditor 2.6 Beta released
Re: FCKeditor 2.6 Beta released
Yes, as long as the Flahs elements have the wmode attribute set to "transparent" or "opaque".
Frederico Knabben
CKEditor Project Lead and CKSource Owner
--
Follow us on: Twitter | Facebook | Google+ | LinkedIn
Re: FCKeditor 2.6 Beta released
Has anyone been able to resolve the problem described here: http://www.fckeditor.net/forums/viewtopic.php?f=8&t=8711#p23169???
Re: FCKeditor 2.6 Beta released
Frederico Knabben
CKEditor Project Lead and CKSource Owner
--
Follow us on: Twitter | Facebook | Google+ | LinkedIn
Re: FCKeditor 2.6 Beta released
I must say I completely agree on EVERYTHING tallyce mentioned 100%. I have come accross the exact same problems myself and would be really happy to see these issues tackled, especially the "turning all popup dialogs into floating panels"...