Saturday, November 27, 2004
progress

I just sent this to the FrontierKernel list:

I just checked in some changes in the sidewinder branch that allow the calling of Python code from UserTalk.

This also implies that the Python kernel verbs are not necessary, as they were used as a substitute for this functionality. So as of now, you can program Python in a script window, and it will execute just like any other UserTalk script. Try calling a Python script from the Quick Script window... it just works. (Note that this does not mean that you can code Python in the quick script window.)

I haven't hooked up the error routines properly, so right now, if there is a syntax error in your Python, the error goes to the console (or into the ether, if there is no console). So this is not really quite ready for primetime yet, but is a good technology demonstration. Actually, there are quite a few things that haven't been properly hooked up yet, but we will get to it.

If you are curious, please build the code and test it out. I'm not quite sure what is involved with getting Sourceforge to automatically build Frontier, but I would like to somehow start making builds available so that more bugs can be found.

So please, give it a try. I feel as if the effort has gotten over a hump with the bits of functionality that have been checked in.

dave



7:32:28 PM    comments ()  trackback []  
adventures in comprehension

The process of learning a new system is fascinating. As you poke around the system, learning each part, at first all of the parts have to be memorized by rote. Each piece is memorized, and you have to hold all of those concepts and steps in your head.

Then you get it. Something happens, and you understand the system. Rather than holding each step in your head by rote, it now flows easily as one obvious step leads into another. The weight of all of those steps in your head is replaced by the much lighter burden of understanding.

I bring this up because I just hit one of those moments in Sidewinder. I've been struggling with the task of tying Python into the general purpose script editing system built into Frontier, and I reached a point where it all started making sense. Suddenly I see what was getting in my way, and why it made sense to do it that way.

It's a wonderful moment.

I think my favorite part was when I successfully executed a Python script that was stored in a database table from the Quick Script window.

Now, don't get too excited, right now it only works for scripts that don't take parameters, but that's just a matter of type conversion, for which I've already got a head start.

It's also really cool when you are walking in uncharted territory and suddenly you pop out of the woods into familiar territory. That's how this feels right now. It feels like I'm close to pulling it all together.



2:24:11 PM    comments ()  trackback []