Re: Which WYSIWYG Editor should we use as Default?Of course I picked up tinyeditor. 
Because it is highly configurable, but a bit outdated.
Can we see the results of the poll so far?
Re: Which WYSIWYG Editor should we use as Default?In XOOPS 2.4.0 Image Manager can be modulized...
I think that we have to divide Editors from Image Manager (the same image manager for all editors) like i wrote here: http://sourceforge.net/tracker/?func=detail&aid=2865026&group_id=41586&atid=430843
What about modulizing also editors? As Tinyeditor module?
Re: Which WYSIWYG Editor should we use as Default?Nearly all editors are working with plugins. So dividing image manager should be easy. tinyeditor supports 4 if every plugin is installed. But as told, the code is a bit outdated.
For flexibility reasons I would like to see editors as modules. There are more people able to update/maintain a module (when the developer gives up his project - like me) than the core devs adapting editors within the core.
What I always liked about tinyeditor was its flexibility. You can set toolsets and command sets for each group. You can give permissions, you can pass toolsets etc.pp.
Re: Which WYSIWYG Editor should we use as Default?My Favorites is the TinyEditor.
Re: Which WYSIWYG Editor should we use as Default?I think poll is just in time. In order to make an informed decision before casting your vote there need to be some report on each editor available for Xoops.
- compare on the functionality
- Compare on the stage of development,
>is it mature,
>is it still being developed actively,
>
*when i did a review a while back my concern was on image management for the site users.
- By default we should support an editor that provides most of the functionality. Then provide support for other editors, just in case there is a need for a basic/minor editor.
I think XOOPS should make a default editor based on these criteria, others may also add to this. XOOPS core should support the editor as well as module developers so the editor is standard across the board. Doing this will allow for the community to move ahead.
- The modular idea is good
- People should be able to download updated editors (from editor devs sites) and drop them in a directory ready to be called by modules which makes use of them.
Of course these editors may not be like desktop word processors, but I've seen CKEditor is one that provides the most functionality and better image manager.
Re: Which WYSIWYG Editor should we use as Default?Before I used Spaw, but after it was removed from XOOPS editor list I start to use tinymce and now I'm quite happy with it. I never try Spaw 2 so I don't know if it's better now or not.
Re: Which WYSIWYG Editor should we use as Default?I read this article before making my choice of TinyMCE over FCK-editor:
Evaluation of web based WYSIWYG-editors - test result
Re: Which WYSIWYG Editor should we use as Default?TinyMCE.
Re: Which WYSIWYG Editor should we use as Default?I forgot to wrote that I don't like in tinyMCE when it load background for edit area XOOPS background image. So if I have black background then I can't see what I'm doing. I would rather use white or some light grey color.
Re: Which WYSIWYG Editor should we use as Default?My favorite - at this time - is xinha because of the genius image- and filemanager!
Re: Which WYSIWYG Editor should we use as Default?Quote:
I read this article before making my choice of TinyMCE over FCK-editor:
Evaluation of web based WYSIWYG-editors - test result
Can we see the results of the poll so far?
Re: Which WYSIWYG Editor should we use as Default?I think if user can select editor for all part of XOOPS is better ! but I test XOOPS 2.4 editors pack ! I think TinyEditor (Module by Frankblack) is better choose
Re: Which WYSIWYG Editor should we use as Default?Quote:
I don't want to influence the voting, so let's wait till the voting is over.
Re: Which WYSIWYG Editor should we use as Default?Quote:
How is that going? Do you believe that someone is registering more often to influence the poll?
Re: Which WYSIWYG Editor should we use as Default?Personally I like xihia as it is flash. I think Java is over rated. With nothing more than performance issues on slow computers. But you know it is upto the vote... So vote now..
I have one more editor as well called NiceEditor it is a longie editor for tiles..
ie.. Others
##############################
##############################
##############################
##############################
##############################
##############################
ie NiceEditor
#############
#############
#############
#############
#############
#############
#############
#############
#############
#############
#############
#############
Re: Which WYSIWYG Editor should we use as Default?Quote:
I read this article before making my choice of TinyMCE over FCK-editor:
Evaluation of web based WYSIWYG-editors - test result
Re: Which WYSIWYG Editor should we use as Default?voted.
Not that I'm trying to complicate this with further suggestions...
but here's a small jquery editor (7kb compacted).
Re: Which WYSIWYG Editor should we use as Default?Quote:
Tinymce has for me the best options and ease. It is easy to eg format a table with even and odd coloured lines.
Re: Which WYSIWYG Editor should we use as Default?Tinyeditor by far !!!
But, hey FB ..... isn't it time for updates.
TinyEditor is much more then a wysiwyg, it's a whole editor/groups-permitions/graphics management/file management and a lot more ....
Should be a core module in my point of view, and maintain more seriusly.
This is a winning editor, and one of the best modules since XOOPS was born !!!
Re: Which WYSIWYG Editor should we use as Default?Thank you, thank you - far too kind (ralf57 have to earn the merits too). But I bet my ass, that tinyeditor won't make it!
Renewing the tinymce-engine would be no problem I think, but the xrmanager is a bit?! ancient regarding to coding. When it comes to javascript coding I am a bit lost (more than in php coding).
Re: Which WYSIWYG Editor should we use as Default?thanks frankblack
Re: Which WYSIWYG Editor should we use as Default?Hi Mamba,
Since you are on a neutral status on this topic. Is it possible to have a comparison of these editors? seems to be between TinyMCE & CKEditor, is there a third one. Let's Look at licensing, and functionality, maturity, etc. Something like this table but with up-to-date releases. Its for the better of all not just one member. Thanks.
btesec
Re: Which WYSIWYG Editor should we use as Default?Quote:
Is it possible to have a comparison of these editors?
Re: Which WYSIWYG Editor should we use as Default?another one that people may not have seen... http://developer.yahoo.com/yui/examples/editor/imagebrowser_editor.html Dunno what implementing this would take.
I just give my users the XOOPS DHTML editor.. anything more is unnecessary 99% of the time.
However it does look a little old fashioned now so a simple standardised one to replace it would be good.
WYSIWYG Editor Poll closed - results are publishedOK, the poll is closed now, and the winner is: Find out here...
Re: WYSIWYG Editor Poll closed - results are publishedCongrats CK! I thought tinyMCE would make it. But only 74 votes?
Re: Which WYSIWYG Editor should we use as Default?In fact TinyEditor and tinymce is the same editor. Only the manner of adding it in the system differs and the addional configuration options from the module.
By using one of the two, 46% of the voting users would be be accomodated to their wish.
I voted tinymce, but won't care if it would be tinyEditor and I expext more or less the same for the TinyEditor voters when they get only tinymce.
I think the configuration options of Tinyeditor should be added as preferences to the core.
Because on second tought a WYSIWYG editor is also a security risk, so it is nice to have some configuration options, that can limit the functionality for some groups.
Re: CK Editor now availableHi from the results of the poll so far CK Editor is now available in the trunk as well as for download.
To Download CK Editor :: Click Here
Otherwise get it from 3rd Party from the Trunk!
Re: CK Editor now availableThank you, Simon! Very much appreciated!!!
Re: Which WYSIWYG Editor should we use as Default?I did not catch , you want use CK Editor or TinyEditor/tinyMCE ?
and you want add some option in Preferences or not?
I think using TinyEditor ( as module ) in XOOPS core is better solution 
Re: Which WYSIWYG Editor should we use as Default?Quote:
In fact TinyEditor and tinymce is the same editor. Only the manner of adding it in the system differs and the addional configuration options from the module.
I think the configuration options of Tinyeditor should be added as preferences to the core.
Because on second tought a WYSIWYG editor is also a security risk, so it is nice to have some configuration options, that can limit the functionality for some groups.
Re: Which WYSIWYG Editor should we use as Default?I'm here! I could do that, but ...
... it takes some time, because a lot changed since I made the last version of tinyeditor
... we need a good image manager, because the main/best image managers used in tinyeditor are not supporting Opera, because at the time of release designmode was not fully supported
... is it the wish of the community? I mean those, voted for tinyMCE, had tinyMCE in mind and NOT tinyeditor. Because perhaps they disliked all the chichi that comes with tinyeditor? I don't want to cause any trouble here. A choice is a choice and it was clearly CKeditor that won the poll.
Just my thoughts here.
Re: Which WYSIWYG Editor should we use as Default?Quote:
... is it the wish of the community? I mean those, voted for tinyMCE, had tinyMCE in mind and NOT tinyeditor. Because perhaps they disliked all the chichi that comes with tinyeditor? I don't want to cause any trouble here. A choice is a choice and it was clearly CKeditor that won the poll.
the wish of the community
.... that would be great .... well there's so many imageeditors now .... Ajax and so .... ) ... simply not comparable ...
Re: Which WYSIWYG Editor should we use as Default?Wow, do I have any choice NOT to update? But things seem to be more complicated then I first thought. I already tried to replace the tinyMCE engine, but the editor isn't working properly anymore, so I have to dig deeper ...
Re: Which WYSIWYG Editor should we use as Default?We'll be waiting
Re: Which WYSIWYG Editor should we use as Default?You have to! Fixed the part for rendering the textareas, but the toolsets have to be written anew.
But maybe part of this re-write could be used elsewhere? My problem was that the same javascript was loaded twice.
With a snippet of javascript the double load could be prevented:
<script type="text/javascript">
if (window.tinyMCE === undefined) {
var head = document.getElementsByTagName("head")[0];
script = document.createElement("script");
script.type = "text/javascript";
script.src = "'.XOOPS_URL.'/modules/tinyeditor/editor/'.$tinyededitor_load.'";
head.appendChild(script);
}
script> Re: Which WYSIWYG Editor should we use as Default?Does the new version of TinyEditor is released for XOOPS 2.5?
| Stats | |
| Goal: | $15.00 |
| Due Date: | Nov 30 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $15.00 |
 |
|