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.

Comments

Anonymous said…
How to run examples?

trapdoor$ ./run-trapdoor demos.helloworld

just hangs
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.

Popular posts from this blog

Respect and Code Reviews

Code Reviews in a development team only function best, or possible at all, when everyone approaches them with respect. That’s something I’ve usually taken for granted because I’ve had the opportunity to work with amazing developers who shine not just in their technical skills but in their interpersonal skills on a team. That isn’t always the case, so I’m going to put into words something that often exists just in assumptions.
You have to respect your code. This is first only because the nature and intent of code reviews are to safeguard the quality of your code, so even having code reviews demonstrates a baseline of respect for that code. But, maybe not everyone on the team has the same level of respect or entered a team with existing review traditions that they aren’t acquainted with.
There can be culture shock when you enter a team that’s really heavy on code reviews, but also if you enter a team or interact with a colleague who doesn’t share that level of respect for the process or…

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. The only re…

How To Care If BSD, MIT, or GPL Licenses Are Used

The two recent posts about some individuals' choice of GPL versus others' preference for BSD and MIT style licensing has caused a lot of debate and response. I've seen everything as an interesting combination of very important topics being taken far too seriously and far too personally. All involved need to take a few steps back.

For the uninitiated and as a clarifier for the initiated, we're dealing with (basically) three categories of licensing when someone releases software (and/or its code):
Closed Source. Easiest to explain, because you just get nothing.GPL. If you get the software, you get the source code, you get to change it, and anything you combine it with must be under the same terms.MIT and BSD. If you get the software, you might get the source code, you get to change it, and you have no obligations about anything else you combine it with.The situation gets stickier when we look at those combinations and the transitions between them.

Use GPL code with Closed S…