Since we're all just making up stuff, I mostly agree with Ben that if
a spreadsheet is the right tool, then use that tool. There are a few
spreadsheets that support version control internally, like Google Docs
and Microsoft Office Version Tracking.

In addition, there are the elite tools of graybeard grognards like
Emacs org-mode spreadsheets and your truly best option 'sc' [1],
because these have plain-text version-control system friendly formats
from the get-go. `sc` is the only way I spreadsheet. n00bs.

Jay

1. man page from FreeBSD:
https://www.freebsd.org/cgi/man.cgi?query=sc&apropos=0&sektion=0&manpath=FreeBSD+6.0-RELEASE+and+Ports&format=html

On Fri, Oct 21, 2016 at 12:16 PM, Ben Greenman
<[email protected]> wrote:
> I vote that you stick with Excel & change the version control protocol.
>
> Maybe:
> http://stackoverflow.com/a/17106035/5237018
>
> On Fri, Oct 21, 2016 at 9:22 AM, Matthias Felleisen <[email protected]>
> wrote:
>>
>>
>> See Claire’s paper on cKanren. Scheduling is one of her examples (though
>> small scale).
>>
>>
>>
>> > On Oct 21, 2016, at 7:18 AM, Robby Findler <[email protected]>
>> > wrote:
>> >
>> > Whaaaa? You're not going to design your own language and implement a
>> > syntax colorer in DrRacket for it so they can tell immediately when
>> > something goes wrong?  ;)
>> >
>> > Robby
>> >
>> >
>> > On Fri, Oct 21, 2016 at 12:21 AM, 'John Clements' via Racket Users
>> > <[email protected]> wrote:
>> >> Yet another totally off-topic question for you extremely smart people.
>> >> Well, it’s a language design question, so it’s not *too* off-topic.
>> >>
>> >> I’m temporarily serving as my department’s scheduler (don’t ask).
>> >> Currently, the planning for the future schedule is done using an Excel
>> >> spreadsheet. I try not to hate Microsoft products for knee-jerk reasons, 
>> >> but
>> >> the simple fact is that this format is completely not git-versionable.
>> >>
>> >> This file has to be shared with non-programmers, though it doesn’t
>> >> necessarily have to be *edited* by non-programmers, just read.
>> >>
>> >> I’m currently thinking that the best compromise may be YAML. E.G.
>> >>
>> >> # 2017-2018 schedule:
>> >> alincoln : {fall: [304, 428], winter: [409, special], spring: []} #
>> >> maybe theater?
>> >> gwashington: {fall: [224, 287, 110], winter: sabbatical, spring: [789]}
>> >> # might be able to hire stuffy?
>> >> stuffy: {fall: [234,234,234], winter: [235, 235, 235]}
>> >> …
>> >>
>> >> It looks like a fairly dense format, it’s a text file so it’s
>> >> versionable in a sane way, and you could be fairly flexible in your 
>> >> parsing.
>> >>
>> >> To be fair, sexprs also look pretty good:
>> >>
>> >> ;; 2017-2018 schedule
>> >> ((alincoln ((fall (304 428)) (winter (409 special)) (spring ()))) ;;
>> >> maybe theater?
>> >> (gwashington ((fall (224 287 110)) (winter sabbatical) (spring (789))))
>> >> ;; might be able to hire stuffy?
>> >> (stuffy ((fall (234 234 234)) (winter 235 235 235))))
>> >>
>> >> Also note that there’s no need for this file to contain any information
>> >> about times and rooms, just a mapping from instructor/quarter
>> >> to classes taught, with room for comments.
>> >>
>> >> I thought hard about scribble and JSON (and xml, yecch), but I think
>> >> that YAML and sexps are the two viable candidates, and I’m guessing that 
>> >> if
>> >> non-programmers have to edit it, they’ll be less likely to botch the YAML
>> >> one.
>> >>
>> >> Any opinions?
>> >>
>> >> John
>> >>
>> >>
>> >>
>> >>
>> >> --
>> >> You received this message because you are subscribed to the Google
>> >> Groups "Racket Users" group.
>> >> To unsubscribe from this group and stop receiving emails from it, send
>> >> an email to [email protected].
>> >> For more options, visit https://groups.google.com/d/optout.
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> > Groups "Racket Users" group.
>> > To unsubscribe from this group and stop receiving emails from it, send
>> > an email to [email protected].
>> > For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Racket Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Racket Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.



-- 
Jay McCarthy
Associate Professor
PLT @ CS @ UMass Lowell
http://jeapostrophe.github.io

           "Wherefore, be not weary in well-doing,
      for ye are laying the foundation of a great work.
And out of small things proceedeth that which is great."
                          - D&C 64:33

-- 
You received this message because you are subscribed to the Google Groups 
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to