From: Justin Collins <justincollins@...>
Date: 2013-06-20T16:11:19+09:00
Subject: Re: [Project] Mime

On 06/19/2013 11:06 PM, Brandon Weaver wrote:
> Hey Ruby-Talk,
>
> Working on a project that I'd like to get some feedback on:
> https://github.com/baweaver/mime
>
> While working on showing some newer technicians how I did things, I
> realized that I should really automate these tasks. I then took to
> making a script to do this, and halfway through thought to myself why in
> the world am I doing this? By showing them the steps I'd already done
> the task, why rewrite the entire thing? It's wasted time that can be
> trimmed up.
>
> Enter Mime.
>
> Mime is the starts of a macro engine that acts as a proxy to the shell,
> recording all of the commands and saving them into mime files for later
> playback. Using # for commenting you can write inline Markdown to
> document things as you go along, and then generate html pages for
> documentation from the code itself. The mime program itself can document
> itself if you change its extension to mime.
>
> My goal with this one is to make an application that allows for rapid
> development of sysadmin tools.
>
> Chain mime files together, combine functionality. In later releases
> there will be a fully integrated macros system that will allow for fast
> generation of code, and really pushing the limits of some of Ruby's
> dynamic features.
>
> So, any thoughts?
>
> Thanks for your time,
>
> Brandon


You might take a look at lbsh[1] which has a very similar (but not 
ruby/markdown based) idea.

-Justin

[1] http://lbsh.cs.ucla.edu/