Table of Contents
Ideas Bin
Feel free to place any idea you may have for the project in this page. Just give it a title and let's have fun.
Collapse / Expand one Row of Toolbar
It would be ideal to have toolbar rows that can contract/expand independently of each other. Or, better yet, have two versions that can be toggled back and forth. It would also be nice to remember this setting in a cookie, too.
Any thoughts on this? Best way to implement?
There are some thoughts about it for version 3.0. I've been thinking about some kind of toolbar configurator, where users can remove/add buttons to the toolbar. It would be available in a new toolbar context menu, which may also have an option to switch between two (or more) toolbar sets.
This one certainly deserves a dedicated ticket. Feel free to open one for it, so we can discuss it there.
Java Server component
FCKeditor should offer world class support for Java server frameworks such as Servlets and JSP! Please check the Java Server component page for details and discussion of the Java integration.
Bug reporting
I think that it would be a good idea to provide a link in the http://dev.fckeditor.net/wiki/Bugs page so that people can check their problems with a version running the current SVN code, so if someone tries to report a bug that it has been fixed in SVN but it still isn't available in the current public version then he can avoid filing a bug that will be closed, and it can help also for the people to test the latest code without the need to learn anything about SVN.
Nice idea. Actually the "Nightly Build" is the thing we need here.
Until now, the nightly was generated based on the SF SVN. Now we must do that from svn.fckeditor.net. The only thing is that the current SVN is dedicated to development. It doesn't include the compressed scripts and has some unneeded files for public distribution (the nightly is also downloadable). So, we need a new releaser that can be run automatically to generate the nightly.
Ticket #86 has been opened for that job.
FredCK
Plugins
A good solution to help people find out if something they want is available as a plugin would be to have a page (properly linked in every place where it does fit) that can show the current plugins categorized, for example:
- Extra tags
- Support for marquee
- Support for abbr
- Aditional features
- Char counter
- Universal Keyboard
- Path to node
- Example plugins
- Simple combo
- etc...
- whatever
The description of each plugin can link to a page where it's properly described, including screenshots, requirements, sample configurations, even a running demo based on the current code.
Doing these pages the right way it won't be easy, but having a list of know plugins properly categorized can help people to find out things that they have been missing.
Word-like Auto Formatting
When someone starts typing a list prefixed with stars (*) we convert it into a genuine bulleted list. There are other techniques, too, like turning '----' on a line by itself into a <hr>.
Why bother?
Some users don't know how to use the icons. Other users create lists with stars out of habit. And many users want to "keep using the keyboard" instead of switching to mouse mid-process. Offering key-combinations (such as control-?? for bulleted list) are nice for advanced users, but not for the common user.
Note: This is different from interpreting wiki markup in the editor. By coincidence, some of the formatting commands might match up, but the goal is really to "help" users by "doing what they meant" as opposed to making them learn a syntax and telling them to use it in the editor.
List of possible keywords for tickets
In order to be really useful I think that we should have a set of possible keywords so it's clear what to add and what not, have proper searches about that keywords.
Example in bugzilla: https://bugzilla.mozilla.org/describekeywords.cgi
Now people seems to put some kind of abstract from the bug report, not something that could be more useful to track the development.
Examples of keywords:
- IE: It affects Internet Explorer
- Gecko: It affects Gecko (Mozilla, Firefox)
- EnterKey : yes, now the Enter Key has its own component, just imagine something similar
- StyleSystem : For things related to the Style combo
- CantFix: We would like, but so far it doesn't seem possible. This way those bugs can be easily referenced.
- Pending: We need more info from the reporter
Ok, I've just updated the Trac Site page with an initial table of keywords. Suggestions are welcome.
