Skip to main content

Dead to Me! Trapdoor, Prototyping web-based desktop applications

This is the inaugural post in my Dead to Me! series which I announced.

 I’m not gonna lie. I’m pretty proud of this one. To say Trapdoor was ahead of the times might be a stretch, but really only a small stretch.
My project README explains
Trapdoor is a web-based desktop framework. Confused yet? The idea is to leverage how much energy is put into the web today and make developing a desktop application fun again. Again? For the first time?
Trapdoor was an exploration of how to utilize web development skillsets to build desktop tools. I wanted to experiment with how this idea would play out and if it really made any sense. I was never planning Trapdoor to become are solution. I just wanted to play with the idea, but I do think I played with the idea pretty early on and that it was an extremely successful experiment.
At the time I was still a KDE user and had been learning a little bit of Qt via the Python bindings PyQt4. I knew that Qt had a WebKit widget and quickly found that PyQt4 exposed this pretty easily.
This was a simple demo I built with Trapdoor. We have a web-app built, for this simple example, all in Javascript dumping a few simple controls to the DOM. The JS is responsible for window creation and gets access to the DOM in the new window, where it can construct an interface in HTML and use jQuery to wire it up.
What I was most proud of is that, recognizing this would only be useful if the desktop applications being built could do anything a normal desktop app could do, I made it really easy to extend the Javascript APIs with new things.
The Calculator class defined in the above calculator.py file above and registered in the manifest is able to expose methods to the Javascript API it injects into the application. Otherwise, it is just regular everyday Python and can do anything and can use any Python libraries.
I only worked on Trapdoor for three days. Vaguely I recall wondering if I could write an extension that used PyOpenGL to render 3D graphics in my web-based desktop application, a good year before the WebGL spec landed and three and a half years before work would begin on Node Webkit. Trapdoor won’t be worked on by me and shouldn’t be picked up by anyone else, probably. It will continue to sit in my Github for a while, but it stay forever among my favorite personal projects.

Check it out, if you’re curious.
Labels:

Comments

Anonymous said…
How to run examples?

trapdoor$ ./run-trapdoor demos.helloworld

just hangs
3:11 AM
Calvin Spealman said…
Sorry I have not touched this code in 4 years, and I don't have an environment with the dependencies right now (I only ever tested it on Linux and I use Mac/Windows mostly now). I am really happy to see someone trying to use it, but I can't say why it would be hanging. I have not tried it on any modern version of Qt, either.
11:01 PM
Post a Comment

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on
1 comment
Read more

Statement Functions

At a small suggestion in #python, I wrote up a simple module that allows the use of many python statements in places requiring statements. This post serves as the announcement and documentation. You can find the release here . The pattern is the statement's keyword appended with a single underscore, so the first, of course, is print_. The example writes 'some+text' to an IOString for a URL query string. This mostly follows what it seems the print function will be in py3k. print_("some", "text", outfile=query_iostring, sep="+", end="") An obvious second choice was to wrap if statements. They take a condition value, and expect a truth value or callback an an optional else value or callback. Values and callbacks are named if_true, cb_true, if_false, and cb_false. if_(raw_input("Continue?")=="Y", cb_true=play_game, cb_false=quit) Of course, often your else might be an error case, so raising an exception could be useful
1 comment
Read more

How To Teach Software Development

How To Teach Software Development Introduction Developers Quality Control Motivation Execution Businesses Students Schools Education is broken. Education about software development is even more broken. It is a sad observation of the industry from my eyes. I come to see good developers from what should be great educations as survivors, more than anything. Do they get a headstart from their education or do they overcome it? This is the first part in a series on software education. I want to open a discussion here. Please comment if you have thoughts. Blog about it, yourself. Write about how you disagree with me. Write more if you don't. We have a troubled industry. We care enough to do something about it. We hark on the bad developers the way people used to point at freak shows, but we only hurt ourselves but not improving the situation. We have to deal with their bad code. We are the twenty percent and we can't talk to the eighty percent, by definition, so we need to impro
4 comments
Read more