I've been wondering for some time if JSPWiki hasn't become somewhat too dependent on esoteric Javascript code for its core functionality. Dirk has done a wonderful job - of that, there's absolutely no doubt. When the template logic works (as it normally does quite well), it's a marvel to behold.
But when it doesn't, it's sometimes a nightmare to figure out. I'm OK figuring out Java, servlets, HTML and the like - even with its poor documentation, I can eventually figure out the innards of JSPWiki code. But the increasingly complex Javascript will often does me in. On Tue, 2008-08-19 at 21:51 +0200, Dirk Frederickx wrote: > Janne, > > The 2nd textarea is inserted to allow section-editing. > Just 'kill' jspwiki-eidt.js to get rid of it. (eg. commenting the > last line of jspwiki-edit.js will do the trick -- remove > window.addEvent ....) > > > dirk > > On Tue, Aug 19, 2008 at 9:43 PM, Janne Jalkanen > <[EMAIL PROTECTED]> wrote: > > > > On 19 Aug 2008, at 22:35, Janne Jalkanen wrote: > > > >>> > >>> Not because of ACLs, but because request.getParameter() is returning the > >>> *page content without edits*. This should NOT be happening. > >> > >> Looks like our Javascript is inserting an extraneous <textarea> without an > >> id, and putting the edit content in it. Ugh. Hard to debug. > > > > I would really like to understand what is going on with the editor. Why are > > there two textareas created programmatically? > > > > /Janne > >
