WYSIWYG

[Ted]

That must be new, then.  Before it used a goofy xml schema to populate the styles box.  If it does regular css parsing now, then it could be quite worthy...

[gnolen]

Noop, it is not really new...But I think the xml thingy is only used to display the css inside the wysiwyg(so people can see how it looks directly) but outside it is put in as a normal div with a class. REALLY handy for quotes and all the rest!

So, try it and consider the fact...it is the best one!

/ Gnolen

[iNSiPiD]

It is the most user-friendly but it also uses a naff XML file for the style includes in the drop-down menu (as wishy indicated).

Like most WYSIWIGs it also feels th eneed to rewrite your code, especially plugin and module tags. I understand the eay to avoid this is to use single quotes to wrap things in.

I'm also led to understand that this rewrite option can be disabled and that you can customise the toolbar to show as little or as many buttons as you like. Unfortunately a thorough lack of documentation has not made this possibe for me yet. It's still the best choice so far though.

I reckon this one should ultimately be hacked for CMSms and a few options added to handle the above. SImple or advanced toolbar. Validate or not. Etc.

[gnolen]

But the XML is still just in the backend and it is really easy to set that it doesn't rewrite anything in the settings...

[iNSiPiD]

gnolen, what's the good in being a CSS Know-it-all if you're not going to share your knowledge??

I've made numerous changes to the settings AND the XML stylesheet (setting an alternative URL for my stylesheet was inappropriate for my needs because I wanted to restrict users to just a few styles). The problem is that none of the chnages seem to stick.

I refreshed and cleared my browser cahce (something which I HATE doing because it takes me months to get all those wonderful cookies back) and STILL the old styles appear and STILL it rewrites my lovely source code.

In the words of a much unloved Australian politician, "please explain...".

Thank you, my friend.

[gnolen]

iNSiPiD....I am surely not a CSS knowitall! And I do not want to make things worse for people with my trial & error approche.

But what exactly are rewritten for you? The whole page or just the content?

Can't you even put a new class into your content with fck?

If you put for examle:





into your modules\FCKeditorX\FCKeditor\fckstyles.xml and then mark something with the class(in the dropdown) in the wysiwyg  and save..

And then just put your .testclass in your default stylesheet with some attributes surely things happens right!? Or maybe this is not the problem for you?

/ Gnolen

[iNSiPiD]

Hi gnolen,

My problem to date has been to set the config so that it doesn't rewrite any explicitly entered source code. Also, I can easily edit the XML stylsheet for dropdown but this is not ideal as it often involves clearing the browser cache before you can see the changes. FCK should use a standard CSS and allow you to simply replace it or point to one of your own. Apparently this can also be achieved through the config but I've not been able to achieve any of these things satisfactorily.

[megabob3]

As i did in this day seem that problem of cache there isn't.

You can see it
http://www.awakening.it/cms_d/admin
User: admin
Pass: admin

trying to modify a contet and after a news, in this two cases the STYLESHEET it's different, as is different for the TWO pages.

FCK realod each time "fck_editorarea.css" and the styles change, it don't use the cache of "fck_editorarea.css".
Same for "styles.xml".