Last post Nov 20, 2005 10:51 AM by leupold
May 24, 2005 11:59 PM|Boskone|LINK
I have been watching the development of the FCK editor for a while and now that Fred has released the fc for version 2, I decided to try it out.
I was quite impressed with all the features of this editor so I created a html provider for DNN3.
You can download it here .The download is free but please register.
May 25, 2005 02:42 AM|ErikVB|LINK
May 25, 2005 09:35 AM|alexdresko|LINK
May 25, 2005 01:42 PM|mvermef|LINK
Boskone... check your link its slightly dead...
May 25, 2005 02:09 PM|codegalaxy|LINK
Havent looked at it but maybe someone looking at this thread could tell me - The RAD editor has a feature which allows it to expand as large as the browser window - nice for editing larger text elements - does FCK have anything like that I didn't see anything
on their site but you never know what I might have missed.
May 26, 2005 12:30 AM|bradoyler|LINK
May 26, 2005 03:11 AM|ErikVB|LINK
May 26, 2005 10:50 PM|locopon|LINK
May 27, 2005 05:08 PM|acorcutt|LINK
May 27, 2005 05:59 PM|DBuckner|LINK
May 27, 2005 06:04 PM|mvermef|LINK
May 27, 2005 06:41 PM|acorcutt|LINK
May 27, 2005 07:04 PM|DBuckner|LINK
May 31, 2005 05:25 PM|bradoyler|LINK
Jun 28, 2005 09:43 PM|ikamiksok|LINK
Jul 01, 2005 05:49 PM|dagilleland|LINK
Even if FCK editor is much better than FTB, the problem is it's license ... the
LGPL used by FCK is not very compatible with the DNN license ... Anyway, its not a real issue, its quite easy to swap editor providers ...
Oct 15, 2005 06:51 PM|ludis|LINK
Oct 15, 2005 07:57 PM|k4gdw|LINK
Oct 15, 2005 07:59 PM|locopon|LINK
Nov 17, 2005 05:46 PM|oledave|LINK
Nov 17, 2005 06:17 PM|xddg|LINK
Nov 17, 2005 06:59 PM|Presstopia|LINK
Nov 17, 2005 07:13 PM|leupold|LINK
While I applaud the effort, I find this provider unusable.
The main problem is that it takes 15 seconds to load every time you view an edit page.
The Editor Options interace is awful... constant postbacks, extremely confusing interface, ... I still can't figure out how to make it do what I want.
As the provider comes with full source and you are an experienced developer you can add improvements following your needs. Co-operation should lead to constant improvements.
Nov 18, 2005 09:53 AM|oledave|LINK
Nov 18, 2005 10:27 AM|Presstopia|LINK
The first recommendation would be to leave styles off the DNNDefault Toolbar Set. It just doesn't make sense for the vast majority of users and I also believe it is causing the slow load.
Nov 18, 2005 10:07 PM|locopon|LINK
Those features will be set as off by default on next release. So, people could have it simple and then add functionality as they want.
I tried to add all requested features to the provider, and I also tried to make those features with an enable/disable capability. So, you can have it as simple as just any default provider, or administrator can have more control under his hands.
Actual release is a test release, and the purpose of that "test" was to tune up some features. I am happy to find some comments here, because there was a lot of downloads, but most of them were finding all OK. Thanks to
Sebastian and Erik for all the good suggestions.
* The new dynamic styles feature will be disabled by default (Speed) and the possibility of setting it from the custom properties form.
* New filter based on regular expressions for improving a enabled dynamic styles
* Now, there will be a new feature to add the same styles to the editor area to improve the editing experience (thanks to Sebastian and his team on this)
* Image and Flash galleries will become complete template driven, so, many people could contribute with templates (Maybe one like the FTB, or maybe better)
* A lot of fixes
The custom properties form was created to dynamically add properties at a more granular level. Obviously it need some visual improvement, but IMHO it brings the provider many powerful features. So, you can have a simple editor for you forums and a powerfully
one for your registered users. Hope to see suggestions about visual disposition of it (We need to make it as compact as possible)
In ajax like implementation is planned to make this custom properties form better by using the new DNN api features, but it will be the next step after all the new features get more stable
Hope to find more and more comments....
B.T.W. Two more days for next release (tunning some features)
Nov 20, 2005 10:51 AM|leupold|LINK
thank you for pointing this out, we are sure, the provider gets better and better with every release. In a multiportal environment it is very important to be able to set styles according to the applied skin, so scanning the css files is a real improvement -
although speed needs to be kept in mind an can maybe optimized using caching in future versions. A filter for the style selector was a request by us, so we can filter all styles, that are not for use within module contents. Meanwhile, after testing your last
version, I would prefer to have another filter for css to be applied to edit area styles as well - as I get some unwanted background effects.
We tried to add WYSIWYG, as this was a demand by out customers with special fonts and backgrounds in the skins they use.
Can you explain, why compactness of the editor settings page is important to you - as it is only visible to admins, I cannot see the need. IMHO it is more important to be intuitive, what sometimes force to reduce/hide functionality or use separate setting controls
for the different options (I feel this need especially for toolbar settings and scope of settings).
Anyway I look forward to the next release, this provider is one of the mayor improvements of DNN in my eyes. Thank you very much!