-
1. Re: Reworked Editor Component - clarification
Hey Matej,
good questions.
1) Skinning
For Alpha4 we have decided to do not re-introduce Editor skinning feature
as I think it's not as handy as I originally though during 4.3 development.
In fact getting the skin work was more trouble than actual benefits.
Little bit more context: There is no solid LESS-based CKEditor skin that
could we compile RichWidgets against.
With that said, I don't think it's worth the trouble. The Editor should
have just one skin and if someone wants to change it, he can use generic
CKEditor skinning feature.
2) Inline editor
..works in RichWidgets, but it is not exposed as JSF component setting.
There are several additional steps that needs to be done in order to get
this:
render a <div contenteditable=true> alongside the <textarea>
hide <textarea>
synchronize a content of editor to <textarea>
Again, I don't think it's a must have.
My opinion: let's see whether someone from our community would consider it
handy.
Cheers,
~ Lukas
On Thu, Mar 13, 2014 at 12:18 PM, Matej Novotny <manovotn@redhat.com> wrote:
Hello
As I am working on editor tests I came across several problem I need to
clarify:
1) Skinning
- This concerns more components than just editor, I heard that this will
be somehow reworked in RF 5 but I have no more specific information, could
you provide me with some please?
- Any test we create for newly developed components should NOT contain
tests for skins atm, is that correct?
2) Inline editor
- Is inline editor also a JSF component?
- If so, how do I create it in code? And furthermore is there any
functionality difference between inline and basic editor? (e.g. some
functions missing etc)?
>
Cheers
Matej
_______________________________________________
richfaces-dev mailing list
https://lists.jboss.org/mailman/listinfo/richfaces-dev