Re: What should we focus on in the future development of TinyMCE
We have been thinking of putting up a Wiki to get some help with the documentation, but we haven't found any Wiki system that uses TinyMCE yet ![]()
TinyMCE Developer
Moxiecode Systems
We have been thinking of putting up a Wiki to get some help with the documentation, but we haven't found any Wiki system that uses TinyMCE yet ![]()
We have been thinking of putting up a Wiki to get some help with the documentation, but we haven't found any Wiki system that uses TinyMCE yet
And I doubt you will find one. Wikis do not use html so using TinyMCE would detract rather than add to a wiki.
Mind you, if someone were to write a custom theme and a complete set of plugins... :-)
Scott
Well an idea would be to use it like we use it on this forum, you edit in HTML, then before posting to backend, a javascript converts it to "wikitext", ive looked into it myself, but some of the regexp required to do the conversion is very complex, and im not an expert in regexps.
this would be terrific, there are wiki's for every possible language around (PHP, Perl, ASP, ASP.Net, etc... mySQL, MSSQL, Access,...) and some even have some basic editor toolbars... i'm sure some tinyMCE experts could make it the way afraithe says (like the toggle TinyMCE on posts).... this would for sure would boost the possible use of tinyMCE... what a nice idea, hopes it will get some people behind...
First of all I think that this sticky should be a seperate forum.
i would be happy have a plugin for inserting templates.
have a look to fckeditor to understand my wish.
That whould be really great. Insert code from a file just like tinyMCE inserts an image or URL (select a template file from a list and paste the code into tinyMCE).
The heavy users are not having that many problems, but the less-skilled (like me) are. I don't think it would hurt if there would be more examples and tinyMCE-for-dummies kind of information.
Yes, our main focus is "normal" users not hackes. They tend to use a plain text area box anyway and hack in their own tags.
But it's hard for us to make the manuals "noob" friendly since we are developers our self. The best would be if someone less skilled wrote a how to.
I agree that "normal" users are the main target audience of tinyMCE.
It's structure is a bit strange but all it needs is to play with it a little bit.
I strongly believe that studing examples is a much better way to really learn to use something than reading endless manuals which sometimes are not so user-friendly. So, what if someone turns this sticky into a new forum that will let every member to upload their own customized examples?
First of all I think that this sticky should be a seperate forum.
krokogras wrote:i would be happy have a plugin for inserting templates.
have a look to fckeditor to understand my wish.That whould be really great. Insert code from a file just like tinyMCE inserts an image or URL (select a template file from a list and paste the code into tinyMCE).
This is quite easy to do (I have already made one, that saves the editor content as HTML too!).
The easiest way to do this is to load the 'template' into an iframe, then use tinyMCE.setContent(html),
where html = document.getElementById("frameid").contentWindow.document.body.innerHTML;
(frameid would be the id of the iframe).
Yo obviously have a list of templates to choose from, in a predefined folder. I use a php script to read the folder nad subdirectories, and generate a link and name for the file, which are presented in a select list.
Just one tip - when using iframes with inlinepopups, you have to dynamically create the iframe when the you load the popup, otherwise it messes with the inlinepopup for some reason.
Ryan.
I would like to see AJAX enabled pluging
and
UNICODE support....
Use the PHP script if you can.
And try to show us an editor that loads less than 45-50kb and is as flexible and well written as TinyMCE.
I suggest implementing/using the trick http://wellstyled.com/css-nopreload-rollovers.html to minimize the number of images. We could do away with just one image for the entire menu.
P.S I love TinyMCE as is :-) The PHP script works great.
Afraithe wrote:Use the PHP script if you can.
And try to show us an editor that loads less than 45-50kb and is as flexible and well written as TinyMCE.
I suggest implementing/using the trick http://wellstyled.com/css-nopreload-rollovers.html to minimize the number of images. We could do away with just one image for the entire menu.
P.S I love TinyMCE as is :-) The PHP script works great.
TinyMCE already has functionality for a one-image toolbar button graphic (one image containing all toolbar button images).
Unfortunately, it only works in Firefox, since MS Internet Explorer freaks out when you try to use the trick. i.e., when you implement the "tiled" image, Firefox loves it, but IE ignores it and uses the individual images instead.
Hopefully IE 7 will fix this, but until then I don't think anyone has been able to figure out a cross-browser technique for TinyMCE yet.
The trick you linked to may be the seed of an idea, but itself does not provide the solution. A LOT more work is needed to adapt that approach.
Last edited by speednet (2005-11-17 16:00:55)
Actually, the problem in IE is that when you use the one-image thing and you have something ontop of the background image as well as your caching off, IE goes nuts and reloads all images all the time when you move your mouse around, quite effective, if you want to kill your webserver instantly.
Well an idea would be to use it like we use it on this forum, you edit in HTML, then before posting to backend, a javascript converts it to "wikitext", ive looked into it myself, but some of the regexp required to do the conversion is very complex, and im not an expert in regexps.
I'm currently starting a http://www.mediawiki.org/wiki/MediaWiki based Wiki for such documentation needs - working title "TinyMCE for dummies". Content would be documentation and how-tos written by TinyMCE users (yes, all those members from this forum) for TinyMCE implementers with not-so-good JS skills.
I hope to build up a lot of sample files (full source code included) and, when this thing lifts off, even try to implement "TinyMCE for WikiText"...
So, what do I wait for? Approval from Moxiecode (sent me a mail or post) and members interested in participating. At the moment I have a fun and sometimes hard time playing with MediaWikis skin and template system, but beside that, this wiki could go live anytime.
What do you, all of you, think? Please let me know.
I think its an excellent idea, we can definetly host it if you wish.
Ive actually talked to the MediaWiki ppl regarding WYSIWYG editing, their main problem is backwardscompatiblity, they have tons of gigs of info thats already stored in the crappy wikitext format. The conversion from Wikitext to HTML is no problem (all Wikis already does this when displaying data). What needs to be done, is a HTML to Wikitext conversion, tricky but not impossible. This should be done on the backend side with PHP.
So you would open the document with Wikitext, convert it to HTML using their internal converter, edit it in TinyMCE and when saved, convert it back from HTML to Wikitext. Problem is... this has to be PERFECT if its to become used by others than just "new" users of MediaWiki.
Apparently, there are some issues with stuff like templates etc in MediaWiki. We could certainly help out by constucting special plugins to handle special Wiki-type-actions, such as linking to internal documents etc.
Unfortunatly, we have very little time to look into this more activly right now, we are currrently under heavy load with several productions due before xmas.
I then assume that I might go forward and start this *new* Wiki at my host? I don't want to to alienate someone here, give me an email or post wheter this is OK for with you.
Later I could transfer all content to your official wiki? At least would let the TinyMCE community get started on the documentation front. Meanwhile, if I (or somebody else) find the time, I will have a look at PHPs PCRE module.
Sure, go ahead, ill make a sticky in the forum once it has some basic usefull content.
Call for duty:
If some members of this forum - both experienced and unexperienced - would like to work with me on the "TinyMCE for dummies" wiki, give me an email an I will mail you the link.
As soon as the wiki has some usefull content, I will publicly announce the Wiki here.
Update: I'm also looking for some native english tongue speakers for proof reading 'some' of the content
Last edited by donadoni (2005-11-17 18:13:20)
I would love to see a "Reset Dimensions" option under Image Properties in the context menu which is displayed when right clicking an image.
It would also be nice to have the link dialog automatically recognize email addresses so that the user doesn't need to know to put mailto: in prior to the email address.
Having a "none" or "deafult" option for the styles drop down which essentially performed "remove formatting" on the document would be great from a usability point of view. In cases where the default styles are assigned to the body/table/p tags and styles exist for only a couple things (eg. a title) it can be a bit of a hassle to try and remove the style. Sometimes selecting "-- Styles --" seems to clear it, other times it doesn't. I also have noticed times when a style somehow gets applied multiple times:
<p class="headline headline">dsafdfadsf</p>Related to this, it would be nice to be able to clear the formatting for a portion of text. For example:
<p class="headline">this is my headline</p>If you wanted to change the above so that only "my headline" was of the class headline, and the rest was the default you currently have to remove the entire class assignment, and then select the portion of text you want the class assigned to and re-assign it. Selecting "this is" and pressing clear formatting does not do anything.
It's hard to know what people want in future releases of TinyMCE. So I made a poll out of some of the key features I would like to add.
hi this is a test reply
spocke wrote:It's hard to know what people want in future releases of TinyMCE. So I made a poll out of some of the key features I would like to add.
hi this is a test reply
this is a 2nd test
for the sake of ordinary users, I just want to add plugins for inserting media object to be played directly on screen, in addition to flash and images, e.g. .wmv, .mov, . rm., mp3....
Anyway, I think tinymce is GREAT!
It's hard to know what people want in future releases of TinyMCE. So I made a poll out of some of the key features I would like to add.
In my opinion, one of the best feature with TinyMCE is that you can easily configure the tags and attributs you want (via the "valid_elements" option). That is very powerfull.
The problem, and I think I'm not alone to think this way, is that this process is linear : there is no possibility to choose the tags that can be nested within the other tags. This is the biggest problem to really comply XHTML.
What I propose is that, with the same approch, you could define the forbidden nested tags for each tag in a configuration option, separed into their types between :
- super block element (div)
- block element
- super inline element (span)
- inline element
- empty element
The W3C definition say that block elements can contain both block and inline elements, whereas inline element can only contain inline elements (there are tags exceptions, you can see them here http://blog.alsacreations.com/2004/09/0 et-enfants in french, sorry... no better link...)
I think that depending on the doctype, the rules are not the same for each tag. So you may have to choose your doctype.
At this moment, TinyMCE produce a mistake by forcing the insertion of <table> into <p>, and that is not correct.
This could be fixed with my solution.
I noticed some others demands about this problem that my solution can resolve them :
Nested tables
http://sourceforge.net/tracker/?group_i
id=1285513
http://tinymce.moxiecode.com/punbb/viewtopic.php?id=54
Nested lists
http://tinymce.moxiecode.com/punbb/view
hp?id=2155
Nested span
http://tinymce.moxiecode.com/punbb/view
hp?id=2132
The ability to configure the nested tags can give you the ability to exactly choose the content structure. For instance, if you don't want to see the <strong> or <em> tags into table headers <th>, you could simply set a rule like (th:!strong,!em), and the system handle it, and the cost of personalization is nothing. This can even be done by people who have no idea how to develop it into Tiny.
All right, hope you understood my idea...
m_axidea,
Excellent post! XHTML rules for nesting of elements is indeed one of the trickiest things to learn when going from HTML to XHTML.
One of TinyMCE's stated goals is producing proper XHTML, so I think this is a great suggestion. I suppose there are two ways to implement it: either as a flexible option, as you suggest, or as a standard part of the cleanup routines.
I would like if you say what files you make changes in. It should be writen in TinyMCE cangelog so i dont have to replace all files.
I always say, the success of any software is : Keep it simple. Dont add to much functionality, rather concentrate on stability. There are some posts here that takes the whole Wysiwyg in a complicated state ! This causes trouble. Keep it simple.
BTW, it is a great product and you guys deserve respect.
I would like the ablility to insert php code into it. like with dreamweaver there is a small icon on the page where the PHP code is. then when you view the source the code is there. When you enter php now it is gone when you return to the HTML editor, because the editor doesnt know how to read it. Im not talking about exicuting the code, just making it sit there for editing.
It would be nice to have this more user friendly. I can find no way to use this or call it up for my users. I do not even see any submit buttons in the samples. Where do the resluts get posted? How do the members call up the editor? Where is the editor? I do not see any support here rither concerning any of this. What gives? A lot of js files and no way to call it.

Last edited by Mayor (2006-03-14 07:45:07)
You are not logged in. Please login or register.