I'm sorry I haven't been spending more time dealing with this, but like most developers I have a job that requires my attention as well. I got involved in this module because (again, like many other people) the issues with TinyMCE and direction it goes impact my projects. That hasn't changed. Drupal-id's last update was a complete surprise and since the since I've been implementing the module with modified .js themes, I didn't have the option of evaluating the code as part of my 9-5 gig. When I asked the people on this list for advice, most of the responses I received were less than helpful. I've downloaded, installed, and have been trying to find the time to test and compare all 3 versions (Moxie, 5.1, and what I've been calling 5.2). I've also been looking at the issue ufku has identified with the TinyMCE code and Drupal... not the modules, but the code all of these modules actually enable. I did try to contact Drupal-id after that latest update became the release and have been exchanging email directly with many of the developers who have been working with the .js themes. I've just launched my biggest project in beta yesterday and will spend some time today and tomorrow dealing with this. My goal was (and still is) to find a way to allow both .js customization per role/content type in the 5.2 versions while dealing with the immediate issues in the other versions, but I'm relatively new to Drupal module development and doing the "Drupal way". I think I might be one of the most informed people about all of the issues in all of the versions of TinyMCE enabling modules and I am willing to continue maintaining this module as time allows, but I understand the importance of error free WYSIWYG toolbars on Drupal's success. If there is someone who is informed and has more time wants to take over, I'm not opposed to that. I have no problem working with other developers, but my attempts to discuss my POV with Allie basically led to name calling. I use features from the previous version of 5.1 that I'd like maintained. If the Moxie group (and now possibly drupal-id) doesn't care about those features, then I agree with Dries and that modules should fork and the better feature set will win out. IMHO, including drupal-id in these conversations isn't productive. The responses I've gotten from Jonathan (and/or Wendy) have been less than productive. I understand that there is a language barrier, but the communication issues go beyond that. I would REALLY like to discuss this in some way other than email or in the issue queues with the people involved. Is anyone interested in finding the time for a multiuser iChat or Skype audio conference? ___ Kevin Reynen Integrated Media Coordinator Reynolds School of Journalism and Advanced Media Research University of Nevada, Reno On 2/15/07, Fernando Silva <fsilva.pt@gmail.com> wrote:
This is one of those "particular" moments, where Drupal core developers should step in, make a statement and enforce it. Drupal community must be able to trust, that when some difficult situations arise, senior developers will solve those situations.
Solution?! There is only one: * enforce a TinyMCE project only * create branches like other projects (4.7.x-1.0, 5.x-1.0, 5.x-2.0) * make those 3 guys work together. It does not make sense to have 3 separate (but similar) projects in the community.
And, no, I do not agree with Dries when he says "The best module will usually win, and the other module will fade away". In this particular case, "beginners" will only be confused and say: "which one should I choose? I need a feature from one of them, but the other is much more secure? In which one should I give some help?"
My vote is for the merge of TinyMCE and TinyMCE Plus, remove of Moxie. Deploy a stable 4.7 version for 5.x, and create a group where all ideas should be discussed for a 5.x (and 6.x) roadmap.
If this needs a core developer intervention! So be it!
Regards, Fernando Silva
On 2/15/07, Boris Mann <boris@bryght.com> wrote:
So, Drupal-Id is back over at TinyMCE Plus. And the TinyMCE javascripts are checked into CVS -- http://cvs.drupal.org/viewcvs/drupal/contributions/modules/tinymce_plus/incl...
So, I'm pretty confused as to where we are now * TinyMCE Plus, Drupal-Id back doing ??? * TinyMCE -- confusion, although I *think* we got agreement on 5--1.x as evolution of 4.7 code, and 5--2.x as the newer "compact" code with less UI -- Kevin as main owner * Moxie -- 4.7 evolution, Allie as lead, can probably go away if 5--1.x branch on "main" TinyMCE is OK
This sucks :(
-- Boris Mann Vancouver 778-896-2747 San Francisco 415-367-3595 Skype borismann http://www.bryght.com