Aram Hăvărneanu
unread,Jun 11, 2013, 10:27:27 AM6/11/13Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Péter Szilágyi, Nico, golang-nuts
The present tool is a tool for people giving talks. They are the
users of the tool. It's analogous to Powerpoint and Keynote, except
it's easier to use, at least for a programmer. It's text, so it can
be versioned controlled, processed by Unix tools, etc. It's also
particularly useful for giving Go talks.
The people that see the slides are not the users of the tool. The
people writing talks and delivering them are. Because the tool
produces HTML slides, they are very easy to share with an audience,
but the audience is only a passive, secondary user. The presenter
is the the primary user of the tool.
Tools like this require an invisible interface when delivering the
talk. It is not a webpage, it is a special tool. The reasons should
be obvious, but it seems some people have a hard time understating
this. Every other tool like this has invisible controls and nobody
complains about that, but somehow they complain now, because it's
HTML.
The invisible interface used by the present tool is standard across
these types of tools, and very obvious in my opinion. If you can't
figure this out I doubt you are in the target audience of the talk,
so I will make no effort in explaining these things.
There are arguments to me made in making the output more tablet
friendly. I will never deliver a talk from a tablet so I don't care,
but I will support whatever effort being made by other people. I'm
talking about code here, talk is cheap.
--
Aram Hăvărneanu