-
1. Re: help with rich:editor and LoadScriptStrategy NONE
nbelaevski Jan 9, 2010 4:34 AM (in response to cdollar393)Hi Chris,
You should save .xcss files together with all linked images and put them as .css in your project.
-
2. Re: help with rich:editor and LoadScriptStrategy NONE
cdollar393 Jan 15, 2010 4:14 PM (in response to nbelaevski)Hi Nick,
Thanks for the reply.
Saving the .xcss and all the linked files won't be very easy if I want to support multiple skins... won't I have to create a .css file for each skin in that case?
Using LoadScriptStrategy NONE and LoadStyleStrategy DEFAULT works for me with all the richfaces components except for rich:editor -- is this a bug with richfaces not supporting this?
Chris
-
3. Re: help with rich:editor and LoadScriptStrategy NONE
cdollar393 Jan 21, 2010 11:36 AM (in response to cdollar393)bump
Can anyone suggest a strategy to save the css and other files for the editor? The method I tried didn't work...
Thanks!
-
4. Re: help with rich:editor and LoadScriptStrategy NONE
gaboo Feb 5, 2010 10:45 AM (in response to cdollar393)Any luck about that ? We have the same problem, we'd like to use the NONE strategy, but then it's very hard to make rich:editor work. -
5. Re: help with rich:editor and LoadScriptStrategy NONE
cdollar393 Feb 8, 2010 7:36 PM (in response to gaboo)I had to stop working on getting NONE working for a while, but I should be back trying to get it working soon. I was experimenting with different values for LoadStyleStrategy in addition to setting LoadScriptStrategy to NONE, and I think I was making the most progress setting LoadStyleStrategy to ALL and then still manually copying over the missing TinyMCE bits that were being requested.
I'll update the post here if I get it figured out... however, this still seems like a bug in RichFaces to me. All the other components seem to work fine when changing LoadScriptStrategy except for rich:editor.
Chris
-
6. Re: help with rich:editor and LoadScriptStrategy NONE
vineyard Aug 9, 2010 10:42 AM (in response to cdollar393)Hi Chirs,
We too have the same issue. Please let us know if you find a workaround for this.
Thank you.