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

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 …

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…