[ 
https://issues.apache.org/jira/browse/CLK-658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12871431#action_12871431
 ] 

Bob Schellink commented on CLK-658:
-----------------------------------

Reality is that we cannot host everyone's favorite component. We need to draw 
the line somewhere. The whole idea behind Click was to build a Component 
oriented framework. That means third-party developers should write components. 
Nothing about that says *all* components must be written and hosted here. If 
you look at other component frameworks a big part of their attractiveness is 
around third-party components. There are already multiple corporates shipping 
third-party JSF components. Wicket is also expanding in this area. Here are 
some good examples:

http://code.google.com/p/wiquery/
http://code.google.com/p/jolira-tools/

> The problem with that is that third party projects tend to get out of sync 
> and poor docs - and than the user has the "component nightmare" a la Tapestry 
> or JSF :).

The component nightmare arises because developers loose interest in maintaining 
them. If I have to maintain all these components I'd loose interest too.

> WYSIWYM (not WYSIWYG) Editor in click-extras or at least click-examples.
> ------------------------------------------------------------------------
>
>                 Key: CLK-658
>                 URL: https://issues.apache.org/jira/browse/CLK-658
>             Project: Click
>          Issue Type: New Feature
>          Components: examples, extras
>            Reporter: George Stan
>
> Add a WYSIWYM (not WYSIWYG) editor control to Click Extras (or at least 
> Click-examples):
> http://en.wikipedia.org/wiki/WYSIWYM
> For many usage scenarios, it holds much better results than a WYSIWYG (this 
> was my experience too), so in many cases when
> a TextArea is used, a Click WYSIWYM Editor would have much better results.
> http://www.wymeditor.org/ would be one possible solution (and it has MIT 
> license too).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to