IE6 FIX
Exciting things are happening in the tech department, at least exciting for the geeks:
At the moment I'm working more or less 100% on both the plugin and the website.
The website is nearly there, and the plugins currently undergoes huge changes:
I ported the code to XCode from CodeWarrior to be able to use GCC and GCJ (Gnu Compiler for Java) instead of the Java Virtual Machine. The advantage of this is that both the plugin and the JavaScript engine are compiled to native code, which starts up and runs faster and uses less memory. But it still behaves just like it did when running in the virtual machine, even Rhino's java bridge is still there. Also, through the use of CNI (Compiled Native Interface) instead of JNI, interfacing with the Adobe SDK will be much easier in future add ons (maybe I even port the old classes to CNI).
The only problem is that AWT does not work, so Graphics2D, platform Fonts (through Java), BufferedImages, etc are not supported anymore.
But that's where the second good news come in: Instead of AWT, I was trying out SWT today (IBM's windowing framework that Eclipse is based on), which is open source and compiles just fine with GCJ. I wanted to see if that interferes with Illustartor's event loop and UI. And I couldn't believe my eyes to see that it worked! Before, AWT was deadlocking and therefore the virtual machine had to be started in headless mode.
So now Scriptographer can use SWT, and through SwingWT AWT, so even Rhino's graphical debugger which is based on AWT will finally work. And I'm sure that there are some nice source code coloring editors based on SWT out there that could be integrated as well, to finally get to something that looks like a proper IDE.
And the third good news is that there is a similar project out there, whose author Geoff strom is already working on an IDE and a debugger that probably could be integrated in Scriptographer too:
http://bantengproject.org/
So this is all very exciting, but before I really start with all this, I should focus on releasing the current version that depends on the Java Virtual Machine properly. Once that's done, work on the above will continue.
At the moment I'm working more or less 100% on both the plugin and the website.
The website is nearly there, and the plugins currently undergoes huge changes:
I ported the code to XCode from CodeWarrior to be able to use GCC and GCJ (Gnu Compiler for Java) instead of the Java Virtual Machine. The advantage of this is that both the plugin and the JavaScript engine are compiled to native code, which starts up and runs faster and uses less memory. But it still behaves just like it did when running in the virtual machine, even Rhino's java bridge is still there. Also, through the use of CNI (Compiled Native Interface) instead of JNI, interfacing with the Adobe SDK will be much easier in future add ons (maybe I even port the old classes to CNI).
The only problem is that AWT does not work, so Graphics2D, platform Fonts (through Java), BufferedImages, etc are not supported anymore.
But that's where the second good news come in: Instead of AWT, I was trying out SWT today (IBM's windowing framework that Eclipse is based on), which is open source and compiles just fine with GCJ. I wanted to see if that interferes with Illustartor's event loop and UI. And I couldn't believe my eyes to see that it worked! Before, AWT was deadlocking and therefore the virtual machine had to be started in headless mode.
So now Scriptographer can use SWT, and through SwingWT AWT, so even Rhino's graphical debugger which is based on AWT will finally work. And I'm sure that there are some nice source code coloring editors based on SWT out there that could be integrated as well, to finally get to something that looks like a proper IDE.
And the third good news is that there is a similar project out there, whose author Geoff strom is already working on an IDE and a debugger that probably could be integrated in Scriptographer too:
http://bantengproject.org/
So this is all very exciting, but before I really start with all this, I should focus on releasing the current version that depends on the Java Virtual Machine properly. Once that's done, work on the above will continue.
Scripts
13.10.08, 01:28
03.10.08, 00:01
18.09.08, 20:43
16.09.08, 21:36
14.09.08, 18:50
Posts
03.01.09, 20:57
02.01.09, 20:40
29.12.08, 18:05
29.12.08, 10:20
27.12.08, 14:28
Example of the Moment
Donation