create new tag
, view all tags

PowerEditPluginDev Discussion: Page for developer collaboration, enhancement requests, patches and improved versions on PowerEditPlugin contributed by the TWikiCommunity.
• Please let us know what you think of this extension.
• For support, check the existing questions, or ask a new support question in the Support web!
• Please report bugs below

Feedback on PowerEditPlugin

Discussions on the Plugin formerly known as PowerEditAddon. For older stuff, see PowerEditAddonDev

Recoded all the Perl so it now works as a plugin. This allowed me to eliminate the server script and reduce the size of the java by 100K. Now uses the beforeEditHandler introduced for plugins version 1.010, so won't work on older versions - hence only tested on the Feb 2003 release.

-- CrawfordCurrie - 15 Mar 2003

Initial feedback:

  • Looks good, this is better served as a Plugin!
  • I made some formatting changes to the PowerEditPlugin topic (added short description setting (debug supported? additional vars?); made links point to TWiki.org's Plugin web also when Plugin is installed elsewhere; removed links to itself; etc). Could be taken back into the zip.
  • Any reason for attaching the Plugin here on the Dev topic? Should I move the attachment to the Plugin topic?

-- PeterThoeny - 15 Mar 2003

Hello Crawford, excellent work, looks great.

Unfortunately I found an inconvenience or maybe BUG?

I started to klick on the questionmark on one of the nin-existant topics in the Sandbox.

  • Then I edited the topic with the usual Edit link and did save using the savemulti script.
    • Topic has beed created with the initial content I have entered. Everything is OK !
  • Then I tried your new PowerEdit and it did the editing work fine. I added content to result in the updated content .
    • Then I did a preview and a save. Everything is OK !
  • Then I tried again your new PowerEdit and it came up with the initial content instead of the updated content . I clicked on Cancel .
  • Then I edited the topic with the usual edit link. It contained the updated content . Everything is OK !

So what did I do wrong or is this a bug?

-- MartinRaabe - 16 Mar 2003

Peter: I'm not QUITE ready to release yet (I need confidence that it works with Plugin-enabled browsers; I've seen problems with IE). BTW, not having modify access to the meta-data during the beforeEditPlugin is a major pain in the nether regions.

Martin: I know; it's because the applet is cached locally. I'm working on it. In the meantime, just refresh the page with the applet on it.

-- CrawfordCurrie - 17 Mar 2003

Is there a demo around anywhere? Thanks.

-- MartinCleaver - 29 Mar 2003

I encountered the following problems:

  • caching problem as described above
  • loaded text is html encoded: means that symbols like > are replaced by
    & gt;
    (i am working with mozill java 1.3 and apache)
-- WenzelKalus-- 04 April 2003

Thanks Wenzel, I know about the HTML encoding, and I've fixed it. No solution for the cacheing yet, though Javascript has some potential.

BTW, one of my colleagues has come up with a really cool "TWiki Assistant" that lets you semi-automatically move text into your favourite editor. It doesn't even require any server-side components. I've asked him to consider releasing it to the community.

-- CrawfordCurrie - 04 Apr 2003

i just solved caching problem: change view template to:

 %TMPL:P{"sep"}%<a href="%SCRIPTURLPATH%/edit%SCRIPTSUFFIX%/%WEB%/%TOPIC%?skin=power&time=%GMTIME{"$hours$minutes$seconds"}%">PowerEdit</a>

(applet receives always different text (cause of time))

Crawford: would be great, if you provided latest version of applet (...tags!!)

-- WenzelKalus

This looks like a very useful plugin - screenshots or a demo link would be useful.

Wenzel's fix is basically a re-invention of RefreshEditPage - the fix for applet caching is to use a different URL for the first and second Edit of a given page - it would be best to just implement the recommended URL there, which is shorter and uses code already in TWiki. See the part that talks about skins - this applies to any applet or skin that includes an Edit feature/link.

-- RichardDonkin - 16 Apr 2003

Why is the downloadable zip in this topic rather than PowerEditPlugin?

-- JohnTalintyre - 16 Apr 2003

Wenzel, Richard, thanks; I'll look into this ASAP.

John, it's here because I haven't released it yet; I wanted a fix to the refresh problem first, and I haven't had time to research it myself.

-- CrawfordCurrie - 17 Apr 2003

I cannot get this to work. I unpacked the zip as described, added a line to templates/view.tmpl as suggested and have the PowerEdit link at the bottom of the pages. When I click on it I get an edit page with the raw page text displayed on it and no editing. I know applets work in my browser(s) as I use the Draw plugin from time to time. The Browser's I have tried are Konqueror, Galeon(1.2.5) and Netscape(7.01).

What have I missed?

-- BrianWallis - 28 Apr 2003

Netscape should be OK. Do you have the permissions to access all the files? Remember it's the apache user who has to read them, not you. Also try opening the Java console, seeing if there are any messages, and maybe even the javascript console (type javascript: into the URL bar).

-- CrawfordCurrie - 28 Apr 2003

Ahha! Javascript console shows

Error: document.main.text has no properties
In http://localhost/twiki/bin/edit/Personal/WebHome?skin=power, Line 11, 
in both Netscape 7 and Galeon. Not sure what this means though.

I commented out line 11 document.main.text.focus(); in edit.power.tmpl and the error goes away but the edit page displays the same. I also tried with IE 5.5 (under Codeweavers Wine on Linux) and get the same page displayed.

-- BrianWallis - 29 Apr 2003

Brian, check TWiki.TWikiPreferences to see if the plugin is really active because if not, you'll get the wrong HTML and there will be no applet code in there. If plugin is not active, try apachectl graceful. Worked for me. But for using it I've tried NS4.78/Solaris, NS7/Solaris, Mozilla 1.4a/OS X, NS4.x/MacOS 9, IE 5.2/OS X. Only NS4.78/Solaris worked. The others load the applet and then say something like "applet not inited". Error from Java log looks like this:

Duplicate key in parameter table: archive using the htmlAttribute.
    first: /twiki/pub/TWiki/PowerEditPlugin/poweredit.jar
   second: /twiki/pub/TWiki/PowerEditPlugin/poweredit.jar
Duplicate key in parameter table: mayscript using the htmlAttribute.
    first: true
   second: true
Duplicate key in parameter table: width using the htmlAttribute.
    first: 984
   second: 100%
Duplicate key in parameter table: scriptable using the htmlAttribute.
    first: true
   second: true
Duplicate key in parameter table: name using the htmlAttribute.
    first: TWikiEdit
   second: TWikiEdit
   at netscape.javascript.JSObject.getWindow(JSObject.java:141)
   at com.ccsoft.edit.TWikiEdit.init(TWikiEdit.java:94)
   at sun.applet.AppletPanel.run(AppletPanel.java:339)
   at java.lang.Thread.run(Thread.java:491)
Oh yes, and I still get the "line 11" error that was reported by others.

-- StefanLindmark - 05 May 2003

Seems like this is not a unique problem. See this page (search for jsobject) for descriptions of similar problems. Could perhaps be used by somebody more skilled in Java to figure out a fix/workaround.

-- StefanLindmark - 06 May 2003

Tried Safari/OS X (build 73) with Java 1.4.1_01 and got this:

   at netscape.javascript.JSObject.getWindow(JSObject.java:144)
   at com.ccsoft.edit.TWikiEdit.init(TWikiEdit.java:94)

   at sun.applet.AppletPanel.run(AppletPanel.java:347)
   at java.lang.Thread.run(Thread.java:554)

-- StefanLindmark - 06 May 2003


  1. The focus problem I found and fixed some ago. The source in the CVS repository should be OK.
  2. I tried to support tags for different browsers/plugins by generating the applet tag on the fly. In the applet (and I think embed) tags, params are fed in by adding them as attributes to the tag. For object (and maybe embed) tags they are provided in external "param" tags in the block. All three tag types are given a full set of param tags, because it didn't seem to break anything. I guess it does, and I need to remove the param defs when they are not used.
  3. A JSException in getWindow could be almost anything.
  4. I checked in the latest code to CVS on Sunday. I'm just finishing up the latest version of the ActionTrackerPlugin, so I should get some time to look at PowerEditPlugin soon.

In general I have found that most of the problems with different browsers are resolved by massaging the javascript; I don't think I've had to recompile the java to fix a problem yet (the java is in general very simple). So some gentle tweaking of the javascript may help you resolve, or at least investigate, some of these issues.

-- CrawfordCurrie - 07 May 2003

Well, it seems that the JVMs in many browsers are just incredibly buggy. I get a lock-up occasionally with NS 4.75, but I can't reproduce it reliably. My IE5 at work doesn't work with the 1.4 plugin and the OBJECT tag, but if I revert to APPLET the browser refuses to recognise the APPLET tag unless I switch off the 1.4 plugin in the options.

The attached updated version is the latest code in CVS, but the only change is a minor tidy-up of the sub-template. Perhaps someone more au fait with Javascript and browser problems can have a look at it and see if there's anything obvious. Question: should I release this? Is it worth it?

-- CrawfordCurrie - 11 May 2003

Well, I got it working here OK now. I missed the bit at the top of this page about not working with TWiki releases prior to the Feb 2003 release which I have now installed. I have tried it with:

  • Galeon 1.2.5 (Mandrake Linux 9.1) which it doesn't work with
  • Mozilla 1.3/Netscape 7.0{1,2} (Mandrake Linux 9.1) with which it does work
  • Konqueror 3.1.0 (Mandrake Linux 9.1) which segfaults (Damn!)
  • IE 5.5 on NT4SP6a where it does work
Is it worth releasing? I think the testing with various browsers and any issues with them needs to be worked out before release. Functionality? I need to play with it some more before I decide about that.

I think it is worth persevering with, but to have an applet editor that is more WYSIWYG would be more to my liking. I'm actually quite happy with a textarea for edit as long as it has undo (which Galeon doesn't!). If I move to an applet, then I expect to get some extra features like WYSIWYG, lists, bold, tables, etc.

-- BrianWallis - 23 May 2003

Brian, I'd like to know what you had to do to get it working on all these platforms. Did you have to modify anything?

Here are some thoughts on WYSIWYG:

  1. Most browsers only support JDK1.1, so implement an applet in JDK1.1. This means missing out on all the juicy stuff in 1.2 onwards and trying to do it all in 1.1. Aside from the obvious replication of what's already been done by Sun in 1.2 on, this implies a HUGE applet, with resultant slow download/startup. This is a major project.
  2. Alternatively, implement an applet in JDK1.4. Most of what you need to create an editor applet already exists in JDK1.4, in the HTMLEditorKit. However, you are requiring users to install a mighty plugin (which may knacker existing applets - see above). You also have the problem of supporting twikiML (twiki markup language). This is a major project.
  3. Re-use an existing editor applet such as EKit Still have the problem of supporting twikiML.
  4. Use JavaScript. Again, this has been explored elsewhere. There's an excellent JavaScript editor called htmlarea that could be extended to use twikiML and is GPL. Unfortunately, it only works with IE. To build a really good JavaScript/IE editor is a medium scale project.
  5. A good approach is that described in DownUploadForEditing. This is a little daemon that takes an 'edit' URL, downloads it, filters out the textarea, and dumps it into your editor of choice. After editing it will feed the results back to the TWiki 'save' script.
  6. Any of the above would become easier if there existed a TWiki ML filter that could convert a page in twiki ML to pure HTML, and HTML back to TWiki ML. Obviously it would only process that subset of TWiki ML that relates to formatting i.e. the strict subset defined in TextFormattingRules. TWiki ML to HTML is fairly straightforward, but the reverse transformation requires a lot of care. Also, start thinking about what plugins might do to page formatting and you enter a world of pain.

I really don't know what the best approach is. Probably:

  1. IE users - JavaScript, though it needs the htmlarea
  2. Users still in the editing dark ages (a.k.a 'emacs-ites') - daemon
  3. Newbies - EKit + twikiML filter

See also: WikiEditor for other editor related pages. I've downloaded EKit and I'm going to explore this last option.

-- CrawfordCurrie - 26 May 2003

I ran the idea of using Wiki for our product in the department, from inital reponses it looks like;

  1. Acceptance will be easier if Twiki has a WYSIWYG type editor. Like editor of EditMe
  2. Using EKit seems to be pretty good idea. But their demo is somehow very very slow. It seems to me their server is a slow one, or have a slow connection. And when I tried to use it at home with IE 5.5 demo didn't start (could be my home PC setup issue as well, and I emailed Ekit folks about very very slowness of their demo).
  3. I beleive CrawfordCurrie was ahed of me on this, I'm wondering what happened with his experiment?

-- IlkerKiris - 14 Jan 2004

I have almost finished extending the PowerEditPlugin to support an optional "Live Preview" pane. This displays the formatted page (TML and HTML) while you are editing. I'll post a demo here when I've finished testing against the XHTML1.0 spec. Features:

  • + XHTML1.0 conformant (well, some of XHTML1.0 anyway!)
  • + edit in TWikiMarkup, immediately see result on display
  • + Java 1.1, no need for Java2 browser plugin (unlike EKit)
  • + small (jar is currently slightly smaller than EKit)
  • + can be used with raw HTML, or used to generate HTML from TML
  • + handles everything handled by TWiki.pm getRenderedVersion(). Uses unedited regexes from TWiki.pm to process TML, so should be
  • + local page rendering, so pretty good cycle time for edit->display
  • + stand-alone or applet versions
  • - (there had to be some) doesn't handle variables (e.g. %YELLOW%, %WIKINAME%)
  • - doesn't handle images (or anything else requiring data from the server)
  • - knows nothing about plugins

-- CrawfordCurrie - 18 Jan 2004

OK, there it is. I haven't created an applet demo, as netscape has it's usual security exception problems that I haven't diagnosed yet. The attached zip (xhtmleditor.zip) contains the jar file suitable for running stand-alone - instructions are in the README. You will need a java JRE installation to run it. I have included an example TML file "combo.txt". Please let me have feedback!

-- CrawfordCurrie - 20 Jan 2004

And here's the applet... mostly works in IE6, haven't tested anything else.

I moved to applet to the end so it's easy to find

-- CrawfordCurrie - 03 Feb 2004

Looks nice, and works fine in Konqueror 3.1.4, Linux. Suffers from the obvious problem for TWiki which is perhaps best shown thus:

  • Type a word - eg flibble
  • Select it
  • Hit Bold - you get *flibble*, rendered as flibble
  • Select the whole thing again (ie *flibble* )
  • Hit Italic - you get _*flibble*_ rendered as *flibble*
  • Type a word - eg flibble
  • Select it
  • Hit Italic - you get _flibble_ rendered as flibble
  • Select the whole thing again (ie _flibble_ )
  • Hit Bold - you get *_flibble_*, rendered as _flibble_

Standard TWiki issue I know, but one users would hit and feel uncomfortable. (Rather than just cryptic, in their eyes it would be that the software "doesn't work". )

Zope has epoz via plone available which has an edit screen that looks like this . It doesn't work in Konqueror, but does work in Mozilla (to differing degrees depending on platform).

-- MS - 03 Feb 2004

very well done!


  • i did not get a scroll bar for the preview pane so I can't see the text on larger topics
  • need buttons for header1, 2, 3, 4...
  • I'd like to use the cursor in the preview pane (could do away with the twiki edit pane and have a wysiwyg editor then smile

-- SvenDowideit - 04 Feb 2004

Don't think about it as a full-featured HTML editor; it isn't. Think about it as a TWiki ML editor. What you see in the plain text pane is what you get in the preview pane (ish).

Enabling clicking directly in the preview pane opens a whole can of spaghetti. A cursor position in the TML does not necessarily have a corresponding position in the XHTML. Consider a heading; if the cursor is on the second of the -'s, where is it in the XHTML? And if you click at the start of the heading in the XHTML, where should the cursor position be in the TML? Also, supporting HTMl editing sets expectations on the part of users. Complexities such as table editing enter the frame, as do forms, frames and all the rest.

I looked at the problem of building a full HTML editor - this is basically what EKit is - but the resultant applet was extremely heavy - large, slow, and complex to use. I also looked at re-using the Zope editor - but rejected that route for the same reasons. By decoupling the edited text and it's rendering, the problem is significantly reduced, because the HTML is constrained to what can be done in TML. And the basic source of the topic remains as TML; the applet does not encourage embedded HTML. However, there are prices to be paid due to the limitations of TML, as you have noted.

One way to think about it is as a teaching tool. A newbie can use the applet to edit, and they will learn TML by osmosis. After a while they'll be able to abandon the applet and use the textarea, like the rest of us.

See WikiCanonicalForm for more on the problems of twiki ML and other ML representations.

Sven, you can add (or remove) whatever buttons you want programatically; see the PowerEditPlugin topic as an example. I don't know what happened to your scroll bar - what browser are you using?

-- CrawfordCurrie - 04 Feb 2004



I just want to report what happened for me (twice) while trying to edit using the test applet on this page.

Background: konqueror 3.1.1 on Knoppix 3.2 (Debian) (installed on hard drive), I keep multiple instances of konqueror open with multiple tabs on each.

Occurrence: After playing with the applet (and specifically, clicking on the icon that calls up the search and replace and then clicking on the x to close it without doing a search and replace), I went to a different tab to edit a different twiki.org (TWiki) page. When I attempted to edit, the edit window opened, I could select text in the edit window (with the mouse) but the insertion point did not appear, I could not make it appear, and the keyboard was not "active" (hitting keys would not enter text in the edit window).

After closing the window on this page, and (iirc) attempting a new edit on that page, things worked fine. (Then I reopened this page and tried editing another page to attempt to recreate the problem. I could edit the page until I called up and then cancelled the search and replace dialog (on this page / applet).)

I don't know if it's a problem with your applet, something in konqueror, some "normal behavior" of HTML, or what, and it doesn't seem serious to me at the moment, but I thought I'd mention it.

-- RandyKramer - 04 Feb 2004

Randy, absolutely no idea! I generally test against Netscape 4.75 and IE6. But what you describe sounds like nothing to do with the applet. As you are probably aware, an applet operates in a sandbox where it can't affect anything outside it's own window, unless you have added that capability (and I doubt it), so it's got to be a browser problem; probably something to do with the focus.

-- CrawfordCurrie - 05 Feb 2004


Thanks for the response! I tried it today on IE 6.0.28 and did not see a problem. I've assumed that it's repeatable on konqueror (because I did get it to repeat once), I may try it again, and if I come up with any more clues or hints I'll add them here.

-- RandyKramer - 05 Feb 2004

I've tested it on Mozilla 1.6 for Win and it works perfectly. Haven't tried it on Firebird .7 but will.

-- SteveRJones - 06 Feb 2004

Very nice! I agree about the need for heading buttons, and the URL button prefixes a / rather than an [

-- MartinCleaver - 06 Feb 2004

I repeat; you can add or remove buttons as you want to. The reason I took the heading buttons off the demo is because it uses and applet tag, which uses <param type parameters, which are truncated in Netscape older versions, and I wanted it to be visible to as many folks as possible.

You can configure it to download the controls from a URL. This also allows you to define your own button images etc for the controls as well. I'll update the applet to demonstrate this.

-- CrawfordCurrie - 07 Feb 2004

Here is what I have found:

  • Running Firebird 0.7 and JRE 1.4.2_03-b02 under WindozeXP. Initial load of the PowerEditPluginDev page results in displaying the PowerEdit window. Performing a refresh results in a blank, grey box yet Firebird status line indicates that the applet is running. The Java console does not indicate any errors.

FIX INDICATOR: In the Jave Console window, choosing option X - Clear Classloader Cache results in the proper re-fresh of the PowerEdit window.

  • Running IE6 and JRE 1.4.2_03-b02 on the same box. Initial load of the PowerEditPluginDev page results in displaying the PowerEdit window. Performing a refresh results in the proper display of the PowerEdit window.

-- SteveRJones - 09 Feb 2004

I've updated the demo to load the controls from a URL, so you should be able to other controls now. BTW if you want to play with the applet locally, download poweredit.jar and PowerEditControls.txt and then java -cp poweredit.jar com.ccsoft.edit.StandAlone -c PowerEditControls.txt file to edit.

-- CrawfordCurrie - 09 Feb 2004

I downloaded stuff and followed instructions. Also copied the stuff at the bottom of this page into a blank/empty twiki page in hopes that editor would work on my site. This as the command .../edit/web/topic?skin=power didn't render a text area for input.

I'm having difficulty getting this plugin to work. So, I ran
ant -f PowerEditPlugin.xml test
from the command line and got error indicating it couldn't find the java.lang package, so searched my box for the rt.jar file and put it into the classpath references in the PowerEditPlugin.xml file and ran the test again: This time I got following errors:

(fch1dev)on fchdev /opt/famhistdev/fhdev3/mtwiki:>ant -f PowerEditPlugin.xml test
Buildfile: PowerEditPlugin.xml


    [javac] Compiling 13 source files to /opt/famhistdev/fhdev3/mtwiki/lib/TWiki/Plugins/PowerEditPlugin/applet.classes
    [javac] /opt/famhistdev/fhdev3/mtwiki/lib/TWiki/Plugins/PowerEditPlugin/src/com/ccsoft/edit/TWikiEdit.java:15: package netscape.javascript does not exist
    [javac] import netscape.javascript.JSException;
    [javac]                            ^
    [javac] /opt/famhistdev/fhdev3/mtwiki/lib/TWiki/Plugins/PowerEditPlugin/src/com/ccsoft/edit/TWikiEdit.java:16: package netscape.javascript does not exist
    [javac] import netscape.javascript.JSObject;
    [javac]                            ^
    [javac] /opt/famhistdev/fhdev3/mtwiki/lib/TWiki/Plugins/PowerEditPlugin/src/com/ccsoft/edit/TWikiEdit.java:61: cannot resolve symbol
    [javac] symbol  : class JSObject
    [javac] location: class com.ccsoft.edit.TWikiEdit
    [javac]     JSObject form;
    [javac]     ^
    [javac] /opt/famhistdev/fhdev3/mtwiki/lib/TWiki/Plugins/PowerEditPlugin/src/com/ccsoft/edit/TWikiEdit.java:73: cannot resolve symbol
    [javac] symbol  : class JSObject
    [javac] location: class com.ccsoft.edit.TWikiEdit
    [javac]     JSObject member = (JSObject)form.getMember(field);
    [javac]         ^
    [javac] /opt/famhistdev/fhdev3/mtwiki/lib/TWiki/Plugins/PowerEditPlugin/src/com/ccsoft/edit/TWikiEdit.java:73: cannot resolve symbol
    [javac] symbol  : class JSObject
    [javac] location: class com.ccsoft.edit.TWikiEdit
    [javac]     JSObject member = (JSObject)form.getMember(field);
    [javac]                            ^
    [javac] /opt/famhistdev/fhdev3/mtwiki/lib/TWiki/Plugins/PowerEditPlugin/src/com/ccsoft/edit/TWikiEdit.java:88: cannot resolve symbol
    [javac] symbol  : class JSObject
    [javac] location: class com.ccsoft.edit.TWikiEdit
    [javac]     JSObject member = (JSObject)form.getMember(field);
    [javac]         ^
    [javac] /opt/famhistdev/fhdev3/mtwiki/lib/TWiki/Plugins/PowerEditPlugin/src/com/ccsoft/edit/TWikiEdit.java:88: cannot resolve symbol
    [javac] symbol  : class JSObject
    [javac] location: class com.ccsoft.edit.TWikiEdit
    [javac]     JSObject member = (JSObject)form.getMember(field);
    [javac]                            ^
    [javac] /opt/famhistdev/fhdev3/mtwiki/lib/TWiki/Plugins/PowerEditPlugin/src/com/ccsoft/edit/TWikiEdit.java:94: cannot resolve symbol
    [javac] symbol  : class JSObject
    [javac] location: class com.ccsoft.edit.TWikiEdit
    [javac]     JSObject jsWin = JSObject.getWindow(this);
    [javac]         ^
    [javac] /opt/famhistdev/fhdev3/mtwiki/lib/TWiki/Plugins/PowerEditPlugin/src/com/ccsoft/edit/TWikiEdit.java:94: cannot resolve symbol
    [javac] symbol  : variable JSObject
    [javac] location: class com.ccsoft.edit.TWikiEdit
    [javac]     JSObject jsWin = JSObject.getWindow(this);
    [javac]                          ^
    [javac] /opt/famhistdev/fhdev3/mtwiki/lib/TWiki/Plugins/PowerEditPlugin/src/com/ccsoft/edit/TWikiEdit.java:95: cannot resolve symbol
    [javac] symbol  : class JSObject
    [javac] location: class com.ccsoft.edit.TWikiEdit
    [javac]     JSObject doc = (JSObject)jsWin.getMember("document");
    [javac]         ^
    [javac] /opt/famhistdev/fhdev3/mtwiki/lib/TWiki/Plugins/PowerEditPlugin/src/com/ccsoft/edit/TWikiEdit.java:95: cannot resolve symbol
    [javac] symbol  : class JSObject
    [javac] location: class com.ccsoft.edit.TWikiEdit
    [javac]     JSObject doc = (JSObject)jsWin.getMember("document");
    [javac]                         ^
    [javac] /opt/famhistdev/fhdev3/mtwiki/lib/TWiki/Plugins/PowerEditPlugin/src/com/ccsoft/edit/TWikiEdit.java:96: cannot resolve symbol
    [javac] symbol  : class JSObject
    [javac] location: class com.ccsoft.edit.TWikiEdit
    [javac]     form = (JSObject)doc.getMember("main");
    [javac]                 ^
    [javac] 12 errors

file:/opt/famhistdev/fhdev3/mtwiki/PowerEditPlugin.xml:95: Compile failed; see the compiler error output for details.

Total time: 2 seconds

I'm running ie 6 on IBM box under Red Hat 8.

Help please wink

-- CharlieSmith - 21 May 2004

You need the netscape javascript classes: http://wp.netscape.com/eng/mozilla/3.0/handbook/plugins/doc/packages.html

You should be able to get them from netscape.com, but remeber your are compiling to target a Java 1.1 environment.

I'm not sure how recent that code you are compiling is; if you are trying to reproduce the applet below, then you will have to use the code I just checked in to CVS. I don't think I ever packaged it for release, as nobody seemed interested. I can't even compile any more (I no longer have a JDK1.1.8, and I don;t have time to instal one) so I'm afraid you are on your own w.r.t the compile environment. Your best source of support would be to catch me on TWikiIRC when I'm there.

-- CrawfordCurrie - 22 May 2004

The installation instructions for the GnuSkin are slightly different. I put

   %TMPL:P{"sep"}% <a href="%SCRIPTURLPATH%/edit%SCRIPTSUFFIX%/%WEB%/%TOPIC%?skin=power">PowerEdit</a>

one line below


in twiki.gnu.tmpl

-- WayneDahl - 07 Jun 2004

Wayne, I tried this, but got better results with

-->add this
  <a href="%SCRIPTURLPATH%/edit%SCRIPTSUFFIX%/%WEB%/%TOPIC%?skin=power" title="Edit this topic"><img src="%PUBURLPATH%/%TWIKIWEB%/GnuSkin/edit.png" align=middle border=0 width=16 height=16 alt="#">&nbsp;PowerEdit</a>
-->end add
  <a href="%SCRIPTURLPATH%/edit%SCRIPTSUFFIX%/%WEB%/%TOPIC%?time=%GMTIME{"$mo$day$hours$minutes$seconds"}%" title="Edit this topic"><img src="%PUBURLPATH%/%TWIKIWEB%/GnuSkin/edit.png" align=middle border=0 width=16 height=16 alt="#">&nbsp;Edit</a>

...in twiki.gnu.tmpl

-- JasonPiterak - 15 Jul 2004

Little bug with renamed TWikiWeb

Hi. I just figured out, why the PlugIn was not running on my TWiki. I couldn't find it (on the first look) above so here a my little hint:

When you change the name of your TWikiWeb to something else the PlugInn won't work!

applet.power.tmpl, line 26:
- TWiki

Perhaps this should be corrected in the next release.

-- KaiRedemann - 09 Dec 2004

Is this Plugin now an obsolete package since the WysiwygPlugin release?

-- PeterThoeny - 14 Mar 2006

Topic attachments
I Attachment History Action Size Date Who Comment
Texttxt PowerEditControls.txt r1 manage 2.0 K 2004-02-09 - 10:49 CrawfordCurrie Controls description for demo applet
Unknown file formatjar poweredit.jar r2 r1 manage 149.0 K 2004-02-09 - 16:35 CrawfordCurrie Jar for demo applet
Compressed Zip archivezip xhtmleditor.zip r1 manage 130.5 K 2004-01-20 - 10:22 CrawfordCurrie Demo of TWiki markup editor
Edit | Attach | Watch | Print version | History: r50 < r49 < r48 < r47 < r46 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r50 - 2006-03-14 - PeterThoeny
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by Perl Hosted by OICcam.com Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.
Copyright © 1999-2018 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.