Return-Path: Delivered-To: apmail-lenya-user-archive@www.apache.org Received: (qmail 78379 invoked from network); 30 Apr 2009 03:13:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 30 Apr 2009 03:13:45 -0000 Received: (qmail 97101 invoked by uid 500); 30 Apr 2009 03:13:45 -0000 Delivered-To: apmail-lenya-user-archive@lenya.apache.org Received: (qmail 96954 invoked by uid 500); 30 Apr 2009 03:13:44 -0000 Mailing-List: contact user-help@lenya.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@lenya.apache.org Delivered-To: mailing list user@lenya.apache.org Received: (qmail 96946 invoked by uid 99); 30 Apr 2009 03:13:44 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Apr 2009 03:13:44 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ifranty@gmail.com designates 74.125.92.26 as permitted sender) Received: from [74.125.92.26] (HELO qw-out-2122.google.com) (74.125.92.26) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Apr 2009 03:13:37 +0000 Received: by qw-out-2122.google.com with SMTP id 5so1147337qwd.5 for ; Wed, 29 Apr 2009 20:13:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=+zLsWAIurDsFO7ew9MD8q93sITkcdmwcl8SSkpYAFTI=; b=ayv/3lYBoQW2KvGoG/JqC/BTsbN7E44XT3pRIYM8DGJdCwJ+xFSRyBnL06BIftYO6i T47FjK4mA4T5yd0f3XA5fqRqoVqvZ5qOuYNRBM4j+SBBp1x2riYUAWqvoSfc36EaliPw mS72SqV16e1A8sfqhixwokvB2tpBxGzoemo1s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=pZ0w5r9znlCy4n8s6+K//C0FZKysrdIAwAEA/rZZ3ESbDGe8lCKMT9Cip91Ox2pDRG c6aNIHoiGFyyH/d/CYWQ01b5EtDa9rOxnGCd1e0kaoI83XHGlnEAD6XUBE0Ee/fi8NXG hST/2Z1GIA7BnA3EBD90CQtaQSVgs/M6Zxn7M= MIME-Version: 1.0 Received: by 10.220.98.70 with SMTP id p6mr2273888vcn.13.1241061196167; Wed, 29 Apr 2009 20:13:16 -0700 (PDT) In-Reply-To: References: Date: Thu, 30 Apr 2009 11:13:16 +0800 Message-ID: Subject: Re: Release 2.0.3: Kupu / TinyMCE / FCKEditor From: hongbing cheng To: user@lenya.apache.org Content-Type: multipart/alternative; boundary=0016e64763d8bdfbd90468bd1312 X-Virus-Checked: Checked by ClamAV on apache.org --0016e64763d8bdfbd90468bd1312 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit IMO, we can make use of the give-and-take of these editors. Cheng 2009/4/30 Rudolf Korhummel > > Hi everyone, > > > > this question has been raised in a thread on the dev list, but IMO it's > > important enough to be discussed in a separate thread on the user list. > > > > I hope we all agree on these facts: > > > > * We need a 2.0.3 release asap. > > * The Kupu integration has serious issues which can't be resolved > quickly. > > * We shouldn't neglect the IE users. > > > > So, assuming that neither delaying the release nor fixing the Kupu > > integration are valid options, which course of action should we take? > > Some suggestions (not mutually exclusive): > > > I think having a document describing the editors situation for new users > would be import. > > > > 1. Just release, add the known issues to the release notes. > This may be be a frustrating experience for new users, because some will > try before they read the documentation (-0) > > 2. Move Kupu to the contributions area, release without Kupu. > > 3. Move Kupu to the last position in the "Edit" menu. > 2 or 3 is ok from MPOV. 3 maybe better, because we still have Kupu users. > > 4. Promote FCKEditor (menu item with link to the install instructions) > > 5. Promote TinyMCE (menu item with link to the install instructions) > > I've no experiences with this editors, because we use custom tags and the > xml validation was importend for us. But we can add the experiences from > other users to the documentation. > > > 6. .... > > > Rudolf > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org > For additional commands, e-mail: user-help@lenya.apache.org > > --0016e64763d8bdfbd90468bd1312 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
IMO, we can make use of the give-and-take of=A0these editors.
=A0
Cheng=A0

2009/4/30 Rudolf Korhummel <= ;rudolf@korhummel.de><= br>
> Hi everyone,
>
> this question has been = raised in a thread on the dev list, but IMO it's
> important enou= gh to be discussed in a separate thread on the user list.
>
> I= hope we all agree on these facts:
>
> * We need a 2.0.3 release asap.
> * The Kupu integration= has serious issues which can't be resolved quickly.
> * We shoul= dn't neglect the IE users.
>
> So, assuming that neither de= laying the release nor fixing the Kupu
> integration are valid options, which course of action should we take?<= br>> Some suggestions (not mutually exclusive):
>
I think= having a document describing the editors situation for new users
would = be import.
>
> 1. Just release, add the known issues to the= release notes.
This may be be a frustrating experience for new us= ers, because some will
try before they read the documentation (-0)
> 2. Move Kupu to the contributions area, release with= out Kupu.
> 3. Move Kupu to the last position in the "Edit"= menu.
2 or 3 is ok from MPOV. 3 maybe better, because we still ha= ve Kupu users.
> 4. Promote FCKEditor (menu item with link to the ins= tall instructions)
> 5. Promote TinyMCE (menu item with link to the i= nstall instructions)

I've no experiences with this editors= , because we use custom tags and the
xml validation was importend for us. But we can add the experiences fromother users to the documentation.

> 6. ....
>
Rudolf


-------------------------------------------------= --------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For addi= tional commands, e-mail: user= -help@lenya.apache.org


--0016e64763d8bdfbd90468bd1312--