Only for CKEeditor with WYSIWYG module?

Maybe later. For now want to get it working on CKEditor because TinyMCE has a goofball, nonstandard way of handling paragraphs.

Is there any vague roadmap for starting to expand this?

I wanted to use CKeditor, but the webkit bug was a non-starter for me.

Not really. I'm really wanting this to work with the WYSIWYG module, but the maintainers so far have declined to act on #735624: Enabling one button removes default editor toolbar. Until that happens, I don't see how to proceed in any sustainable manner.

As for other editors, their Drupal modules need to expose some API that allows this module to programmatically interface with them. I checked the CKEditor module, but it has no such feature. See #735632: Relation between plugins and toolbar buttons.

I'm confused why #735624: Enabling one button removes default editor toolbar is a show-stopper for this. The UI setup issues with WYSIWYG are a pain, but not a showstopper on this functionality.

The point of this module is to increase GeSHI usability. But the current status of the WYSIWYG module means:

• Enabling anything, even just one new button, causes the entire default toolbar to disappear.
• Reassembling a toolbar is kludgy:
  • Requires picking new buttons out of a checkbox list.
  • Impossible to sort buttons. Button order solely determined by position in this list.
  • Impossible to group buttons. All buttons appear next to each other; cannot add separators or spacers.
  • Cannot have multiple lines of buttons. All buttons appear in one line at top of editor box.

It is impossible to create anything close to the usability of CKEditor's default toolbar. This is an unacceptable usability regression, caused by a module whose sole purpose is to increase usability!

It's not yet clear if or how the WYSIWYG maintainers will fix this problem. Until then, I don't see the point of further development of this module.

I read that issue, and it seemed very clear that they intend to solve the problem. However, it is a very complex issue, and one which is likely to take a while to be realized.

I appreciate you wanting to defend the effectiveness of WYSIWYG UX, but I think that's a problem for the WYSIWYG module maintainers. What I want is to be able to easily sit down to TinyMCE or CKeditor and make use of Geshi. I'm less concerned with the admin hoops I need to step through (I don't use the defaults anyway), than I am with having the text rendered to the screen the way I want.

The usability problem will be steadily reduced over time, but I am more concerned with satisfying my end-users than having an easy WYSIWYG config. I cannot use Geshi without this functionality.

In short, please concentrate on the Geshi integration with WYSIWYG. Leave the WYSIWYG admin usability to that project.

I agree that "effectiveness of WYSIWYG UX ... [is] a problem for the WYSIWYG module maintainers." However, WYSIWYG's customized toolbar usability flaw constrains this (WYSIWYG - GeSHi bridge) module's effectiveness.

I disagree that "...it seemed very clear that they intend to solve the problem." Unless something is lost in translation, sun and TwoD don't think the issue is important. They both tried to shut down, minimize, misinterpret, or mis-assign the issue. It's left open but with "minor" importance.

I am a part time graduate student "over traditional age" with a family, full-time job, and other things going on. I wanted this to support my research work. The cost/benefit ratio for me is skewed because this module's minimal benefit, due to the WYSIWYG usability problem, does not offset the high personal cost of time spent developing this module.

Once there is clearly a path towards resolution of #735624: Enabling one button removes default editor toolbar, I may pick this back up. In the meantime, I'd be happy to invite others to contribute.

Alright. I read that issue, and it looked to me like a bad miscommunication. They have a specific game plan to address this effectively, it will just take a while. I did not understand any of your proposals as actually being workable within the existing architecture and direction. That's just my reading.

Since the default toolbar is not actually the assumed standard practice, I don't see it as a big deal to turn on all the needed buttons. I would like that to include Geshi, but Codefilter will do the trick for now. For me the concern is simply using Geshi with the WYSIWYG. Would be nice if I could sort it out with Markdown too. ;)

Thank you for getting this project started, and I look forward to it eventually building up momentum again.

Going to mark this as "won't fix" unless someone points out another module that this should tie in with.