including documentation for new features
CSS fix for nested lists
if there are no \!SLIDE markers in the markdown file, then make every…
… H1 define a new slide
remove execute bit from static file
set version to 0.4.2.alexch
'showoff serve' can take an argument to specify presentation directory
CSS changes (nested lists are bulleted; plain text isn't tiny)
added ? as an alias for toggle help; updated help box to include most…
… key commands
improve CSS for nested bullet lists, subsection titles
don't fail if there's no showoff.json file
bump version (for alexch patches)
make small bullets more legible
refactoring: make showoff.json a method call
pres_file option which to override the name of the 'showoff.json' fil…
…e, to allow several different presentations which share sections
I feel stupid - I honestly didn't even know you could do this in markdown.
bump version to 0.5.0
This will not do what you think. What you want is:
c.desc "Presentation directory"
c.flag [:pres_dir,:pres-dir] # I like dashes :)
c.action do |global_options,options,args|
ShowOff.run! :host => options[:h], :port => options[:p].to_i, :pres_dir => options[:pres_dir]
What you have works incidentally, but you didn't actually specify a flag named pres_dir so it won't get documented and can't be specified via a command-line option
I didn't want it specified via an option... just as an argument, e.g. "showoff serve foo". It felt right as an argument since we are serving that directory. Is there a reason to make it an option instead? Seemed like just more typing to me.
Also, I figured out CLI better and it up to where it's supposed to be in a later commit: 186bedc#L59R59
I see; I didn't see your later commit. I dunno; my opinion is everything should be an option and that the actual arguments should be reserved for glob-friendly things (which, arguably, don't make sense for showoff anyway, so it's probably moot)
I like this feature, but I'm not sure I would know what it was; what about
c.desc 'JSON file used to drive presentation'
+1, this is awesome. I have typed :1,$s/^#/<!SLIDE>^V^M/g so many times in vi…
There should also be "showoff slidify" which does that and saves it, but this is good to bootstrap an existing Markdown file. (Suggestions welcome for a better command name :-))
btw, my fork now has code that makes all H1s create a new slide (unless they're the first thing on a slide) --
see c8f9451 and c84e41f
(or wait for me to get around to making a proper pull request)
Most of the CLI documentation is/can be generated. If you run bin/showoff rdoc, it will create showoff.rdoc which is generated docs for all of the command-line arguments and interface. You can just drop that in to replace the existing section and don't have to maintain it by hand.
bugfix: stop using gemspec directive, since showoff.gemspec loads stu…
…ff that's not necessarily there yet
plus I've been doing a lot more on my main branch... I'll organize it into branches soon