MozillaZine

SiteMason Announces Support for Midas

Friday March 14th, 2003

Ryan Smith writes: "SiteMason has announced full support for Midas editing in their CMS system. There's a press release about it on their press page." SiteMason is a Web design and content management solution. Midas is Mozilla's new API for rich text editing in webpages. A demo of Midas is available.


#16 Re: What it means

by user4321

Sunday March 16th, 2003 11:43 PM

You are replying to this message

Humph. Not what I wanted to hear, but I guess I have to accept it. However, that won't stop me from commenting further while I've got somebody listening. ;)

"If IE's designMode is a special case of contentEditable (rather than the other way around), then doing them with the same backend is easy."

Well, obviously, if I knew enough to really comment intelligently on that I'd probably be able to pore throught Mozilla's source and figure out all these answers for myself. I'm no C++ guru though, so I'll note that IE's designMode came well before contentEditable. I know it's probably more than too much to hope for, but is there anybody on the Mozilla staff who is willing and able to spend some thought on how that played out (and how it might be able to be similarly accomplished in Moz)?

"It may well be true that IE's stuff is easier to use..."

It isn't so much a question of ease of use as it is a question of functionality. I'm basically trying to fake functionality that cE has in order to make the Midas implementation seem to work as well. I'm bending the DOM over backwards to make it happen, but that can only go so far.

"... I really don't care for either set of functionality, I'm just describing the Mozilla implementation, with no comments as to quality (again, because I do not care, hence have not used it). ;)"

Again, I'm not happy to hear it, but I can understand it. In this particular case, though, you (not you personally necessarily, but the Mozilla organization) are basically a tool maker (a position I am not unfamiliar with in the non-virtual world). At what point do the desires of the people using your tools override your unwillingness to provide the features they want? And more to the point, how do you expect to accomplish the stated goal of getting people to develop applications with your platform when you are unwilling to provide the features they tell you they need to do so?