• Do not register here on develop.twiki.org, login with your twiki.org account.
• Use View topic Item7848 for generic doc work for TWiki-6.1.1. Use View topic Item7851 for doc work on extensions that are not part of a release. More... Close
• Anything you create or change in standard webs (Main, TWiki, Sandbox etc) will be automatically reverted on every SVN update.
Does this site look broken?. Use the LitterTray web for test cases.

Item4555: It is confusing how the link is between WysiwygPlugin, TinyMCEPlugin and TinyMCEContrib.

Item Form Data

AppliesTo: Component: Priority: CurrentState: WaitingFor: TargetRelease ReleasedIn
Extension WysiwygPlugin Normal Closed   minor 4.2.0

Edit Form Data

Summary:
Reported By:
Codebase:
Applies To:
Component:
Priority:
Current State:
Waiting For:
Target Release:
Released In:
 

Detail

It is confusing - even for us experts - how the link is between WysiwygPlugin, TinyMCEPlugin and TinyMCEContrib.

Expecially the fact that a plugin needs to be installed but not activated.

Please look at the #twiki conversation below

[21:36] <ArthurClemens> Lavr: can you check if I am right with the action summary: http://develop.twiki.org/~twiki4/cgi-bin/view/Bugs/Item4536
[21:36] <Lavr> Looking right away
[21:37] <Lavr> Yes. And wysiwyg in the meaning TinyMCE
[21:38] <Lavr> The edit button already today is normal edit when TMCE is disabled. So you only need to add the Raw Edit with the condition that TMCE is enabled.
[21:38] <Lavr> My guess is that WYSIWYG goes away when you do not activate the old KUPU WYSIWYG.  I can try and confirm that right way.
[21:42] <ArthurClemens> Lavr: should Wysiwyg plugin be disabled? That is: replace all WysiwygPlugin buttons witl TinyMCEPlugin buttons?
[21:43] <Lavr> Arthur. As I understand Crawford. And have also just confirmed ... 3 line explanation follows
[21:43] <Lavr> TinyMCE plugin - when enabled - redefines the Edit button to mean TMCE Edit.
[21:44] <Lavr> WysiwygPlugin - when enabled - activates the WYSIWYG buttons which activates the old WYSIWYG button 
[21:45] <Lavr> The new thing we need is - The Raw Edit - When TinyMCE is enabled.
[21:45] <Lavr> When we distribute 4.2.0 the WysiwygPlugin will per default be disabled.
[21:46] <ArthurClemens> This means I will copy all Wysiwyg button stuff with TinyMCE stuff: about 8 lines will be quite similar
[21:50] <ArthurClemens> What I don't get is that styling is (partly) done in WysiwygPlugin
[21:51] <ArthurClemens> So that seems a required plugin still
[21:52] <Lavr> Yes. TMCE needs WysiwygPlugin installed. But not activated in configure.
[21:54] <ArthurClemens> This will be very confusing
[21:55] <Lavr> I see that the Wysiwyg plugin is removed already from TWiki.spec  so it is included in the distribution but not activated. 
[21:55] <Lavr> And yes I agree - this is confusing.
[21:56] <Lavr> It would be better if the Kupu editor was enabled as a separate entiry and the WysiwygPlugin should be a Contrib.
[21:58] <ArthurClemens> I don't know if contribs can have lib files
[22:00] <Lavr> Hmm. I don't know. I guess Crawford will clean this up eventually. Right now I am sure his main focus is to get TMCE to work.
[22:01] <Lavr> But yes people will enable the Wysiwyg Plugin thinking that they need to do that to get TMCE to work.
[22:02] <Lavr> I will copy paste these words into a bug item with Normal priority
 
Not urgent. But confusing and should be addressed. I have no preference or suggestion for how.

-- TWiki:Main/KennethLavrsen - 05 Sep 2007

See the FAQ in http://twiki.org/cgi-bin/view/Plugins/TinyMCEPluginDev for more information.

CC

Yes. We understand now Arthur and I - after having experimented and read documentation. But it is still confusing for the admins that there is a WysiwygPlugin which needs to be deactivated - and yet you get Wysiwyg (with TMCE).

That is the confusing part.

It is not logical that a plugin is used and needed though it is deactivated. That is not how all other plugins work.

No documentation can save this. It is designed confusing.

But again - not urgent. Don't consider fixing this until after 4.2.0

-- TWiki:Main.KennethLavrsen - 06 Sep 2007

OK. Just as well, because to "fix" it requires a major refactoring, and I know how much you hate those!

CC

I'm closing this because no-one seems interested in helping out with the doc.

CC

I wonder what this last remark was all about??

The conclusion was that AFTER 4.2.0 we should consider packaging the contrib in a more logical way.

There is no documentation expected to fix this.

But actually - since we opened this bug report - things changed. We no longer ship the Kupu and the Wysiwyg plugin now needs to be activated along with TinyMCEPlugin. And this actually resolves the original confusing element.

So this one is not No Action. It is fixed. Closed. We are happy. Hurray!

KJL

ItemTemplate
Summary It is confusing how the link is between WysiwygPlugin, TinyMCEPlugin and TinyMCEContrib.
ReportedBy TWiki:Main.KennethLavrsen
Codebase ~twiki4
SVN Range TWiki-4.2.0, Wed, 05 Sep 2007, build 14735
AppliesTo Extension
Component WysiwygPlugin
Priority Normal
CurrentState Closed
WaitingFor

Checkins

TargetRelease minor
ReleasedIn 4.2.0
Edit | Attach | Watch | Print version | History: r6 < r5 < r4 < r3 < r2 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r6 - 2007-09-27 - KennethLavrsen
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback