Brad Cable · Home
Recent News:

Surrogafier 1.9.1b Release - Mon Dec 12 19:30:03 CST 2011
Surrogafier 1.9.1b is now public. This has many new upgrades and bugs fixed, so check it out.

I have also taken the time to set up two public installs of this project, now that I have some more bandwidth to mess with. Both are available through SSL on a self-signed certificate.

http://surrogafier.net/
http://surrogafier.org/
https://surrogafier.net/
https://surrogafier.org/

You may also sign up for the mailing list for new updates in Surrogafier by emailing me personally at brad@bcable.net


Surrogafier Future Plan - Tue Aug 09 22:24:20 CDT 2011
I was settling in to a new job as well as a few other changes in my life, so I have had some time away from development. I'm now ready to be unlazy and start going back to work on my projects.

I have some news, as well as a detailed plan for future releases of Surrogafier. This will hopefully address some requests that have come in over the last couple of months.

Also, make sure to remind/bug me about all of this, seriously. I have a full time tech job and suffer from chronic laziness outside of work, so the more I get bugged the better. It's for my own good, anyway. It's not like I have any children or family to blame.

Here's the todo:
  1. Finish loose ends with Facebook (bugs that were half fixed), and postpone full support of Facebook (for now, see below, I know a lot of you want this). There might be rudimentary support for Facebook at this point, as last I checked it was almost done. They added features since then, so I'm not sure where I stand anymore. The bugs that I did fix with Facebook should make large improvements for other sites, though.

  2. Google's main page. Apparently it's broken, even though it's usually the first thing I test with. I must have missed something.

  3. Google's image search. Don't usually test this but it's important to support.

  4. Craigslist. I've never tested it but I have reports that it is buggy at the moment. Shouldn't be too difficult to support.

  5. Set up a (one-way) mailing list for new releases. This, along with RSS and Freshmeat, should be enough to keep people informed. I actually prefer email myself so I don't know why I didn't do this sooner.

  6. Release (0.9.1b?)

  7. Plugins support (?) or YouTube support through an option (disabled by default). I will include a FOSS video player in the dev repository, and make sure to include instructions on how to install and enable this feature.

    Also, I would like NOW for people to give me ideas on other plugins they might want, so I can decide if this is a worthwhile feature. If it's a big site, I'll probably go with it, but if not, it depends. If it's a feature, I'll probably include it no matter what. I really haven't given it much thought at the moment so a vote in either direction would have a very large sway.

  8. Release (0.9.2b?)

  9. Full Facebook support.

  10. Release (1.0.0?) - I know, you are all mind boggled that after 10 years of development I might consider a stable release version.

  11. Twitter support.

  12. Release (1.1.0?)

  13. Check to see if Google+ allows Google Apps users yet (you know, the ones that pay them?). No? Didn't think so. Ignore it, since my Google+ account was disabled for this reason.

  14. Migrate email away from Google for being tossers.

  15. Laugh at the fact that you now all think I'm British.


Facebook support coming soon! - Sun May 22 17:08:46 CDT 2011
Today I successfully got Facebook working through Surrogafier. Among quite a few other bug fixes, later this week there will be a Facebook supported Surrogafier released!

It's still buggy, for instance it's read-only for the most part and the chat is broken, but for general navigation it works pretty well. I'll obviously keep on working on improving the support as I continue to develop.

Screenshot:

http://bcable.net/surrogafier/facebook.png


Surrogafier 1.9.0b Release - Thu May 12 16:58:39 CDT 2011
Surrogafier has a new beta release, packing a new engine and a full rewrite!

So it's been, WHOA. 4 YEARS? My bad. In my defense I was in college...

Anyway, I haven't been sitting there doing nothing while working and going to school full time... I still managed to find time to put into this, so it's actually a MAJOR release. Test it! Break it! (and tell me if you do!)

This might not be perfect, as the Javascript support is more complex, so I'll be knocking out test cases on various sites for awhile. My current things on my to-do list are to get unicode working on encoded HTML forms, and then to work on getting jQuery support for sites like Twitter and Facebook.

Told you this wasn't over!

New features:

Complete new engine that has been in development for 4 years.

New encode HTML feature.

Config options are now storable in a separate config file.

Complete CSS style support with label editing and include files for header, footer, and on the URL form page.?

New privacy protection for SSL/TLS sites.

Better commenting and cleaner code. Should be faster, even.

New force options for every setting, with some other config updates, changes, and other things so make sure to look carefully at the config.

New sandbox script which runs asserts on the code (available in git repository).


Spring Semester - Fri Jun 11 16:10:03 CDT 2010
I added all the code and research projects I completed in my previous semester at ISU. Two new Git projects and one new publication.

The Go learning method failed, but provided some interesting results. It also has code that properly generates Go games from GNUGo as well as a system for representing Go games and stepping through them. This could be used to test out other theories with some simple modification. I did a write-up on it which is now listed under publications (and also in the publications repository).

The Swing based SVG editor is extremely basic and loves to chew up CPU cycles. It was probably the only Java project I actually enjoyed doing so it's here for a good Swing reference, mostly for myself, and also for if I ever get bored and need something to code. That's not likely to happen, though.