To hstraf and Spocke, I couldn't agree more. A pagebreak function is cool, and in many cases a great function - if it works flawlessly. However as Spocke mentions, it isn't something I feel belongs in a WYSIWYG editor, since it needs to be treated serverside afterwards - which again makes it a CMS specific function. I remember I had a customer aswell who wanted this function, and referred to Mambo (note, i havnt checked mambo lately), and Mambo was superior for this functionality while my system (TinyMCE, FCKeditor, Xinha and htmlArea) was crappy since they lacked it. A fast test hower inserting the pagebreak within a table broke the design big time in Mambo, which in turn brings me to Spockes point that such a function needs some amazing logic which isn't buildt in a jiffy.
Sure, I would love such a functionality - but is it reasonable to expect it to appear in TinyMCE, or should we let the developers focus on the core itself. If we look at the typical user of a CMS (People like me who are looking for functions like pagebreak are, in my belief, all persons using the WYSIWYG in our CMS), so the typical user is a person who doesnt know alot about HTML, probably nothing (If he knew HTML, he would probably use raw HTML, BBcode or MarkDown for optimal control in theese XHTML days). So what does a typical webpage in a WYSIWYG rendered page look like? It could be one table surrounding the entire page which is, say 5 pages long, containing 4 pagebreaks.
This would mean that we would make the Moxiecode staff spend a heck of a lot of time for this "seemedly" easy plugin to accually rewrite the entire code of the page to work with the pagebreaks (Or this is probably where our own serverside system gets to work), we can't just do what Mambo did (again, maby they solved this lately, I havnt checked), assume that the person using the WYSIWYG is not using the plugin wrong - after all it's WYSIWYG so people tend to do alot of wrong things (Did I mention paste from word and other websites, even if told otherwise)...
Lately I have spent more and more time using TinyMCE, but I would like to share my 2 cents here to be sure that the development is going in the right direction, and not focusing on messy plugins which will hault the development unneccesary. After all the developers are doing a great job on this free tool, and it doesnt hurt if we support them once in a while instead of always demanding new functionality all the time. Finally, as hstraf mentioned, if you really like this plugin to surface the people at Moxiecode will more than happy (ugh... As George Carlin mentions this is a pretty meaningless condition, hehe) spend time developing it for you if you are willing to pay for it.
Looking forward for the next release of TinyMCE, I will need to upgrade alot of users again... Keep up the good work
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
www.steinhaug.no - www.easywebshop.no - www.easycms.no