Dev-Picayune

I just completed converting Brandon Corfman’s Python + Tkinter Splines program over to wxPython. You can find more details about my little effort here. I have also changed all the projects internally to have their own directory so that source and related materials won’t all run together. Along with that, I have created a separate Misc. menu item to throw smaller projects into.

In their recent Clarion DevCon 2004 Sessions Overview there is some talk of the Clarion .NET project.

The Clarion .NET project provides an easy way to port existing Clarion applications to the .NET platform. The compiler also supports several language extensions that provide access to the .NET platform specific features from the Clarion language. The main project goal is to produce a Clarion .NET compiler that is both a Full Producer and a CLS Consumer. Programs that are compiled by a CLS-consuming compiler can access all of the functionality of all CLS-compliant libraries. Find out how you’ll be able to run on top of the .NET Framework, without having to rebuild your applications from the ground up, and find out what the technology like Longhorn, Yukon and Avalon mean
for Clarion.

Now there is one session, I’d kind of like to go to. However, knowing what I know now, I really don’t care too much about it. Trying to hold on to Clarion is just like holding on to a safety line that eventually going to disintegrate — just got to let go and keep on moving. I don’t mean to say that I don’t want the work to succeed. But for me, I am more interested in the future of IronPython.