Talk:Scripting

Proofreading

Hello, Volker -

I've begun proofreading the Scripting section here, as promised. Since I'm just getting started with scripting for Freeplane, would you please double-check my edits to ensure that I've understood the content?

As a novice I'll also have some questions as I follow the steps under Getting started. It seems cleanest to ask those questions here on this Talk page (below), rather than muddying up the text on the Scripting page itself.

--Jayseye 09:49, 8 March 2010 (UTC)

Content Questions

Create a script...

If the user requires a text editor to create the script, then it would be good to say that explicitly. When I read "You can start with scripting without any prior download of additional software," I assumed that referred to Freeplane's built-in Script Editor. That seems to be the wrong tool to use here.

Also I wonder if steps 1 and 2 should be swapped, to create the scripts directory first, before creating the test script.

Warning for unsigned scripts

When running the script for the first time, the user gets a dialog with a rather severe warning that an unsigned script could damage their computer. So it would be a good idea to prepare the reader for this in advance.

--Jayseye 09:49, 8 March 2010 (UTC)

Log file

Watching the log file as suggested, I see a lot of "Result:null" entries before and / or after the expected output. Here's an example:

STDOUT: Result:null

STDOUT:[org.freeplane.plugin.script.proxy.NodeProxy@1c78794a]

STDOUT: Result:null

Any idea what might be causing these?

Thanks!

--Jayseye 10:16, 8 March 2010 (UTC)