click-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrian A. (JIRA)" <>
Subject [jira] Commented: (CLK-658) WYSIWYM (not WYSIWYG) Editor in click-extras or at least click-examples.
Date Tue, 25 May 2010 17:54:25 GMT


Adrian A. commented on CLK-658:

> The rate at which these libraries (or plugins) are created and abandoned is amazing.
Unfortunately this is the actual "state of the art", and it happened to Click a few times
What's even worse is that even the same JS library after a few versions is not backwards compatible
anymore - not like we are used in the Java world.

> For the majority of JS centric controls I think they should be pushed into third party
projects hosted elsewhere. 
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 :).

> WYSIWYM (not WYSIWYG) Editor in click-extras or at least click-examples.
> ------------------------------------------------------------------------
>                 Key: CLK-658
>                 URL:
>             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):
> 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.
> 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.

View raw message