About the author

Steven Harmansteven harman :: makes sweet software with computers!

For recent posts and more about me, scroll to the bottom.

Sponsors

Subscribe

  • Subscribe to my feed. via RSS
  • Subscribe via email via email

It's been a while... a LONG while.

OK, so its been quite a while since my last post... almost 4 months it looks like. I don't really have any excuses other than, I've been lazy. Well, thatch not entirely true... its more like I've been BUSY! I mean, summer happened, and that naturally means tons of stuff to do. So, since my last post: Anyhow, like I was saying... its not really an excuse, so much as an explanation. Now, onto the actual update: The subText Project.
subText is a personal blog publishing platform that focuses on usability, elegance, and simplicity. If you've ever caught yourself throwing your hands in the air and declaring that you're going to write your own blogging engine, then subText is for you. subText is an open source project licensed under the BSD license. It is a fork of the popular dotText blogging platform.
Currently, I'm focusing on an import Framework for subText that will allow users to import content (posts, comments, trackbacks, pictures [well we'll have to see about this one], etc...) from their existing blog into a subText installation. For the initial release we'll only support importing from an existing dotText (v. 0.95) blog. Though the Framework allows blog specific Import Providers to be plugged-in, so it should be pretty easy for someone to build a provider for their blog platform of choice. For example, I imagine there will will a good bit of interest in being able to import a Community Server blog setup into subText (since CS is where a good bit of the old dotText community went). With the Import Provider framework, the bulk of the work would be figuring out the data-mappings from CS to sT [I think that will be my new shorthand for subText]. And then whip together a new provider class (which can be based on the existing dotText v0.95 provider), do some tweaking, and BAM! You can import your CS content into your brand-spankin-new subText platform. What's easier than that? OK, so I obviously glazed over the nitty-gritty...so if you want more specific info, send a message to the subText Developer's Mailing List.

So, I think that's enough on subText for now... I think I hear a few pints calling my name.

What others are saying.

# CVS - Keeping your branch(es) in sync...
Gravatar StevenHarman.net
Nov 02, 2005
...the first thing I did was create a branch off of subText proper. The idea was that I would simply make my changes, test them, etc... and then at some point merge back into TRUNK. Good in theory, except that shortly after I branched, some of the other guys starting making a lot of changes to TRUNK, and my branch was quickly way out of date. Normally this isn't an issue b/c the merge will take care of. However, some of the changes on TRUNK were changes to the subText.Framework and I needed
Comments have been closed on this topic.