To quckly review, yes, if one places the applet code in an externally accesible locatio then it is easy enough to reference the codebase, as in the case of the java sketchpad jsp directory getting installed at fqdn/jsp. Others have noted that one an use relative paths, but that is going to be very problematic fro someone who is not the actual administrator.... The obvious answer is to be able to place the applet files in a directory created by Moodle and use the Moodle reference to access it in the html, which makes the files easily accessible to the teacher with a minimum of confusion as well as unavailable to everyone else on earth (see my prior note on the use of the /jsp install of the sketchpad files.)
I have now tried a variety of things to accomplish this. By way of example, the java sketchpad files are installed here: http://fqdn/files/index.php?id=12&wdir=//jsp
If you go to here:
jsp is the first directory listed, and is listed as above
And use slash args is tagged.
While moodle will let me reference a file using file.php, as in:
<applet width="706" height="437" align="middle" code="GSP.class" archive="jsp4.jar" codebase="/jsp"> <param name="etc=1" /> </applet>It will seem to throw an error when one references a codebase that is a directory as is the case with the java sketchpad....
and as yet I have not been able to test just using the the above as the codebase reference as now the html source editor no longer responds ;=}
So, is anyone using php to identify the codebase, and if so, how have you done this. If no one has been able to make this work, why, and is this something that needs to be brought to developers attention prior to Moodle 2. Lastly, if there is a simple work around (i.e. a way to proviee a simple installation location that will limit access to the users of that moodle trhough a simple URL, does some have something that can serve as a kernel for a HOW To so that this issue can be viewed as done and done?