jclem/gifify

Thoughts on interface cleanup

Closed this issue · 4 comments

kirbysayshi commented

#11's README mentions made me wonder: are you, @jclem open, at some point, to a revamp of the flags? Some changes I've been thinking of making:

  • make -n the default behavior, or assume the command should be gifify file.mp4 | cloudup
  • remove the -o, assume user will redirect (maybe)?
  • merge -r and -s since they are dependent on each other, perhaps something like gifify -r 1.5@30 (1.5x speed, output at 30fps)

Maybe others?

jclem commented

I like the third mention there. I'm not sure what cloudup is, but I like requiring nothing other than the CloudApp app itself. That said, I'm not collecting metrics here, so I have no idea how much people are actually using the CloudApp part of it. Come to think of it, I'm not really, even.

kirbysayshi commented

Ooops! I meant cloudapp, not cloudup, and looking at the script I see it's actually the cloud command. Sorry about that. So I suppose ignore that first idea. Maybe just reverse the default, make it require a -c to send to cloudapp?

jclem commented

I've implemented this except for the piping. In my experience, people typically don't really care about the resulting filename, so I'd rather avoid requiring redirecting output.