Emacs at Lunch: Programmer Power Point

Sdílet
Vložit
  • čas přidán 1. 06. 2024
  • Dslide (formerly Macro Slides), the presentation framework
    github.com/positron-solutions...
    Master of Ceremonies, the package of less-specific tools for presentation:
    github.com/positron-solutions...
    Positron's Github Sponsors Page 🍔
    github.com/sponsors/positron-...
    Our monthly sponsors get access to a private repository containing notes for video ideas. This allows for early feedback and shaping of the direction of the channel. Published video org files may contain code snippets used in presentations.
    Subscribe and activate notifications for updates on the Emacs Speedrun, more Lunch videos, shorts, and more.
    TIMESTAMPS
    00:00 Overview
    00:21 Features
    02:11 Ecosystem Dividends
    03:55 Configuring Slides
    05:50 Extending with EIEIO
    08:00 Hooks
    09:01 Master of Ceremonies
    09:54 Publishing & Availability
    #emacs
    #programming
    #opensource
    #presentation

Komentáře • 7

  • @dziltener
    @dziltener Před 19 dny +3

    This looks very very cool and promising!

  • @Jedlmind
    @Jedlmind Před 19 dny +1

    Comment for the algorithm. Emacs!

  • @fredriklindlof8720
    @fredriklindlof8720 Před 19 dny +1

    Absolutely marvelous!
    In my daily work presentations and communication are very important and I was always looking for a way to make presentations that I would not be ashamed off from within emacs!

  • @ismbks
    @ismbks Před 19 dny +1

    EMACS

  • @finndriver1063
    @finndriver1063 Před 19 dny +3

    I would make renaming the package & prefix a subtle priority. As Emacs lacks namespacing, the require'd symbol should be clear in each exposed function & variable. hideshow has BIFs that break this and it annoys me to no end, not to mention in external packages.
    While prefixing 'macro-slides-' would be okay, Emacs has a long history of catchy titles and double entendre.
    My best attempt is 'waterslide', tagline: Slideshows that won't interrupt the flow. I've never claimed to be good at wordplay.
    I find the method names confusing, and I'll make some suggestions although I should read the code first.
    In my mind, 'ms-init' should be 'ms-begin-action', matching 'ms-end-action'; and 'ms-final' should be named for it's effect, 'ms-cleanup' or 'waterslide-action-cleanup'.
    Similarly, with the hooks:
    'ms-start-hook' sounds like it might have something to do with the 'ms-init/ms-end' methods. 'ms-begin-presentation-hook' or 'waterslide-present-hook', perhaps (if you chose M-x waterslide-present as your command).
    'ms-narrow-hook' is probably fine, but 'ms-slide-hook' or 'waterslide-step-slide-hook' would be clearer and match with 'ms-after-last-slide-hook'.
    Consider aliasing or renaming 'ms-after-last-slide-hook' to 'ms-end-presentation-hook'.
    Also, I'm always torn on start/end vs. begin/end. The latter sounds better to me. Nearly nobody uses 'finish', though.
    Finally, thank you for the videos, they're fun and I love learning modern patterns for Emacs Lisp.

    • @Positron-gv7do
      @Positron-gv7do  Před 16 dny +1

      I like begin presentation and end presentation.
      One of the main name collisions is the method `ms-step-forward` and the command `ms-forward`. Maybe... `ms-presentation-foward`. for the command
      I like begin instead of init. Since begin and end are quite common in Elisp, it makes the role of final more obvious. Is final still ambiguous to likely users? Hard for me to guess.
      `attr_methods` is definitely wrong. I mainly export org to texinfo, so I forgot that these are supposed to be namespaced over the export backend. In this case, macro slides is kind of like an export backend.
      If you have more thoughts, catch up in a few days with an issue. A new draft of the naming should be in place by then.

  • @user-tb4ig7qh9b
    @user-tb4ig7qh9b Před 19 dny +1

    Absoulte awesome ❤️