20130914 (Saturday, 14 September 2013)

DavLink

Fixed several problems in DavLink:

• Added a davlink.jnlp file and a manifest.txt file as explained in the Deployment Trail.

• Added a file davlink_jnlp_test.html which is like davlink_test.html but using JNLP.

• To facilitate further experimenting, lino.extjs.ext_renderer can now generate either with or without JNLP depending on whether USE_DAVLINK_JNLP is True or False.

• AFAICS both methods work the same, so I prefer the simple applet method until proof of the opposite.

• It seems that the main problem was the fact that DavLink.init() tried to set the SecurityManager. It seems that this was some obsolete technique, that it is simply not allowed and not necessary to change the security manager.

• DavLink.open() did not write a traceback to the console when some Exception occured.

• DavLink.open() returns a string with the error message when it fails, but davlink_test.html did not report this error message:

  document.applets.DavLink.open(webdavURL);
  

  Replaced this by:

  var msg = document.applets.DavLink.open(webdavURL);
  if (msg) alert(msg);
  

• Could not find any reason for a NullPointerException on Windows7 reported by Gerd. Added a message “DavLink.generate_default_prefs() done” in order to continue testing on Monday.

• In davlink_test.html and davlink_jnlp_test.html added a JavaScript function and a link to invoke DavLink.generate_default_prefs() with one click instead of using the brute force method of deleting the prefs.xml file.

All the above has been tested only using IcedTea and OpenJDK.

Note: for efficient testing on a live webdav-enabled Lino Welfare database:

• go once to the detail of some Event/Note which is being printed as webdav (i.e. a CV)

• click the permalink button

• Copy the URL line of your browser and then launch it directly to this url from the command line:

  $ chromium-browser http://127.0.0.1:8000/api/notes/MyNotes/28?an=detail
  

test_sdist

I finally got fab test_sdist to run. And found the reason for the problem with the last release reported by Joe: The install_requires of Lino specified ‘north’ instead of ‘North’. Also ‘PyYAML’ was missing in install_requires.

Now there’s just one ImportError:

Could not import settings 'lino.projects.belref.settings' (Is it on sys.path?): No module named lino_welfare.modlib.statbel

(which is normal. TODO: move lino.projects.belref to lino_welfare) or statbel from lino_welfare to lino)