Skip to main content

Greasemonkey Paving the Way for Frankenstein Software?

I'm not real big into Greasemonkey, and I've never written a userscript, but I love what they can do for me. Blogger drafts are posted for the time I post them, not when I originally wrote them, just like I wanted when I first started using Blogger. Gmail labels can be color coded. There is a huge array of improvements to existing webapps, and what can be done beyond that is amazing. The biggest impact is to webapps, rather than websites. The impact is both in the current set of modified apps, and in what it means for the software landscape. There have been plenty of people to suggest this, but if you haven't heard it you should consider what the greasemonkey mentality could lead to in making software fit every individual user's needs better. Firefox extensions have a lot in common, not surprisingly, sometimes altering core fundamentals of the program to tailor better for users who are frustrated with something that other user's might enjoy perfectly. This kind of pick-your-parts software customizing is going to increase, and sooner or later the developers will emprace it and we might even see webapps that function as a base and implement some more of their functionality as userscripts. What if greasemonkey started to recognize a way for websites to publish large sets of userscripts that apply to them, and you could easily enable or disable the ones you want. The application would become a channel for its own customization through external scripts, lower the bar to using the scripts drastically. Just how much development could we push into userscripts, and how much of a framework could we build out of them, to make them more stable between versions, work together more safely, and one day be able to build entire apps with them? Can the userscript concept go beyond the web? How could something be implemented for a Python or Java application?

Comments

Matthew Marshall said…
"""
Just how much development could we push into userscripts, and how much of a framework could we build out of them, to make them more stable between versions, work together more safely, and one day be able to build entire apps with them? Can the userscript concept go beyond the web? How could something be implemented for a Python or Java application?
"""

I've been working on something along those lines. Hopefully I can start tech/prealpha releases within a month or so.

MWM
Anonymous said…
What if greasemonkey started to recognize a way for websites to publish large sets of userscripts that apply to them, and you could easily enable or disable the ones you want.

That would be so cool. I run across a lot of posts from people that don't know about the very extensive scripts that exist and dramatically change the webapp.

I'm not sure that complex web apps will embrace greasemonkey addons soon. I know that the gmail faqs take a negative/dismissive stance towards addon scripts but I don't know of any others that even acknowledge them.

Just how much development could we push into userscripts ... [could we] one day be able to build entire apps with them?

I'm rather into greasemonkey hacking, and have a particular interest in completely redesigning websites I frequent. By looking at the url structure and the basic layout of a page, it's quite possible to generate your own data feeds for websites by screen scraping the page.

The DOM isn't terrible as a screen scraping environment, there are usually a few bits of semantic info in the page which improves resilience, but you still have problems with site redesigns. Unfortunately, I get distracted and don't finish my projects.

I have a half complete redesign and had just completed the scraper when they redid the site for HTML 4.0. I got annoyed and dropped the project.

Similarly, I have a parser for oreilly's safari that can grab the full contents of a book when you hit the book index. I intended to create a nice columned layout but got distracted by work projects and haven't gotten back to it.

Alas, too many ideas. Not enough time.

As for userscripts in python programs, it seems the answer is eggs. Ian Bicking gave a talk on it at PyCon and the TurboGears project makes fairly heavy use of eggs as plugins.

Karl "grayrest" Guertin -- I refuse to sign up for a blogger account

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…

Finding "One Game A Month"

I was really excited about the One Game A Month challenge as soon as I heard about it.
For about two years I've struggled in fits and starts to make my way into game development. This hasn't been productive in any of the ways I hoped when I started. Its really difficult to be fairly experienced as a developer, which I believe I am in my day job as a web developer, while struggling really hard at an area in which your experience just doesn't exist.
Its like being a pilot who doesn't know how to drive.

But this challenge provided a new breath to this little hobby of mine. It gave me a scaffolding to experiment, to learn, to reflect on finished projects. I had spent far too much time on game projects that stretched on far past their exciting phases, bogged down by bad decisions and regret.
And it has worked.
I have a lot to learn. I have a lot of experience to gain through trial and error and mistake and discovery. I have a lot of fun to be had making more small games t…