Obout Editor Provider

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

Please do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.

This forum is for discussing mojoPortal development

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

You can monitor commits to the repository from this page. We also recommend developers to subscribe to email notifications in the developer forum as occasionally important things are announced.

Before posting questions here you might want to review the developer documentation.

Do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.
This thread is closed to new posts. You must sign in to post in the forums.
8/17/2009 5:08:24 PM
Mike Sigsworth
Gravatar
Total Posts 6
View Posts
If at first you don't succeed... it's likely that you missed something minor. Like an '=' that should have been an '=='. I always do that!

Obout Editor Provider

Hi Joe,

I am interested in using the Obout Editor in lieu of FCK, TinyMCE, etc.

How much of a challenge is it to add a new Editor provider?

8/18/2009 7:02:06 AM
Joe Audette
Gravatar
Total Posts 18439
View Posts

Re: Obout Editor Provider

Hi,

Its basically implement a control that wraps the editor then implement an adapter to configure it. Compile it into your own dll, put it in the bin and add an entry to mojoEditor.config or ideally copy that file rename it and then reference your custom file from user.config by override the setting:

<add key="mojoEditorConfigFileName" value="mojoEditor.config" />

that way you won't lose your custom settings on upgrades.

Note however that I'm currently working on improvements to our TinyMCE integration and I plan to make it the default for new installations as it will be our best one after the improvements.

I've already implemented our Content Templates and Content Styles and now I'm finishing up a new file browser for browsing/uploading images and other files. Its going to be very nice.

Best,

Joe

8/20/2009 11:58:51 AM
Mike Sigsworth
Gravatar
Total Posts 6
View Posts
If at first you don't succeed... it's likely that you missed something minor. Like an '=' that should have been an '=='. I always do that!

Re: Obout Editor Provider

The Obout editor is already a .NET control. FCKeditor and tinyMCE are javascript based controls, so there's lots of code in mojo to wrap them. 

Looks like I'll have to create a class OboutEditorAdapter : IWebEditor to allow for configuration but would it still be necessary to create an OboutEditor : Control, IPostBackDataHandler? Looks like this is just to wrap the javascript behavior of these editors.

Thanks for your help.

8/20/2009 12:01:04 PM
Joe Audette
Gravatar
Total Posts 18439
View Posts

Re: Obout Editor Provider

Yes, if its already a .NET control then probably you can just use it as it is and create the adapter to configure it/wrap it. 

You must sign in to post in the forums. This thread is closed to new posts.