[nongnu] elpa/dslide 6a8897f592 174/230: version 0.4.0, some breaking changes

[ELPA Syncer]

branch: elpa/dslide
commit 6a8897f59287b21ea0bd79d3b51b4110d7e42261
Author: Psionik K <73710933+psionic-k@users.noreply.github.com>
Commit: Psionik K <73710933+psionic-k@users.noreply.github.com>

    version 0.4.0, some breaking changes
    
    Child actions that were fiddled with for 0.3.x might break with 0.4.0, not 
that
    any of this should have been stable.  It was very fiddly to write child 
actions
    in 0.4.0
    
    In 0.5.0, there is a strong chance that I combine child / slide action into 
just
    multiple slide classes
    
    Repeated development is revealing inherent coupling between the child and 
slide
    action.  Their lifecycles are ambiguously encompassing and only the slide 
object
    will be able to figure this out.
    
    On the plus-side, it makes configuring the slides much, much easier.  Some 
of
    the hydration code will die
    
    The downside is that slide and child action won't be independent able to
    articulate, but like I said, for the most part, they are not independent at 
all,
    and what you want to do with the children is affected by what you do with 
the
    slide, especially the restriction handling
    
    Signed-off-by: Psionik K <73710933+psionic-k@users.noreply.github.com>
---
 README.org | 3 ++-
 dslide.el  | 2 +-
 2 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/README.org b/README.org
index 5c9b38afc3..b2f6f40e1e 100644
--- a/README.org
+++ b/README.org
@@ -22,11 +22,12 @@ Fully programmable sequences behind a two-button interface:
 - Integration with Elisp programs and arbitrary Emacs buffers
 - Custom class support for extending the framework
 ** Status 🛠️
-Version 0.3.2 👷
+Version 0.4.0 👷
 - Stabilizing the API and naming (as in not stable yet)
 - Gathering user feedback & experience
 - Accepting PR's and issue reports
 - Composed children actions coming soon™
+  + This is very close.  I will likely combine the "parent" and "child" 
actions into new slide classes instead because their behavior is inherently 
coupled and requires coordination on the slide class.
 
 The user-facing API will look pretty similar to what is already there today, 
but if any keys change, I'll call ~warn~ on the old keys.
 * Installation
diff --git a/dslide.el b/dslide.el
index 519da82ef6..ec7b2d4068 100644
--- a/dslide.el
+++ b/dslide.el
@@ -4,7 +4,7 @@
 ;; Copyright (C) 2024 Positron
 ;;
 ;; Author: Positron <contact@positron.solutions>
-;; Version: 0.3.2
+;; Version: 0.4.0
 ;; Package-Requires: ((emacs "29.2"))
 ;; Maintainer: Positron <contact@positron.solutions>
 ;; URL: https://github.com/positron-solutions/dslide