yea, kixforms requiring .net 1.1 to run has been a bitter part lately.
having done some development on kf.net myself, I would love the chance to retarger it for something newer and maybe even improve it.

I am not totally sure but think steelkix was build around a language framework where you give rules how things should behave and the interpreter does the heavy lifting.
I was planning in the beginning of doing that too, but because of the free nature of kixtart language, I ended up going other way. Even though I took out one layer of code processing in the earlier builds, I still think kixnet is more complex than kixtart itself. And thus I don't believe steelkix and kixnet having really anything in common.

and yes, I wrote all of it. might be something that isn't working right (as proven) as when I wrote it, I went through all of it in couple months with little sleep or social interaction. and I am ready grateful that Shane helped me with the macro's, even though they are not the hardest part, saved my fingers a lot \:\)

and like said before, debug isn't there. that was a choice in the beginning to save some time and make a compatible engine asap. I have debugging code but I wipe it out when I publish the build because it doesn't work the same as normal user would expect ;\)
another not working bit is sendmessage() as that is not supported by OS since XP sp2 (iirc). so I didn't enable it.

Open sourcing is definitely a choice. just need to, when I have time, go and compare different licensing options there are.
_________________________
!

download KiXnet