id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
13499	CKBuilder Improvements	Steve James		"I think CKBuilder could be improved to make it more functional and less confusing to use.

(A) I would suggest redoing the Select Preset and Select Plug-ins section by combining them into a 7 column table as follows:[[BR]]

''Legend to my notation below...''

The ( ) at the top would be the radio buttons that would select a pre-set from the available columns. The checkmarks in the pre-set columns could be styled since they are for indication only.

The [X] would be simple checkboxes that everyone is familiar with--the checkboxes would be checked and disabled for plug-ins in the selected pre-set.  They would be enabled and could be checked by the user for plug-ins not in any pre-set.

The Category would be current colored tag icons that you currently are using.  

The Plug-in Name would be the current description and details and could be a wider column with this format than the one you are using, since this layout only needs one column across for the details.  Since it is compact, it would be easy to add other pre-sets in the future.
{{{
      Select A Pre-Set:
( )     ( )      ( )      (*)
None   Basic   Standard   Full   Plug-in Name     Category   Included?
======================================================================
         √        √        √     About CkEditor     Incl        [X]
         √        √        √     Accessibily Help   Incl        [X]
 .
 .
etc.
}}}

(B) Lastly, I frequently get confused about which panel is which for the language selections.  Why couldn't that just be a list of checkboxes for selecting the languages?  New flashier, looking UI controls are not always better... sometimes they are just flashy and confusing.  Frequently, the old tried and true (e.g, checkboxes) are what works best.
"	New Feature	closed	Normal		Project : CKBuilder		wontfix