-
1. Re: Adopting CKEditor 4
rruss Feb 11, 2014 10:33 PM (in response to Lukáš Fryč )Do you guys think there is any value in providing Ace (the open source, source code editor used in Cloud 9) as a component?
Just curious, really.
-
Original Message -
From: "Lukáš Fryč" <lukas.fryc@gmail.com>
To: richfaces-dev@lists.jboss.org
Sent: Tuesday, February 11, 2014 7:58:46 AM
Subject: Adopting CKEditor 4
Hey guys,
I have evaluated CKEditor in version 4 as we are going to update in
RichFaces 5.
Note: RichFaces 4 use CKEditor 3.x
The issue is tracked here:
https://github.com/richwidgets/richwidgets/issues/175
Notable additions:
=============
CKEditor now has new inline mode which works with contenteditable
areas http://ckeditor.com/demo#widgets
Caveats:
======
Skins:
---------
The skins known from CKEditor 3 are NOT part of CKEditor 4.
There is a new Moono skin that is the only one that is bundled with a
distribution. There is a ported Kama style that isn't part of
distribution.
I think we should go with this default option and see whether it
poses a problem for our users. If they want, they can always attach
any other skin.
Cheers,
~ Lukas
_______________________________________________
richfaces-dev mailing list
_______________________________________________
richfaces-dev mailing list
https://lists.jboss.org/mailman/listinfo/richfaces-dev
-
2. Re: Adopting CKEditor 4
bleathem Feb 12, 2014 3:40 PM (in response to Lukáš Fryč )On 14-02-11 06:58 AM, Lukáš Fryč wrote:
I have evaluated CKEditor in version 4 as we are going to update in
RichFaces 5.
The issue is tracked
Great stuff Lukas, I look forward to see how this will simplify the
RichFaces codebase.
Notable additions:
=============
CKEditor now has new inline mode which works with contenteditable
Very cool! This will be a popular use case I'm sure!
The skins known from CKEditor 3 are NOT part of CKEditor 4.
There is a new Moono skin that is the only one that is bundled with a
distribution. There is a ported Kama style that isn't part of
distribution.
I think we should go with this default option and see whether it poses
a problem for our users. If they want, they can always attach any
other skin.
+1. Let's get the widget incorporated as a first start, and re-visit
skinning of the editor on a 2nd pass (likely post 5.0).
-
att1.html.zip 1.1 KB
-
3. Re: Adopting CKEditor 4
bleathem Feb 12, 2014 3:43 PM (in response to rruss)On Tue 11 Feb 2014 07:33:06 PM PST, Rodney Russ wrote:
Do you guys think there is any value in providing Ace (the open source, source code editor used in Cloud 9) as a component?
Neat! I definitely think that would make a good addition to our widget
set. Let's track it with a future planned richwidget issue:
https://github.com/richwidgets/richwidgets/issues/177
Brian
_______________________________________________
richfaces-dev mailing list
https://lists.jboss.org/mailman/listinfo/richfaces-dev
-
4. Re: Adopting CKEditor 4
It definitely makes sense.
Note that Ace also powers alternative GitHub/Gist editing mode.
It seems it is targeted on "coders for coders" kind of projects.
On Wed, Feb 12, 2014 at 4:33 AM, Rodney Russ <rruss@redhat.com> wrote:
Do you guys think there is any value in providing Ace (the open source,
source code editor used in Cloud 9) as a component?
Just curious, really.
----- Original Message -----
From: "Lukáš Fryč" <lukas.fryc@gmail.com>
To: richfaces-dev@lists.jboss.org
Sent: Tuesday, February 11, 2014 7:58:46 AM
Subject: Adopting CKEditor 4
Hey guys,
I have evaluated CKEditor in version 4 as we are going to update in
RichFaces 5.
Note: RichFaces 4 use CKEditor 3.x
The issue is tracked here:
https://github.com/richwidgets/richwidgets/issues/175
Notable additions:
=============
CKEditor now has new inline mode which works with contenteditable
areas http://ckeditor.com/demo#widgets
Caveats:
======
Skins:
---------
The skins known from CKEditor 3 are NOT part of CKEditor 4.
There is a new Moono skin that is the only one that is bundled with a
distribution. There is a ported Kama style that isn't part of
distribution.
I think we should go with this default option and see whether it
poses a problem for our users. If they want, they can always attach
any other skin.
Cheers,
~ Lukas
_______________________________________________
richfaces-dev mailing list