Re: 2_1_X and editors

On 09/22/2010 09:19 PM, Rainer Schöpf wrote:
> Hello Florent,
>
>   >  Hi rainer,
>   >
>   >  On 09/22/2010 07:16 PM, Rainer Schöpf wrote:
>   >  >  On Wed, 22 Sep 2010 at 09:53 -0500, Richard Frovarp wrote:
>   >  >
>   >  >    >   We also were going to provide very clean getting started documentation
>   >  >  to
>   >  >    >   instruct people to install TinyMCE when they test. What is the status
>   >  >  of
>   >  >    >   getting the latest Tiny working with Lenya?
>   >  >
>   >  >  Tiny 3.0.8 is working for me, with the patch in
>   >  >
>   >  >     https://issues.apache.org/bugzilla/show_bug.cgi?id=49580
>   >  >
>   >  >  I'd like at least one person to confirm that before I checkin the patch.
>   >
>   >  I will try it tomorrow.
>   >
>   >  Can you provide the "New version of css file for tinyMCE popups" as a patch ?
>   >
>   >  I don't see very well where I have to put it.
>
> See https://issues.apache.org/bugzilla/show_bug.cgi?id=49580#c1
>
> For the time being, it goes into
>
>    src/pubs/default/resources/shared/css/lenyatable.css
>
>   >  (Begin note : I don't really know how editors works.)
>   >
>   >  As I read, it's seems that the css for tinyMCE popups is not in the tinyMCE
>   >  module. there is a way to put it in the tinyMCE's folder module and don't
>   >  have css somewhere else in the app ?
>
> Yes, that's open to discussion. I'm not entirely sure but I'm inclined to agree
> with you.
>
> The only tricky bit is to write the correct _relative_ URL in tiny_config.js and
> in the @import in lenyatable.css. I've just comitted new versions to Bugzilla.

Yes sure ! The path @import "../../modules/~~" seems strange on a first 
point of view ! :)

>
> Note that lenyatable.css has now to go into
>
>    src/modules/tinymce/resources/css/
>
> Another thing to note: this is meant to work together with TinyMCE version 2
> and 3. Since the names of the css files changed between version 2 and 3,
> lenyatable.css tries to @import both the old and the new file. Ie. one of these
> @import statements will result in an invisible 404 error when the browser tries
> to load the css file.
>
> There are several possible ways to handle this:
> 1) Leave it as it is
> 2) Keep seperate versions of the lenyatable.css file, for Tinymce version 2 and 3.
> 3) Forget about TinyMCE version 2
>
> Personally I have a slight preference for 3), but that might be a problem for
> people upgrading from an earlier version of lenya, but not upgrading TinyMCE
> from 2 to 3.

I prefer 3) too.

Maybe we can do this :
- Keep 1) for kupu 2 / 3 for 2.0.4 release
- do 3) for next 2.1.0 release

?

Thanks for this.
Some news tomorrow ! :)
++


>
>    Rainer
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]