First:
The FCKeditor project is a great project.
Second:
From my previous (mailing) contact with you I know you are a serious developer.
Then:
There are some serious issues (at least for me) I would like to get fixed before implementing FCKedtior
into my CMS project, and I might want to DONATE (give) you some money to get those
specific issues to be fixed. (have donated moeny earlier)
However:
I do not just want to donate money without knowing
if the money I donate will be used to fix the issues that are important for me to work.
Have tried for a while to get in contact with you without any replies.
Have tried to mail you using: fredck@fckeditor.net
This only gives me an autoreply answer which is of no use.
Have also tried to mail you using: fredck@fredck.com
No answer. It might be that you have tried and it got lost in bulk folder, i do no not know....
I DO NOT use the mailaddress given to me by sourceforge.
So then I will try here:
Issue 1.
Delete/Backspace/CTRL+x not working without first changing content in FF.
Have checked this in the buglist (BUG 1242979) and there is no word here if
the bug is being worked on or not.
Are this beeing worked on?
When is it expected to be fixed?
Issue 2.
Working with DIV's behaves differently and sometimes do not work in FF and IE (only tested in those two).
Here are my class definitions and styles definition for others to try as well.
Classes for DIV's put in the .css file:
.divtest-left { padding: 20px; font-family:arial, sans-serif; font-size:12px; width: 50%; background-color: #aaaaaa; color: black; }
.divtest-left a { color: black; text-decoration: underline; }
.divtest-left h3 { margin:0; padding:0; color: #ffff44; font-family:arial, sans-serif; font-size:12px; font-weight:bold; }
.divtest-right { display:inline; float:right; padding: 5px; margin:0; font-family:arial, sans-serif; font-size:10px; width: 50%; background-color: #448844; color: white; }
.divtest-right a { color: white; text-decoration: underline; }
.divtest-right h3 { color: #44ffff; }
Definition in fckstyles.xml:
<Style name="Title H3" element="h3" />
<Style name="LeftContainer" element="div">
<Attribute name="class" value="divtest-left" />
</Style>
<Style name="RightContainer" element="div">
<Attribute name="class" value="divtest-right" />
</Style>
DIV's when using IE:
I write some text in the editor area, then select the text and select the LeftContainer style.
A div (first level div) is created around the text with the class applied to it. So far so good.
If I click on/in div for the first time then a nice border is shown to indicate that the DIV is selected.
This is nice. When I click twice above some text in the DIV then cursor is placed within the text
and I can start to write and eventually move around using the arrow (keyboard) buttons or select using SHIFT+arrow
buttons.
If I select a div, I can drag the div and its content around within the editor area. This is nice. ( and would be
nice to have for FF as well (I'll guess this is a browser issue but do not know)).
I CANNOT select text by left-click and drag (that would be nice to do if possible, is this a browser limitation or not?, probably not since works in TinyMCE).
IT does not look like the inline and float works as it should for first level div (you have to change the class to see this),
text are not wrapping around the div if inline and float are applied.
Okay, if I now write some more text inside my newly created div, then select that text and then select the RightContainer style.
A div (second level div) are now created within the first DIV. So far so good.
I CANNOT edit any text within the second level div.
IT does not look like the inline and float works as it should. Text are not wrapping around the second level div.
When I select a DIV and I scroll that DIV outside the top border or bottom border of the editor area then the markings around
the DIV is visible outside the editor area and floats on top of other elements in the page. This is annoying.
When I select a DIV and I scroll that DIV outside the top border so the DIV markings gets above the editor buttons then the
editor buttons that is within the DIV markings are not clickable. THIS is not so good.
DIV's when using FF:
I write some text in the editor area, then select the text and select the LeftContainer style.
A div (first level div) is created around the text with the class applied to it. So far so good.
It is easy to edit text within the DIV. It is possible to select text by dragging the mouse.. great (It should work like this in IE as well).
Not possible though to mark the whole DIV and drag it around in the editor area as it is in IE, but
that is not that important though.
IF I now try to write some text either before or after DIV that is not possible. Unable to
place the cursor outside the DIV in editor area. (Note: to reproduce this you must not have entered any other text
or line breaks outside the created DIV in the editor area).
Okay... I enter a couple of linebreaks at the end of the first DIV that I created. Then I write a couple of lines, and select
those lines, and select the RightContainer style from the style dropdown.
A div is created and class applied. Great.
Text is easily editable. Great.
THE div continues above (below) the the bottom border of the first DIV and this is not good, if I remove the float attribute then the DIV displays
correct within the outer div.
TEXT in the first div does not wrap around the second floating div.
Other DIV stuff:
As you can see I have created a style for the H3 tag "within" the styles above.
I have found that using IE and FF to insert H3 tags within my DIVS behaves somewhat differently.
Inserting a H3 in IE using style dropdown and the format dropdown:
Writing a line in the beginning of the text in the first (outer DIV), then select that line,
then select the H3 (tag) from the styles dropdown applies the H3 tag only to the selected text. Which is what I wanted. nice.
BUT inserting the same H3 tag using the format dropdown applies the H3 tag to all the text in the DIV .
Why is this behaving differently. In my opinion they should not. I might be wrong.
If I use styles or the format dropdown to apply the H3 tag, only the styles H3 shows when I place
the cursor in the text between the H3 tags and not the "Heading 3" from the format dropdown.
Inserting a H3 in FF using style dropdown or the format dropdown behaves the same (in FF), and the H3 tag
is only applied to the selected Text (this I like).
When placing the cursor within the text between the H3 tags the H3 style shows in the
styles dropdown and in the format dropdown.
Note:( In TinyMCE it is possible in IE to mouse-drag to select text within a DIV. so this might be possible in FCKeditor as well... ??)
If it is not possible to mouse-click and drag to select text and
keeping the ability to select the whole DIV and drag it around, I think I would prefer the ability to
select the text with mouse-left-click and drag in IE and skip the DIV selection.
In my opinion it is better if it works the same in FF and IE. Maybe some others do not agree... okay... maybe possible to
control this behaviour in fckconfig.js in the future.
Issue 3:
BODY styles:
I want to make it possible for my users to change the BODY styles (read class) on the fly.
The best way for me would be to let the users create their own classes as I did for the DIV's in the beginning of my post.
(The user defined classes are stored in a database and in externaly generated .css file.
Then I would display those (particular BODY) styles in a dropdown outside (or inside) FCKeditor.
NOTE: it is BODY styles in FCKeditor but not in my populated pages where it is styles (class) applied to a DIV container.
When the user then select one of those styles I would like the BODY styles for the editor area to change accordingly without having to refresh the page.
Okay... have not done much testing on this one except that I know how to apply the default styles for the editor area.
But with this kind of body styling it is a bit awkward to change each of the body style attributes one by one in javascript and would
be MUCH better (IMHO) and easier if it was possible to define a class for the BODY tag and then be able to change/switch the class
by using javascript.
***** End of issues ******
All testing using FCKedtior 2.0 Final on Windows XP with FF 1.06 and IE 6.0.
As I said before:
I'm willing to give money to the project but then only if I know if you use that money to do the above,
and if it is doable at all and with a timeframe.
But then I need to get in direct email-contact with you as well.
Might be that DIV's are not supposed to be used toghether with the FCKedtior.
I hope this is not the case and that you will and have time to work on these issues.
Best luck with the project, it rocks.
The FCKeditor project is a great project.
Second:
From my previous (mailing) contact with you I know you are a serious developer.
Then:
There are some serious issues (at least for me) I would like to get fixed before implementing FCKedtior
into my CMS project, and I might want to DONATE (give) you some money to get those
specific issues to be fixed. (have donated moeny earlier)
However:
I do not just want to donate money without knowing
if the money I donate will be used to fix the issues that are important for me to work.
Have tried for a while to get in contact with you without any replies.
Have tried to mail you using: fredck@fckeditor.net
This only gives me an autoreply answer which is of no use.
Have also tried to mail you using: fredck@fredck.com
No answer. It might be that you have tried and it got lost in bulk folder, i do no not know....
I DO NOT use the mailaddress given to me by sourceforge.
So then I will try here:
Issue 1.
Delete/Backspace/CTRL+x not working without first changing content in FF.
Have checked this in the buglist (BUG 1242979) and there is no word here if
the bug is being worked on or not.
Are this beeing worked on?
When is it expected to be fixed?
Issue 2.
Working with DIV's behaves differently and sometimes do not work in FF and IE (only tested in those two).
Here are my class definitions and styles definition for others to try as well.
Classes for DIV's put in the .css file:
.divtest-left { padding: 20px; font-family:arial, sans-serif; font-size:12px; width: 50%; background-color: #aaaaaa; color: black; }
.divtest-left a { color: black; text-decoration: underline; }
.divtest-left h3 { margin:0; padding:0; color: #ffff44; font-family:arial, sans-serif; font-size:12px; font-weight:bold; }
.divtest-right { display:inline; float:right; padding: 5px; margin:0; font-family:arial, sans-serif; font-size:10px; width: 50%; background-color: #448844; color: white; }
.divtest-right a { color: white; text-decoration: underline; }
.divtest-right h3 { color: #44ffff; }
Definition in fckstyles.xml:
<Style name="Title H3" element="h3" />
<Style name="LeftContainer" element="div">
<Attribute name="class" value="divtest-left" />
</Style>
<Style name="RightContainer" element="div">
<Attribute name="class" value="divtest-right" />
</Style>
DIV's when using IE:
I write some text in the editor area, then select the text and select the LeftContainer style.
A div (first level div) is created around the text with the class applied to it. So far so good.
If I click on/in div for the first time then a nice border is shown to indicate that the DIV is selected.
This is nice. When I click twice above some text in the DIV then cursor is placed within the text
and I can start to write and eventually move around using the arrow (keyboard) buttons or select using SHIFT+arrow
buttons.
If I select a div, I can drag the div and its content around within the editor area. This is nice. ( and would be
nice to have for FF as well (I'll guess this is a browser issue but do not know)).
I CANNOT select text by left-click and drag (that would be nice to do if possible, is this a browser limitation or not?, probably not since works in TinyMCE).
IT does not look like the inline and float works as it should for first level div (you have to change the class to see this),
text are not wrapping around the div if inline and float are applied.
Okay, if I now write some more text inside my newly created div, then select that text and then select the RightContainer style.
A div (second level div) are now created within the first DIV. So far so good.
I CANNOT edit any text within the second level div.
IT does not look like the inline and float works as it should. Text are not wrapping around the second level div.
When I select a DIV and I scroll that DIV outside the top border or bottom border of the editor area then the markings around
the DIV is visible outside the editor area and floats on top of other elements in the page. This is annoying.
When I select a DIV and I scroll that DIV outside the top border so the DIV markings gets above the editor buttons then the
editor buttons that is within the DIV markings are not clickable. THIS is not so good.
DIV's when using FF:
I write some text in the editor area, then select the text and select the LeftContainer style.
A div (first level div) is created around the text with the class applied to it. So far so good.
It is easy to edit text within the DIV. It is possible to select text by dragging the mouse.. great (It should work like this in IE as well).
Not possible though to mark the whole DIV and drag it around in the editor area as it is in IE, but
that is not that important though.
IF I now try to write some text either before or after DIV that is not possible. Unable to
place the cursor outside the DIV in editor area. (Note: to reproduce this you must not have entered any other text
or line breaks outside the created DIV in the editor area).
Okay... I enter a couple of linebreaks at the end of the first DIV that I created. Then I write a couple of lines, and select
those lines, and select the RightContainer style from the style dropdown.
A div is created and class applied. Great.
Text is easily editable. Great.
THE div continues above (below) the the bottom border of the first DIV and this is not good, if I remove the float attribute then the DIV displays
correct within the outer div.
TEXT in the first div does not wrap around the second floating div.
Other DIV stuff:
As you can see I have created a style for the H3 tag "within" the styles above.
I have found that using IE and FF to insert H3 tags within my DIVS behaves somewhat differently.
Inserting a H3 in IE using style dropdown and the format dropdown:
Writing a line in the beginning of the text in the first (outer DIV), then select that line,
then select the H3 (tag) from the styles dropdown applies the H3 tag only to the selected text. Which is what I wanted. nice.
BUT inserting the same H3 tag using the format dropdown applies the H3 tag to all the text in the DIV .
Why is this behaving differently. In my opinion they should not. I might be wrong.
If I use styles or the format dropdown to apply the H3 tag, only the styles H3 shows when I place
the cursor in the text between the H3 tags and not the "Heading 3" from the format dropdown.
Inserting a H3 in FF using style dropdown or the format dropdown behaves the same (in FF), and the H3 tag
is only applied to the selected Text (this I like).
When placing the cursor within the text between the H3 tags the H3 style shows in the
styles dropdown and in the format dropdown.
Note:( In TinyMCE it is possible in IE to mouse-drag to select text within a DIV. so this might be possible in FCKeditor as well... ??)
If it is not possible to mouse-click and drag to select text and
keeping the ability to select the whole DIV and drag it around, I think I would prefer the ability to
select the text with mouse-left-click and drag in IE and skip the DIV selection.
In my opinion it is better if it works the same in FF and IE. Maybe some others do not agree... okay... maybe possible to
control this behaviour in fckconfig.js in the future.
Issue 3:
BODY styles:
I want to make it possible for my users to change the BODY styles (read class) on the fly.
The best way for me would be to let the users create their own classes as I did for the DIV's in the beginning of my post.
(The user defined classes are stored in a database and in externaly generated .css file.
Then I would display those (particular BODY) styles in a dropdown outside (or inside) FCKeditor.
NOTE: it is BODY styles in FCKeditor but not in my populated pages where it is styles (class) applied to a DIV container.
When the user then select one of those styles I would like the BODY styles for the editor area to change accordingly without having to refresh the page.
Okay... have not done much testing on this one except that I know how to apply the default styles for the editor area.
But with this kind of body styling it is a bit awkward to change each of the body style attributes one by one in javascript and would
be MUCH better (IMHO) and easier if it was possible to define a class for the BODY tag and then be able to change/switch the class
by using javascript.
***** End of issues ******
All testing using FCKedtior 2.0 Final on Windows XP with FF 1.06 and IE 6.0.
As I said before:
I'm willing to give money to the project but then only if I know if you use that money to do the above,
and if it is doable at all and with a timeframe.
But then I need to get in direct email-contact with you as well.
Might be that DIV's are not supposed to be used toghether with the FCKedtior.
I hope this is not the case and that you will and have time to work on these issues.
Best luck with the project, it rocks.

RE: Open letter to Frederico Kaldeira Knabben
RE: Open letter to Frederico Kaldeira Knabben
http://sourceforge.net/tracker/index.ph ... tid=543656
RE: Open letter to Frederico Caldeira Knabben
Sorry for the misspelling of FCK name.
It should be Frederico Caldeira Knabben.
Looks like the FCK team has fixed the "editing startup problems when using FF" .. ref latest CVS.
That is great.
Also looks that is should be pretty easy to implement use of className on the BODY tag of the editor.
I really hope FCK can implement this in next version.
I would like it to work like this:
1.
Make it possible to optionally set a class for the body tag of the editor in the page that contains the editor, and eventually an ID if that is nessesary in order to change the class by using javascript after editor initialization.
2.
Make it possible to include a second .CSS file where these classes can be defined. And not as an internal css file, since it might be the developer / editor do not want those classes be visible in the style list (dropdown).
3.
Then it will be a lot easier for end users to switch the look and feel of the content as well as for developers to control the styling for the body tag.
e.g by displaying a dropdown with available classes for body outside the editor or eventually a new dropdown within the buttons area of editor.
4. This will make it a lot easier and cleaner to handle "container" (read DIV) related content. Which is how many CMS systems work.
For me (and I hope for a lot of others) this looks very dooable to implement.
What do you think FCK. Can we have this in next version?
THEN:
There is the DIV tag issues. I hope the issues here (see my inital post) can be fixed as soon as possible.
Would be nice if editing text within a DIV work as similar as possible in IE and FF.
1. Would be nice if possible to edit nested DIV's in IE.
Trying to edit a second level DIV within editor area in IE is not doable today.
2. Would be nice to be able left-click and drag to select text within a DIV in IE. Not doable today.
3. Would be nice to make text floating around a DIV if you use float:left/right on a DIV. Not working in either IE or FF today.
4. Would be nice to fix issue in FF where a DIV floats above and *** below *** parent DIV if DIV has a float:left/right attribute set.
5. Would be nice to fix the problem with markings of a ***selected*** DIV in IE displays above elements outside the editor area when scrolling the DIV up or down. This also disable the use of those buttons in the editor that is within the boundaries of the markings.
6. Would be nice to be able to select some text within a DIV and the apply a e.g. H3 tag to it either using the styles list (dropdown) or the format list (dropdow).
Well the H3 is applied today. But behaves differently by FF and IE (see my original posting).
7. When clicking on a DIV in IE then the whole DIV is marked. And it is draggable around in editor area.
This is a cool feature. For me it is much more important if it is easy to edit content within the DIV... like being able to left-click and drag to select text.
So if the two editing features for a DIV in IE is not combinable:
1. mark-and-drag to move around
2. left-click and select text.
Then I would prefer to loose the "mark and drag to move" in order to make "left-click and select text" work.
If so .. it will work similar in both IE and FF as well.
Hope someone can make this work in upcoming versions.
If that was doable ... then FCKeditor would be very close to perfect.
Best regards
RE: Open letter to Frederico Kaldeira Knabben
Will come back width more info when I have some.
RE: Open letter to Frederico Kaldeira Knabben
http://sourceforge.net/tracker/index.ph ... tid=543656
RE: Open letter to Frederico Kaldeira Knabben
RE: Open letter to Frederico Kaldeira Knabben
1.
Text ARE wrapping nicely around floating divs (sorry for previously giving wrong information about this).
2.
Regarding the problem with not being able to edit images inside a DIV, and not being able to select text within a DIV using left-click + drag with mousepointer.....
THIS happens as soon as you put a width attribute in the DIV styling.
Is this DIV behaviour fixable?
When will it be fixed?
RE: Open letter to Frederico Kaldeira Knabben
http://xinha.python-hosting.com/
http://www.fckeditor.net
http://xinha.python-hosting.com/roadmap
RE: Open letter to Frederico Kaldeira Knabben
>issues so every new user do not
>have to accidentially find them
>themselves......?
Hey,
it's a opensource project.
There is a bug section on sourceforge where you can post such bugs.
Currently it contains only two open bugs.
Perhaps you should consider posting these bugs there, then you (and all others) have such a list.
The idea in opensource projects is that the users also participate in development.
And participating in development does not mean coding, but also testing, reporting bugs, mainting websites etc.
Andr
RE: Open letter to Frederico Kaldeira Knabben
Thanks for your notes and tests. They are being very useful.
I would just like to leave some notes:
1. Due to performance issues, it is better to leave the editor control some of the editing features. This is the case of the Bold, Italic, Underline, Strike-Thought, Indent and Para Justifications.
There would be some way to make it cross-compatible. We could transform all <STRONG> and <EM> tags to <B> and <I> when loading the content in Firefox.
The "GeckoUseSPAN" configuration option is not recommended to be active because of the cross-compatibility issues. I'm also thinking about removing this option from the editor.
2. The nested DIV issue must be investigated. Your messages regarding it were very confusing and so things got complicated. Maybe a simple description of the problem would be nice, including some sample HTML. (a few lines).
All I can tell you is that this issue is a little hard to work on because of the intrinsic behaviors of the editor itself while editing.
Fortunately this is a problem faced by a very few users.
3. I ask you to always maintain our Bugs Tracker updated with your discoveries. The Bugs Tracker is used as the base of the bug fixing development (as you can see on the Whats New? docs.
4. I ask you and all users to not assign developers or priorities to the bugs and features requests entries. Those are settings that should be used by the development team only. I know that for you your bugs are very important, but maybe they are not so important to the developer sat right next to you.
5. You should continue using the Forums. I saw you have found many useful answers here and participation from other users. But please dont explicitly ask for my participation here (like the tile of this thread it is not adequate). Let the answers open to who wants and can give then. Ive already discussed about my participation in the Forums on other messages.
6. Regarding your mention about giving feedback to every message, test or report left by all users this is a community web site. Messages should be targeted to everybody. We have a big community and lots of users sending messages everyday the same thing for my e-mail address. So, if I would have to answer all message, there would be no time for developing and so, Ill leave you the answer to where I should concentrate my efforts. I only can guarantee direct answers to support subscribers.
Thanks again for your message. Best regards,
FredCK
Frederico Knabben
CKEditor Project Lead and CKSource Owner
--
Follow us on: Twitter | Facebook | Google+ | LinkedIn
RE: Open letter to Frederico Kaldeira Knabben
Regarding your thought to using the <b> and <i> tags instead of <strong> and <em> respectivley: I'd like to encourage you not to do this, and ask you to investigate <strong> and <em> for both IE and FF.
The reason for this is that the <b> and <i> tags are depricated in XHTML and are to be "repalced" with <strong> and <em>. Ideally, the code the editor generates should be able to validate.
Great work on the editor, Frederick!
--Christian
RE: Open letter to Frederico Caldeira Knabben
Thanks for your clarification. Best regards,
FredCK
Frederico Knabben
CKEditor Project Lead and CKSource Owner
--
Follow us on: Twitter | Facebook | Google+ | LinkedIn
RE: Open letter to Frederico Caldeira Knabben
Is this possible?
--Christian
RE: Open letter to Frederico Kaldeira Knabben
http://www.fakeimage.com/fakeimage.jpg
http://www.fakeimage.com/fakeimage.jpg
RE: Open letter to Frederico Caldeira Knabben
Thanks again,
FredCK
Frederico Knabben
CKEditor Project Lead and CKSource Owner
--
Follow us on: Twitter | Facebook | Google+ | LinkedIn
RE: Open letter to Frederico Kaldeira Knabben
RE: Open letter to Frederico Kaldeira Knabben
http://www.fckeditor.net
RE: Open letter to Frederico Kaldeira Knabben
From a semantic perspective, FCK in IE gets it right, and FCK in FF doesn't.
That said, is this the place to post such problems or are we better off posted them elsewhere? If so, where?
It's a great editor, and I want to do my part to make it better.
RE: Open letter to Frederico Kaldeira Knabben
RE: Open letter to Frederico Kaldeira Knabben
http://sourceforge.net/tracker/index.ph ... tid=543656
RE: Open letter to Frederico Kaldeira Knabben
window.onload = function () { switchClass(theclass) }
I'm seeking information to set the body.backgroundColor for the eEditorArea. I had this working flawlessly in v1.2.4, and have a mod working in Firefox but can't seem to get it working right for IE in v2.0.
This is an interesting thread. It seems essential that users be allowed to change the entire background color of the editorarea in a click, instead of just changing small spans of text by highlighting and changing.
Thanks, keep up the good work.