unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thorsten Wilms <t_w_@freenet.de>
To: guix-devel@gnu.org
Subject: Re: Outreachy project infrastructure
Date: Thu, 22 Nov 2018 13:32:18 +0100	[thread overview]
Message-ID: <b6d3e326-b507-0041-fa18-20c7fc0d0437@freenet.de> (raw)
In-Reply-To: <87h8ga2hhg.fsf@elephly.net>

On 21/11/2018 23.28, Ricardo Wurmus wrote:
>> Thank you very much for the workflow as well as for the suggested tools. I
>> did not know that slides were created with inkscape :)

> I’ve been using Inkscape for all of my presentations (after exporting to
> PDF).  It’s more flexible than software made specifically for
> presentations, but the flexibility comes at the cost of convenience
> (e.g. in Inkscape you have one file per slide, and to create a slide
> deck you need to combine all these files to a single PDF with another
> tool like Ghostscript).  In this project I think the flexibility
> outweighs these minor drawbacks.

Years ago, I created dozens of presentations with Impress (then 
OpenOffice, now it would be LibreOffice). I shudder at the though of 
doing more involved presentations with Inkscape, even though it's my 
primary bread and butter tool :)

Impress may quite likely be the most mature and full-featured Free 
Software WYSIWYG presentation tool. That said, of course it may seem a 
bit clunky and the file format is not suited for versioning and 
manipulation from external tools.

Even though Inkscape saves unpacked SVG, it's not version control 
friendly, either. AFAIK, Inkscape tends to reorganize more of the SVG 
than necessary, when saving after a change.

Main issues I see in using Inkscape for presentations:
1. Lack of master pages (page templates)
2. Lack of text-styles
3. Much harder to see and edit the sequence of pages

On 1: There are at least 2 approaches to achieve a similar feature via 
scripting.

On 2: I guess this can be done with CSS.

Inkscape presentation extension "JessyInk" seems to offer helpful 
features, but I worry that there's no straight way to get the kind of 
export out of it, that you need.
http://tavmjong.free.fr/INKSCAPE/MANUAL/html/Extensions-JessyInk.html

Still, the concept of using several layers in one file might be 
worthwhile. An export script could toggle layer visibility before 
calling inkscape with --export-ps (or -png or -pdf). I recently did 
something like that, where the central bash script line is:

xmlstarlet ed -P -S -L -u "//_:g[@inkscape:label='templates']/@style" -v 
display:none $file

That is: Edit the file in-place and set the display attribute of a group 
that has the label 'templates' to none. Thus the layer won't appear in 
export.

Instead of bash and xmlstarlet, a Racket or Guile script may end up 
longer, but more readable :)

Looking for a Guile presentation tool, I found out that Andy Wingo went 
down that route and further:
https://wingolog.org/archives/2007/07/11/fold-xml-presentations

For maximal version-control-friendliness and guaranteed consistency, one 
would have to opt for entirely script-driven slide generation. Aside of 
something Latex-based, there's:
https://wingolog.org/projects/guile-present/doc/
https://docs.racket-lang.org/slideshow/


-- 
Thorsten Wilms

thorwil's design for free software:
http://thorwil.wordpress.com/

  parent reply	other threads:[~2018-11-22 12:35 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-21 13:51 Outreachy project infrastructure Gábor Boskovits
2018-11-21 14:37 ` Laura Lazzati
2018-11-21 15:34   ` Julien Lepiller
2018-11-21 15:19 ` Ricardo Wurmus
2018-11-21 20:18   ` Laura Lazzati
2018-11-21 22:28     ` Ricardo Wurmus
2018-11-22  1:13       ` Laura Lazzati
2018-11-22 12:32       ` Thorsten Wilms [this message]
2018-11-22 13:12         ` Ricardo Wurmus
2018-11-22 14:23           ` Thorsten Wilms
2018-11-22 20:11     ` Björn Höfling
2018-11-23  1:54       ` Laura Lazzati
2018-11-23  9:04       ` Ricardo Wurmus
2018-11-23 10:24         ` Gábor Boskovits
2018-11-23 11:01           ` Ricardo Wurmus
2018-11-23 11:38             ` Gábor Boskovits
2018-11-23 12:27               ` Ricardo Wurmus
2018-11-25 23:08         ` Björn Höfling
2018-11-26  0:30           ` Laura Lazzati
2018-11-26 14:07             ` Björn Höfling
2018-11-26 15:40               ` Laura Lazzati
2018-11-29 15:19           ` Laura Lazzati
2018-11-29 15:36             ` Ricardo Wurmus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b6d3e326-b507-0041-fa18-20c7fc0d0437@freenet.de \
    --to=t_w_@freenet.de \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).