On Wed, 2 Mar 2005 01:49:53 +0000 (UTC), ug57dsm@cs.bham.ac.uk wrote:
>Hi,
>
>I have been working on a project to bring the poplog environment to a
>more modern development platform (jEdit) than it currently possesses
>(xved). The result is a jedit plugin that runs and manages the poplog
>incremental compiler (http://sourceforge.net/projects/jpop/).
>
>As far as I can see, there are just a few problems to be ironed out
>before this can reach a version 1.0 (at the moment I have it at a beta-2
>stage), and it would really help if people could have a look at it
>(especially people in Birmingham Uni, but everyone is welcome), and let
>me know of any improvements you would like to see. Extra developers are
>also welcome if anyone wants to have a go :)
I haven't had time to look at this yet, and I haven't tried jEdit
either, but I am interested in the general question of interfacing
poplog to other editors/IDEs.
How's it going? (The sourceforge site looks like you haven't had
time to do anything new since 8th March.)
Jonathan
--
I'm doing NaNoEdMo in March, so may vanish from rasfc.
(And *will* vanish if I have any sense.)
Mail to spam auto-deleted, use jlc1 instead.
>From jeffb@jtbest.demon.co.uk Mon Mar 21 19:47:44 2005
Path: news.demon.co.uk!mutlu.news.demon.net!peer-uk.news.demon.net!kibo.news.demon.net!demon!newsfeed.stueberl.de!ecngs!feeder.ecngs.de!195.40.0.165.MISMATCH!easynet-monga!easynet.net!feed4.jnfs.ja.net!feed2.jnfs.ja.net!jnfs.ja.net!warwick!news-out.ftel.co.uk!bhamcs!news
From: jeffb@jtbest.demon.co.uk
Newsgroups: comp.lang.pop
Subject: Re: Poplog plugin for jEdit
Date: Mon, 21 Mar 2005 19:47:44 +0000 (UTC)
Organization: cs.bham.ac.uk MAIL->NEWS gateway
Lines: 144
Message-ID: <d1n8d0$1d5a$1@soapbox.cs.bham.ac.uk>
X-Trace: soapbox.cs.bham.ac.uk 1111434464 46250 147.188.192.10 (21 Mar 2005 19:47:44 GMT)
X-Complaints-To: abuse@cs.bham.ac.uk
X-Relay-Info: Relayed through cs.bham.ac.uk MAIL->NEWS gateway
Originator: exim@emily
Xref: news.demon.co.uk comp.lang.pop:1456
David,
Thank you to Jonathan for reminding me about this.
In message <200503211305.j2LD5pdw045571@soapbox.cs.bham.ac.uk>, Jonathan
L Cunningham <spam@softluck.plus.com> writes
>On Wed, 2 Mar 2005 01:49:53 +0000 (UTC), ug57dsm@cs.bham.ac.uk wrote:
>
>>Hi,
>>
>>I have been working on a project to bring the poplog environment to a
>>more modern development platform (jEdit) than it currently possesses
>>(xved). The result is a jedit plugin that runs and manages the poplog
>>incremental compiler (http://sourceforge.net/projects/jpop/).
>>
>>As far as I can see, there are just a few problems to be ironed out
>>before this can reach a version 1.0 (at the moment I have it at a beta-2
>>stage), and it would really help if people could have a look at it
>>(especially people in Birmingham Uni, but everyone is welcome), and let
>>me know of any improvements you would like to see. Extra developers are
>>also welcome if anyone wants to have a go :)
>
>I haven't had time to look at this yet, and I haven't tried jEdit
>either, but I am interested in the general question of interfacing
>poplog to other editors/IDEs.
I had a quick look at this today. To ensure there were no adverse
reactions from other plug-ins, (a problem I have had with jEdit in the
past), I installed a fresh version of jEdit onto a Windows 2000
partition that had not previously had jEdit installed and fetched the
current JPop download from Sourceforge. There was no apparent
documentation included with the download, but I guessed from David's
description of the project as a jEdit Plug-in, that the file needed to
be placed in jEdit's "JARS" directory to be recognised by the plug-in
manager, and so copied it there.
Once the plug-in was visible to the Plug-in Manager, I told it to load
the plug-in and then loaded a Pop11 file into the editor. I also started
a WinPop11 session. From the Poplog plug-in menu, I selected "Spawn a
Process". In response, jEdit recaptioned its main window "jEdit -
stdout.p" and did not, apparently, responding to any form of user input,
including a request to close the window. All access to jEdit's own
menus, including the edit buffer menu was lost.
I next killed both the WinPop11 and the "javaw.exe" processes and
restarted jEdit. It remembered the file I had loaded and the Poplog menu
was still enabled. I tried the "Open Docs Browser" menu option. This
opened a new window with some controls, including a text box, OK button,
tree control and a status panel. I navigated, in the tree control, to
the REF section, whereupon jEdit's main window was relabelled "jEdit -
ERROR[]", (where the "[]" is my representation of a non-printing
character at the end of the caption string), and the window listed the
following content,
null
Cause: null
org.jpop.net.PoplogDocProtocol.println(Unknown Source)
org.jpop.net.PoplogDocProtocol.getList(Unknown Source)
org.jpop.net.PoplogDocProtocol.processRequest(Unknown Source)
org.jpop.net.PoplogDocServerThread.run(Unknown Source)
At this point, I failed to work out how to get back to the file I had
opened for editing, since "Close View" wasn't the way to dismiss the
ERROR[] window, but it did close jEdit. (I subsequently spotted the
"drop-down menu indicator below the tool-bar that indicated a buffer
menu).
Finally, after restarting jEdit, I tried selecting some text; in this
case, the "exload" keyword, and tried the Poplog menu entry "Find Poplog
Documentation for Selected Text". This made the main window become
"jEdit - ERROR", (with no non-printing character at the end), and it
displayed the following, while also popping up a "Poplog Docs" window,
similar to the earlier one, containing a root of "Poplog Help" in a tree
control and with "Status: NOOP HELLO" in the status panel.
org.jpop.net.ClientException: null
Cause: null
org.jpop.net.PoplogDocProtocol.println(Unknown Source)
org.jpop.net.PoplogDocProtocol.getList(Unknown Source)
org.jpop.net.PoplogDocProtocol.processRequest(Unknown Source)
org.jpop.net.PoplogDocServerThread.run(Unknown Source)
[null:-1] in class:org.jpop.net.PoplogDocClient$2(method:
errorReceived)
[null:-1] in class:org.jpop.net.PoplogDocClient(method: run)
[null:-1] in class:java.lang.Thread(method: run)
org.jpop.net.ClientException:
[null:-1] in class:org.jpop.net.PoplogDocClient$2(method:
errorReceived)
[null:-1] in class:org.jpop.net.PoplogDocClient(method: run)
[null:-1] in class:java.lang.Thread(method: run)
org.jpop.net.ClientException: Cannot get a listing for HELP
[null:-1] in class:org.jpop.net.PoplogDocClient(method:
resolveDocName)
[null:-1] in class:org.jpop.net.PoplogCachedClient(method:
getDoc)
[null:-1] in class:org.jpop.net.PoplogDocClient(method: parse)
[null:-1] in class:org.jpop.net.PoplogDocClient(method: parse)
[null:-1] in class:org.jpop.gui.PoplogDocBrowser$3(method: run)
Assuming that there must be some instructions not included with the
download, I took a look at the jpop/sourceforge.net web page and there
were a number of instructions. It wasn't clear which were the minimum
necessary and sufficient instructions for use of the JPop plug-in. For
example, do I need to explicitly run the Documentation Server, Client,
Browser, etc. processes to support the plug-in?
I followed the plug-in installation instructions to dock the "Poplog
Docs" and "Poplog" plug-in elements in the suggested locations. Together
with my discovery of the edit buffer menu, this made navigating around
jEdit a little better, although the "javaw.exe" process still tended to
consume more system resources than anything else. In particular, I
retried the selection of the "exload" keyword, followed by choosing the
Poplog menu entry "Find Poplog Documentation for Selected Text". This
now produced two new buffers, one containing instructions regarding the
HELP function and the other with similar errors to before. Having
navigated to the HELP buffer, I typed "version" into the "Poplog Docs"
text box and clicked on OK. As I write, the javaw.exe process is still
consuming over 90% of my CPU, is refusing to update the screen and seems
to have failed to supply any information in response to the entered
command. For some reason, the process has produced over five and a half
million page faults and over eleven and a half million "Other" I/O
operations.
At this stage, I decided that either the software itself, or its
configuration, due to the way I installed it, was not at a suitable
level for testing and aborted my investigation.
I will try to find the time to have another look at it when you get back
to me. If the software is still in a very early stage, with little more
than skeletal functionality, then it may be the case that you should
consider it pre-Alpha software, and hold on to it for more work before
releasing it for test feedback. If you are trying to produce something
with rapidly-prototyped functionality, built in to a largely incomplete
skeleton, then it would be helpful to have some indication of the
functionality that you think is ready for testing.
Regards,
--
Jeff
|