I'm trying to integrate the new editor in my CMS. It works fine and looks great until now, but there are still some questions:
1.) In the API doc I found this about CKEDITOR.config.baseHref:
The base href URL used to resolve relative and absolute URLs in the editor content.
Doesn't matter what path I set here, it looks like it has no effect. The only way I got images to show up, was by giving them a absolute URL... 
Lets say my editors path is http://localhost/web01/cms/editor.php
but the images in the HTML content to edit has their root at http://localhost/web01/upload/
so it should work after I set myeditor.config.baseHref = 'http://localhost/web01/upload';
but it has no effect... Any ideas?
2.) In the document where CKEDITOR is created, I set for HTML and BODY the height with css to 100% => html, body { height:100%; }
Then I was trying to get the editor to full height with this: myeditor.config.height = '100%';
But this will not work... Any idea why?
3.) Is there a way to get rid of the border around CKEDITOR?
If I have a textarea (or div element) with e.g. 500px width, and this is replaced by an instance of CKEDIT, I would like to have the inner editable width again exactly 500px, and not shrinked by this border...
Any idea how to do this? Do I have to make a new skin for this?
Thanks for tips and help!
Skywalker
Re: Some questions regarding CKEditor 3.0
my workaround for now looks like this:
bofore I pass the content to the editor, a PHP routine changes all relative path to absolute path for all resources (even to images in the CSS file, like background-image:url(<path>);
And before saving the editors content back to database, I do the reverse changes...
Although it works it's not a nice solution: When you open the image dialog, there is the long absolute url shown. Also when you pass back a image from your file/image selector, you have to add a absolute url - not very nice at all, but it works at least...
Hope this helps,
Peter