On Fri, Jan 28, 2011 at 11:29 AM, Christian Lohmaier <lohmaier+ooofut...@googlemail.com> wrote: > Hi Michael, > > On Thu, Jan 27, 2011 at 5:45 AM, Michael Wheatland > <mich...@wheatland.com.au> wrote: >> We really need a path forward on this, probably should have had >> resolution of this major bug prior to selecting Silverstripe as the >> CMS. > > Bullshit again. During the evaluation period I had a demosite from the > very beginning, invited people to check it out and compare the > feature, show up limitations, etc. > > You didn't take the chance obviously, and are now complaining the > loudest, despite several NL-teams, the LibreOfficeBox team, etc. all > coming along nicely with the editor.
I was not involved with the initial setup, as the understanding was that we were moving away from silverstripe in a short time. This was a communication misunderstanding that was addressed earlier. > I see you take the chance to bash silverstripe and in that way push > support for drupal, but please don't do it so obvious. > > Raising issues with silverstripe is OK, but you should avoid starting > to go to bashing mode right away. I stated I don't want to spark up the CMS debate again. See below. I am raising concerns which need to be addressed with the current system, and referencing LibreOffice team developments that have worked as specified: CKEditor. >> I don't really want to spark up the CMS debate again. So I hope I am >> totally incorrect and it is very easy to change editors. > > No, there is no need to change editors. As none of the editor choices > in drupal were even close to being usable. I completely disagree. The implementation of CKEditor by Carlos Jenkins was nothing less than masterful. The editor worked exactly as it was designed without interference by the systems UI. Some drag and drop from the desktop features and pasting rich text worked perfectly. > Again: What "breaking of content" please. > >>here's a little screenrecording of image handling with chromium >>browser. I don't see the problem. >> >>http://pumbaa.documentfoundation.org:7780/assets/cloph/imagehandling.ogv >>(3.7MB) Although I appreciate the screencast of the things that do work, I was raising the things that don't. I have put together a screencast of the options which I have found so far: http://www.wheatland.com.au/sites/default/files/files/BrokenEditor.ogv The two features which currently don't work is editing the image properties via the right click menu and inserting a table. As far as I can see, the UI that Silverstripe injects into TinyMCE does not have image options for border, links, vspace or hspace which is needed. I would appreciate a reduction in the stonewalling and ridiculing my legitimate concerns. I am not trying to attack your work, I am raising concerns which need to be addressed for the system to work for all contributors. Michael Wheatland -- Unsubscribe instructions: E-mail to website+h...@libreoffice.org List archive: http://listarchives.libreoffice.org/www/website/ *** All posts to this list are publicly archived for eternity ***
