Revisiting ECMA. Seriously, folks. :)
By the way, I am finally starting again to work on the ECMAScript/SVG binding (not Inkscape scripting). I checked in a cleaned-up directory of Mozilla's Javascript C engine. It is in /src/extension/script/js so that it can be convenient to both the SVG binding and IS scripting guys. I also started checking in a few files in /src/ecma for testing. Hopefully in a few days we can start seeing some progress. Bryce shamed me out of my lethargy with his article. ;-)
Off topic: You might be interested in this mail list thread from another OS project (probably -the- OS project), gcc:
http://gcc.gnu.org/ml/gcc/2004-06/msg00014.html
This shows the kind of interaction among the members of a very large project. Some of the threads in that list can be fascinating.
Bob
On Thu, Jun 03, 2004 at 02:06:57PM -0500, Bob Jamison wrote:
(not Inkscape scripting). I checked in a cleaned-up directory of Mozilla's Javascript C engine. It is in /src/extension/script/js so that it can be convenient to both the SVG binding and IS scripting guys. I also started
Is this available from mozilla as a devel library or anything instead of keep a "local" copy in the inkscape source tree? Or is that not feasible?
On Thu, 3 Jun 2004, Bob Jamison wrote:
By the way, I am finally starting again to work on the ECMAScript/SVG binding (not Inkscape scripting). I checked in a cleaned-up directory of Mozilla's Javascript C engine. It is in /src/extension/script/js so that it can be convenient to both the SVG binding and IS scripting guys. I also started checking in a few files in /src/ecma for testing. Hopefully in a few days we can start seeing some progress. Bryce shamed me out of my lethargy with his article. ;-)
This is very cool to hear! Glad my article had some use to it. ;-)
I'm looking at the code now and have some comments.
First, can you put a README in the src/extension/script/js/ directory mentioning a) where the code was obtained and what version it is, b) who to contact about it (i.e., you), c) general info about it and the intent for including it with Inkscape, and d) that it is being used under terms of the GPL but can be used under any of the MPL, GPL, or LGPL.
For the work you're doing, are you adding or modifying any of the files in script/js/? If so, it might be worth mentioning that in the README too.
Bryce
Bryce Harrington wrote:
On Thu, 3 Jun 2004, Bob Jamison wrote:
By the way, I am finally starting again to work on the ECMAScript/SVG binding (not Inkscape scripting). I checked in a cleaned-up directory of Mozilla's Javascript C engine. It is in /src/extension/script/js so that it can be convenient to both the SVG binding and IS scripting guys. I also started checking in a few files in /src/ecma for testing. Hopefully in a few days we can start seeing some progress. Bryce shamed me out of my lethargy with his article. ;-)
This is very cool to hear! Glad my article had some use to it. ;-)
I'm looking at the code now and have some comments.
First, can you put a README in the src/extension/script/js/ directory mentioning a) where the code was obtained and what version it is, b) who to contact about it (i.e., you), c) general info about it and the intent for including it with Inkscape, and d) that it is being used under terms of the GPL but can be used under any of the MPL, GPL, or LGPL.
Will do. I pruned out all of the unnecessary files from the distro, and in addition to that file, I probably should also put a copy of mozilla.org's license file in there, as it is theirs, after all. I already had a few lines describing this in one of the /ecma/*.cpp files, but I will expound further.
For the work you're doing, are you adding or modifying any of the files in script/js/? If so, it might be worth mentioning that in the README too.
No, of the files which I checked in, I have touched none of them. I have only added Makefile(s) which fit into our build structure. I think that using a pristine libjs.a in our app is another bit of evidence we can use to add to our "compliance" claim.
Bob
On Mon, 7 Jun 2004, Bob Jamison wrote:
For the work you're doing, are you adding or modifying any of the files in script/js/? If so, it might be worth mentioning that in the README too.
No, of the files which I checked in, I have touched none of them. I have only added Makefile(s) which fit into our build structure. I think that using a pristine libjs.a in our app is another bit of evidence we can use to add to our "compliance" claim.
Agreed, that's a good idea. After sending the email I saw the directory where you're adding the code to handle hooking in the js code, keeping it separate from the js core code. Good approach.
If you think there are areas you could use other people's assistance (such as adding run buttons to the GUI, etc.), it could be useful to start working on making a todo list somewhere convenient.
Bryce
If you think there are areas you could use other people's assistance (such as adding run buttons to the GUI, etc.), it could be useful to start working on making a todo list somewhere convenient.
Bryce
I don't want to break the build, or add any bugs, but I don't think that this stuff will affect anyone at all, at least for the foreseeable future. Keep in mind that the libjs code will never change, and is also rather small, though it is a lot of small C files. So it should not add to the build burden.
However..... ;-)
...actually, if someone could take the /src/extension/script/js/Makefile and add its info to the main build tree, that would be a good start. I think they are using Makefile_insert or something.
Also, a menu item like "test script" or "run" or some name like that would be useful, and have it execute the static method:
Inkscape::EcmaBinding::testMe()
would be awesome.
Bob
participants (3)
-
Bob Jamison -
Bryce Harrington -
Kees Cook