Quick answer to the guy who used yesterday’s Form Experiment to ask what’s happening with SdiDesk …

Here’s the status report :

1) In the last couple of weeks I quit my job and moved back to the UK … which has been taking up quite a lot of my time and energy.

2) Once we’ve settled in, I hope I can get some time to focus on my projects … including SdiDesk (and GeekWeaver, MTC etc.) The good thing, no more distractions from my previous demanding day-job. The bad thing, after a brief holiday I need to find work in the UK. (Offers, tips and suggestions are, of course, welcome)

3) SdiDesk was converted to VB.NET this year. And the source-code in progress is available on Google Code.

4) I am NOT a VB.NET programmer, and frankly, from the little I’ve played with it so far, I’m not very excited about getting more involved. I admired VB exactly because the combined language + IDE made Windows programming mindlessly easy. Throw away that virtue (as VB.NET seems to have done, and I’m blaming the new, incredibly sluggish and cluttered VS2008 as much as changes to the language) and it has little to recommend it against other languages.

5) On the hand, I’m a pragmatist and often able to find something interesting pretty much anywhere. I also know that in a recession I may not be able to be too fussy when it comes to getting a job. So I will be spending a bit more time over the next month or so tidying up the VB.NET codebase, fixing some egregious issues, and making an installer. It’s going to be useful to me to be able to say that I can operate in the VB.NET world, and produce working products.

6) Longer term, my preference and commitment is still to a Python SdiDesk-like thing. And most-likely a Python server with UI in the browser (javascript etc.) I’ve cooled towards the idea of Flex (mainly because my trial copy expired and I remembered all the problems of depending on proprietory software)

The attraction of anything other than the browser has always been the vector drawing in the network diagramming part of the software. But I’m sure that if I just wait a little bit longer, the browser will eventually be able to handle this too.

7) As always, I’m not unaffected by user feedback and other things going on in my life 🙂 … if there’s suddenly a surge in interest or demand for a VB.NET SdiDesk then I may reconsider.

8) Joe Question asks : “how risky is it to commit myself to SdiDesk.NET then? What about all my pages?” Answer : SdiDesk.NET reads your existing PageStore files. There may be some issues with the size of the diagrams, but everything works. If it doesn’t, tell me.

However, you can’t even try SdiDesk.NET currently unless you’re a VB programmer because it’s only available in source form. There will certainly be a build for end-users this year and it will read your existing PageStore. The main reason you want this is if you’re an existing SdiDesk user who has moved (or will move soon) to Vista where the old VB6 version won’t run.

I’m always committed to upgrade compatibility. You’ll be able to move your existing SdiDesk pages to SdiDesk.NET, and you’ll be able to import them into a future Python version.

Adobe Thermo looks interesting.

At first, of course, it looks just like another Visual Basic which is of note only because it targets Flex (and hence the Flash Virtual Machine).

But it’s clever in the way that it imports Photoshop files and takes advantage of some of the logical structure.

Not for me, though, obviously.

Update : for people wondering how the whole new-SdiDesk-in-Adobe-Flex? thing is going. I solved something I thought was a problem yesterday.

I now have a (very fragile) Flex front end which can pass plain-text GeekWeaver programs to a web-server with GeekWeaver embedded, and get a compiled chunk of GeekWeaver out.

That’s very cool … unfortunately it also revealed yet more problems with the GeekWeaver compiler which need fixing before I can release the next version.

Still, it looks promising. The signs are better and better that something interesting is coming out in the next 3 months. 🙂

Just spent the last few hours downloading and playing with the beta of Flex 3, Adobe’s IDE for Rich Internet Applications (ie. applications running on the Flash Virtual Machine) which is based on Eclipse and has an XML-based UI / form description language more or less like HTML.

I’m having two thoughts about it. One is a kind of sigh of relief. This is, after all, finally, The One. After years of fruitless searching I’m pretty sure here’s a framework I can settle down with and commit to, and start making babies with. At least, it’s more or less mature enough, handsome enough and well endowed enough to put these thoughts into a girl’s head. A browser and a desktop? Holidays in Windows, Mac and Linux? Own grid and canvas. Tabbed notebook and some cute chunky buttons.

And it’s all done in a way that’s pretty self-evident when you look at a few examples. Forms and input widgets are described in XML. They layout nice; and you can start banging them in and prototyping the look of your interface in a couple of minutes. The round-trip from coding to running and testing is a bit slow on my poor 512MB Vista laptop, but it’s going to be bearable. And the Eclipsyness of it all is comfortingly familiar if a trifle overblown.

As long as my next experiments turn out right (the one where I try to find a tutorial example of pulling data off a server over http, and the one where I try to compile with AIR into a stand-alone application) then I’m sold.

But there’s another part of me going, “huh? Is this all there is? WTF?”

I mean, it’s 2007 and I’m happy because I’ve finally found a way to make GUIs that’s sufficiently lower than my pain threshold that I might actually get a piece of software released again. Zowie! But that’s what I had with Visual Basic 6 – which came out in about 1997!

In fact, I was already a Pythonista before I started writing SdiDesk in VB. And I only pulled out VB (a language I thought I’d left behind for good) because I got impatient to see what the UI of an SdiDesk could look like and thought I’d prototype it. As often happens, the prototype spiraled out of control as I kept thinking, “maybe I can just also add … ” and within a month or so it had already started to grow into a real program. Another phase of development with some serious refactoring and cleaning up the internal architecture, and it was a quite respectable and powerful bit of software (If I say so myself; I’m talking about the time I made the tutorial screen-casts.)

(Then, of course, I hit the crisis of not wanting to be on the Microsoft treadmill and forced to upgrade to .NET; even though it was obvious that VB6 was as extinct as a very extinct thing from the Lower Devonian period. But also of not having any viable alternative. )

So there’s a sense that Flex smells extraordinarily similar. I can see how you can knock out your prototype interface and start building backwards from it. That feels good. That’s why it seems like this is plausible option to get development rolling again.

But, like I say, it *is* basically what I had 10 years ago. Except with javascript dressed up in Java’s suit and tie to look more grown-up and respectable. And XML.

In fact, I was gchatting to Zbigniew earlier today, and realizd that all of this stuff is hardly a big advance on Hypercard back in 1985. Or perhaps Smalltalk 1972. Why the hell haven’t we progressed further? Why am I struggling on each new platform to rediscover the level of comfort I had on the previous one? What’s going wrong here?

I suppose it could just be that the idea of quick GUI builders is inherent in the idea of a GUI?

Or maybe we programmers of the noughties need to get our acts together and start coming up with serious new, cool shit. Stuff which couldn’t have been thought up in the 60s and 70s. Stuff which is radically easier and more productive than something we had 10 years ago. Something like reinventing Lisp with a cleaner (non)syntax … erm … well anyway, I’m off to do more experiments with Flex and try to get it to talk to some kind of server.

If I succeed, then expect to see some interesting developments along the lines I mentioned earlier today … steps towards a new SdiDesk, possibly a GeekWeaver development environment … maybe even the long fabled, but never released SystemSketch. Or even the more outré things I’ve got buzzing around in my fevered imagination like “SexyCells” and “FlowerBrush”.

Of course, it still sucks that Flex / Flash seems to have no musical ability whatsoever so Gbloink! doesn’t look like an option. Which is a double pity because I think it would make a great Chumby widget and that would have justified me buying one.

🙁