brushed
added a comment - 02/Mar/14 19:05 Fixed in the HADDOCK TEMPLATE v2.10.1.svn.10,
The he functionality, previously implemented by posteditor.js, is now covered as part of the redesigned plain editor javascript classes.
dirk

The posteditor.js is only compatible with safari and firefox. (probably also chrome) IE support was never intended by the author.

As soon as jspwiki graduation is completed, I plan to do a major update of the plain editor. Parts of it were already committed in v3.0.0. That update will remove the need of the posteditor.js. So, I suggest to leave this jira issue till then.

brushed
added a comment - 16/Jul/12 20:36 @Florian
The posteditor.js is only compatible with safari and firefox. (probably also chrome) IE support was never intended by the author.
As soon as jspwiki graduation is completed, I plan to do a major update of the plain editor. Parts of it were already committed in v3.0.0. That update will remove the need of the posteditor.js. So, I suggest to leave this jira issue till then.
dirk

Florian Holeczek
added a comment - 16/Jul/12 12:29 Dirk, what is your opinion on Juan Pablo's suggestion?
I don't completely understand what problems are remaining. Is anything not working with IE? If so, is the current trunk affected?
Maybe we can close this one and create a new issue with some details attached?
Regards
Florian

Juan Pablo Santos Rodríguez
added a comment - 02/May/12 11:35 The license issue has been fixed, however posteditor.js lacks of IE support so, may be we can keep this one open, but setting priority to "Minor" and Issue Type to either "Improvement" or "Wish"?
Also, I've removed the Fix Version/s field: 2.9 was tagged a few days ago and we're not working on 3.0 anymore.

Juan Pablo Santos Rodríguez
added a comment - 24/Jan/12 21:27 postEditor's site ( http://icebeat.bitacoras.com/mootools/posteditor ) now explicitly states that it's licensed under MIT license.
If needed, we can reach postEditor author in order to get the license into the .js file, but I think that it's enough as it is right now (we ship a minified version of the library)..

brushed
added a comment - 20/Feb/10 20:39
Thanks )
The need of posteditor.js was removed already several versions back.
But I wanted to keep this jira open till the new snipeditor was at the same functional level as the posteditor.
dirk

Andrew Jaquith
added a comment - 20/Feb/10 18:12 Removed in 3.0.0-svn-207. Dirk, if and when you want to re-add this feature, feel free after we get to an Alpha build. But in the meantime, I felt it was best to remove it so we can graduate.

Janne Jalkanen
added a comment - 29/Sep/08 19:35 In fact, since any replacement is likely to be a BIG chunk of untested code, I'd actually really prefer to keep posteditor.js for 2.8... Else the release will take a long, long time.

Hmm... On second thought, since 2.8 isn't going to be an official Apache release, ASF won't have to suffer from any license problems. So I guess we could keep posteditor.js for 2.8, and then get rid of it for 3.0.

Janne Jalkanen
added a comment - 29/Sep/08 19:34 Hmm... On second thought, since 2.8 isn't going to be an official Apache release, ASF won't have to suffer from any license problems. So I guess we could keep posteditor.js for 2.8, and then get rid of it for 3.0.
However, JSPWIKI-380 needs to be resolved. It's REALLY annoying me...

Janne Jalkanen
added a comment - 23/Sep/08 22:23 The problem is really with the license, not with the functionality (though it is quite a mess too; little comments and non-obvious variable names).
What exactly is needed for the toolbar functionality? I tried disabling posteditor.js completely, and couldn't find anything that didn't work (aside from tab-completion and smart brackets).

This is not an obvious one, as most toolbar functionality relies on the posteditor functionality.
For the rest we could drop is, as it mainly provide support for the tab-completion and automatic bracks, which are not core to jspwiki.

brushed
added a comment - 23/Sep/08 21:45
This is not an obvious one, as most toolbar functionality relies on the posteditor functionality.
For the rest we could drop is, as it mainly provide support for the tab-completion and automatic bracks, which are not core to jspwiki.
I'll need some time to rewrite the toolbar functionality.
dirk