From: Psionic K <psionik@positron.solutions>
To: emacs-orgmode@gnu.org
Subject: dslide 0.4.0, last unstable release
Date: Sat, 25 May 2024 23:36:06 +0900 [thread overview]
Message-ID: <CADQMGASncZDS4nX8Z3pvtYa=n4tAqf9JbcpiUz_y+yMNQL544A@mail.gmail.com> (raw)
Dslide (Domain Specific sLIDEs) is a rethought, mostly complete
rewrite of org-tree-slide.
Its highlight features:
- using babel blocks
- per-slide configuration
- extensible via custom actions and support for custom EIEIO classes
There is a file in the /test directory called demo.org. You can see
the presentation with `dslide-deck-start' or `dslide-deck-develop' to
watch progress updates be highlighted.
You need my other package, `master-of-ceremonies' to complete the last
slides of the presentation.
https://github.com/positron-solutions/master-of-ceremonies
There are a few areas I plan to change where feedback could be
beneficial. Stop me if any of these choices seem unintuitive.
I plan to get rid of the idea of independent `DSLIDE_SLIDE_ACTION' and
`DSLIDE_SLIDE_CHILD_ACTION' and instead combine the child and slide
behaviors into several distinct slide classes. The user will set
`DSLIDE_CLASS` to achieve the combination of these two options. They
will still accept plist style arguments for small behavior tweaks.
Per-slide actions will still be supported, via `DSLIDE_EXTRA_ACTIONS'
or `DSLIDE_ACTIONS' to completely override the normal actions set via
customize or document properties.
A user asked me to enable hiding babel blocks via setting the
`:exports none`. I'm not sure if this is consistent with other uses
of that option.
My other option was to re-use the babel block keywords that are
usually already present, adding just "hide" to the normal list of
method names. You can reply directly if you like:
https://github.com/positron-solutions/dslide/issues/1
reply other threads:[~2024-05-25 14:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADQMGASncZDS4nX8Z3pvtYa=n4tAqf9JbcpiUz_y+yMNQL544A@mail.gmail.com' \
--to=psionik@positron.solutions \
--cc=emacs-orgmode@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/emacs/org-mode.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).