Skip to main content

Soft Announcement: Trapdoor Prototype

Previously I made a little preview of something I'm announcing today, but it is a soft announcement as I've had it on github for some time, but I haven't done anything with the project.

This is just a prototype, an experiment, and it is called Trapdoor. I don't remember why I named it Trapdoor.

Trapdoor has a simple concept, along the lines of Mozilla Prism. I wanted to take things I use to build web applications and test how they could be applied to building desktop applications. This meant two things:

1) I need to wrap up a web application in something that can be run locally.

2) I need some way to extend a web application in ways that normally only desktop applications can provide.

This has been done in the simplest way I could find, at the time, and is available on github.

extensions:
 - calculator.Calculator
js:
 - calculator.js
plugins:
 - trapdoor.contrib.windowmanager

Applications are configured through this simply manifest, where they are given extensions, plugins, and javascript. Honestly, extensions and plugins can probably be merged. They are both defined by a Python class and the object exposes methods to the Javascript, which gets loaded and initialized by the runtime. The current version includes two plugins:

trapdoor.contrib.windowmanager

This is a basic plugin that provides a simple createWindow method, through which the Javascript can create new windows with (in the future) more control than the standard Javascript APIs would otherwise provide. One thing I'll be adding to this is a fullscreen API and other properties to control the window appearance, such as borders and which controls are visible.

trapdoor.contrib.nodes

This is my favorite of the two standard plugins. Each Node is an isolated Javascript runtime, in its own global space. The application is loaded in the first node, but it can create and initialize others, allowing it to run untrusted Javascript safely. If I continue development, I hope to use this to test ways to allow community additions to software without worrying about what they are running. This is similar to how extensions and user scripts work in Firefox and Chrome.

Now, I don't know if more will come of this. I think, if it does, it should probably be evaluated if I should rewrite it based on Chromium and V8, rather than Qt and whatever Javascript engine it is running on. It is also lacking a solid use case, for me, that I can use to drive my desire to improve it. However, I had fun writing it for the thought experiment, and I do hope to do more with it in the near future.

Please, fork it and tell me what you think.

Comments

Rich Moore said…
Sounds similar to an app sebas and I wrote called selkie. http://techbase.kde.org/Projects/Silk/Selkie for more details.

Qt uses the standard webkit js engine by default. If you build it from source you can use the v8 engine however by passing the option to the build_webkit script.

Popular posts from this blog

On Pruning Your Passions

We live in a hobby-rich world. There is no shortage of pastimes to grow a passion for. There is a shortage of one thing: time to indulge those passions. If you're someone who pours your heart into that one thing that makes your life worthwhile, that's a great deal. But, what if you've got no shortage of interests that draw your attention and you realize you will never have the time for all of them?

If I look at all the things I'd love to do with my life as a rose bush I'm tending, I realize that careful pruning is essential for the best outcome. This is a hard lesson to learn, because it can mean cutting beautiful flowers and watching the petals fall to the ground to wither. It has to be done.

I have a full time job that takes a lot of my mental energy. I have a wife and a son and family time is very important in my house. I try to read more, and I want to keep up with new developments in my career, and I'm trying to make time for simple, intentional relaxing t…

The Insidiousness of The Slow Solution

In software development, slow solutions can be worse than no progress at all. I'll even say its usually worse and if you find yourself making slow progress on a problem, consider stopping while you're a head.

Its easy to see why fast progress is better: either you solve the problem or you prove a proposed solution wrong and find a better one. Even a total standstill in pushing forward on a task or a bug or a request can force you to seek out new information or a second opinion.

Slow solutions, on the other hand, is kind of sneaky. Its insidious. Slow solution is related the Sunk Cost Fallacy, but maybe worse. Slow solutions have you constantly dripping more of your time, energy, and hope into a path that's still unproven, constantly digging a hole. Slow solutions are deceptive, because they still do offer real progress. It is hard to justify abandoning it or trying another route, because it is "working", technically.

We tend to romanticize the late night hacking…

Why I Switched From Git to Microsoft OneDrive

I made the unexpected move with a string of recent projects to drop Git to sync between my different computers in favor of OneDrive, the file sync offering from Microsoft. Its like Dropbox, but "enterprise."

Feeling a little ashamed at what I previously would have scoffed at should I hear of it from another developer, I felt a little write up of the why and the experience could be a good idea. Now, I should emphasize that I'm not dropping Git for all my projects, just specific kinds of projects. I've been making this change in habit for projects that are just for me, not shared with anyone else. It has been especially helpful in projects I work on sporadically. More on why a little later.

So, what drove me away from Git, exactly?

On the smallest projects, like game jam hacks, I just wanted to code. I didn't want to think about revisions and commit messages. I didn't need branching or merges. I didn't even need to rollback to another version, ever. I just …