nodezator 1.5.3__tar.gz → 1.5.5__tar.gz

{nodezator-1.5.3 → nodezator-1.5.5}/PKG-INFO

@@ -1,35 +1,30 @@
-Metadata-Version: 2.1
+Metadata-Version: 2.4
 Name: nodezator
-Version: 1.5.3
+Version: 1.5.5
 Summary: A generalist Python node editor
-Home-page: https://nodezator.com
-Author: Kennedy Richard
-Author-email: kennedy@kennedyrichard.com
+Author-email: Kennedy Richard <kennedy@kennedyrichard.com>
 License: Unlicense
-Project-URL: Source code, https://github.com/IndiePython/nodezator
-Project-URL: Forum, https://github.com/IndiePython/nodezator/discussions
-Project-URL: User manual, https://manual.nodezator.com
-Project-URL: Bug Tracker, https://github.com/IndiePython/nodezator/issues
-Project-URL: Donate, https://indiepython.com/donate
+Project-URL: Homepage, https://nodezator.com
+Project-URL: Source Code, https://github.com/IndieSmiths/nodezator
+Project-URL: Forum, https://github.com/IndieSmiths/nodezator/discussions
+Project-URL: User Manual, https://manual.nodezator.com
+Project-URL: Bug Tracker, https://github.com/IndieSmiths/nodezator/issues
+Project-URL: Donate, https://indiesmiths.com/donate
 Keywords: gui,desktop,application,pygame,pygame-ce,graph,graphs,nodes,node,editor
 Classifier: License :: OSI Approved :: The Unlicense (Unlicense)
 Classifier: Development Status :: 4 - Beta
 Classifier: Programming Language :: Python :: 3
-Classifier: Programming Language :: Python :: 3.7
-Classifier: Programming Language :: Python :: 3.8
-Classifier: Programming Language :: Python :: 3.9
-Classifier: Programming Language :: Python :: 3.10
 Classifier: Programming Language :: Python :: Implementation :: CPython
 Classifier: Topic :: Software Development
-Classifier: Topic :: Software Development :: User Interfaces
 Classifier: Topic :: Software Development :: Libraries :: pygame
+Classifier: Topic :: Desktop Environment
+Classifier: Topic :: Multimedia
 Classifier: Topic :: Software Development :: User Interfaces
 Classifier: Topic :: Software Development :: Code Generators
 Classifier: Topic :: Artistic Software
-Classifier: Topic :: Desktop Environment
-Classifier: Topic :: Multimedia
 Classifier: Topic :: Office/Business
 Classifier: Topic :: Scientific/Engineering
+Classifier: Intended Audience :: End Users/Desktop
 Requires-Python: >=3.7
 Description-Content-Type: text/markdown
 Requires-Dist: pygame-ce
@@ -69,7 +64,9 @@ main_callable = get_circle_area
 
 ![node image](https://nodezator.com/images/get_circle_area_node.png)
 
-You can store these functions/node definitions anywhere you want in your disk and once you launch Nodezator just provide the path so Nodezator can load them. The only requirement is that you organize these nodes definitions in separate files and store then in a folder (more about that further ahead in another section).
+You can store these functions/node definitions anywhere you want in your disk and once you launch Nodezator just provide the path so Nodezator can load them. The only requirement is that you organize these nodes definitions in separate files and store them in a folder. This small video (~2min) actually shows you how to define and load a node in **less than 60 seconds**:
+
+[![video: Defining and loading a node in less than 60 seconds](https://img.youtube.com/vi/cMfoaEs0fGY/hqdefault.jpg)](https://www.youtube.com/watch?v=cMfoaEs0fGY)
 
 You can actually turn **any** callable into a node very easily: classes, methods, etc. All callables available in the Python ecosystem can be turned into a node (even the ones defined in C, for instance).
 
@@ -93,14 +90,14 @@ There's also a [youtube video][] presenting Nodezator:
 
 [![thumb of youtube video](https://img.youtube.com/vi/GlQJvuU7Z_8/hqdefault.jpg)](https://www.youtube.com/watch?v=GlQJvuU7Z_8)
 
-Nodezator is made with pure Python on top of the [pygame-ce][] library (and a bit of the excellent [numpy][] library as well), by [Kennedy Richard Silva Guerra][] (born in 1990), as part of the [Indie Python][] project.
+Nodezator is made with pure Python on top of the [pygame-ce][] library (and a bit of the excellent [numpy][] library as well), by [Kennedy Richard Silva Guerra][] (born in 1990), as part of the [Indie Smiths][] project.
 
 > [!NOTE]
 > Despite being maintained mostly by a single person, Nodezator is a serious and active project that gets a couple of large releases every year.
 
 We recommend Nodezator for **intermediate Python users**. Or, in case you are not a programmer, have an intermediate Python user next to you so that person can help you set up a no-code/low-code workflow for you.
 
-Nodezator can already be used in production and supports a vast variety of workflows. It still has a long way to go, though. So, please, be patient and also consider supporting it: https://indiepython.com/donate
+Nodezator can already be used in production and supports a vast variety of workflows. It still has a long way to go, though. So, please, be patient and also consider supporting it: https://indiesmiths.com/donate
 
 After you finish reading this README file, you may also want to visit Nodezator's homepage: https://nodezator.com
 
@@ -113,7 +110,7 @@ On top of making it very easy to define nodes, Nodezator comes packed full of us
 
 As we said before, Nodezator allows you to convert callables from third-party libraries with minimal effort. Here are just a few screenshots showing the usage of Nodezator with different libraries.
 
-Here's is a simple graph showing Nodezator usage with the [Pillow](https://python-pillow.org/) library.
+Here's a simple graph showing Nodezator usage with the [Pillow](https://python-pillow.org/) library.
 
 ![Pillow demonstration](https://nodezator.com/images/nodezator_pillow_demo.png)
 
@@ -167,7 +164,7 @@ Simply put, Nodezator is just a visual, node-based representation of Python.
 
 ### Socket proximity detection
 
-Having to click exactly over a socket to drag a new connection out of it and on top of that having to drop such new connection exactly on top of another socket are both repetitive tasks that are difficult to do right in one quick motion. Often, people loose precious time trying to ensure the mouse is exactly over the desired socket, specially considering how often those tasks are performed in any graph edition session.
+Having to click exactly over a socket to drag a new connection out of it and on top of that having to drop such new connection exactly on top of another socket are both repetitive tasks that are difficult to do right in one quick motion. Often, people lose precious time trying to ensure the mouse is exactly over the desired socket, specially considering how often those tasks are performed in any graph edition session.
 
 Because of that, Nodezator features socket proximity detection to assist the user when establishing or replacing existing connection. The user doesn't need to click exactly over a socket to drag a new connection out of it anymore. Dropping the new connection exactly over the other socket isn't necessary either. As long as the mouse is close enough, these actions can be carried over effortlessly. Here you can see it in action:
 
@@ -251,6 +248,8 @@ However, users are encouraged to define their own nodes for their specific purpo
 
 ![A user-defined node](https://nodezator.com/images/node.png)
 
+In case you missed it at the beginning of this README, here's the link to a small video demonstrating how to define and load a node in less than 60 seconds: https://www.youtube.com/watch?v=cMfoaEs0fGY
+
 Nodes are created from Python scripts organized within folders that we call **node packs**. You can create a node pack folder **anywhere you want in your disk**. Under the hood, Nodezator treats it as a package in some contexts, so you can name that folder whatever you like, as long as it is a Python identifier. That is, it must start with a letter or underscore and contain only letters, digits and underscores.
 
 In other words, you **create nodes by writing Python functions/callables using your preferred text editor or IDE** and only then you **launch Nodezator in order to load them as nodes**, so you can create, edit and execute graphs.
@@ -280,7 +279,7 @@ Once you distributed your nodes, you may want a place wherein to let people know
 
 You can do all this on the [nodes gallery][] website. There you can search node packs by name, author and tags.
 
-To have a link to your node pack added to the nodes gallery/database, upload it somewhere people can download/install it from, as described in the manual's chapter about [distributing your nodes][], then submit the relevant info about your node pack in this [node pack submission form][]. Alternatively, you can also submit a pull request to the [nodes gallery repository][] on github following the instructions on the README.md file.
+To have a link to your node pack added to the nodes gallery/database, upload it somewhere people can download/install it from, as described in the manual's chapter about [distributing your nodes][], then submit the relevant info about your node pack in this [node pack submission form][]. Alternatively, you can also submit a pull request to the [nodes gallery repository][] on GitHub following the instructions on the README.md file.
 
 You can also [email][] me if you need any help.
 
@@ -326,9 +325,13 @@ The in-app version is always the most accurate, since it is updated first, where
 
 Everyone is welcome to suggest and contribute changes.
 
-If the proposed change is small enough, you can submit your pull request for analysis right away and it will be answered ASAP.
+If the proposed change is small enough, you can submit your pull request (PR) for analysis right away to the `develop` branch and it will be answered ASAP.
+
+Please, if submitting a pull request, use the `develop` branch, not the `main` branch. This way it is easier to refine/complement your changes before merging them with `main`.
+
+More complex pull requests will also be welcome in the future, but due to the complexity of the app, I will first need to finish implementing the missing system test cases to ensure everyone's future contributions do not break each other.
 
-More complex pull requests will also be welcome in the future, but due to the complexity of the app, I will first need to implement some automated GUI tests to ensure everyone's future contributions do not break each other.
+Speaking of system testing, Nodezator has system testing capabilities that take advantage of GUI automation, with a few test cases already implemented. Just press **Shift+Ctrl+F8** to see the current system test cases run automatically. Once the tests finish running, a report with the results is displayed so you can inspect them. If you need, the report can be exported to a variety of formats with the buttons at the bottom of the report. You can also configure the system testing session in the menu **Gui Automation > System testing > Setup and run custom session**.
 
 
 ## Issues
@@ -341,7 +344,7 @@ If you find a bug that...
 - causes Nodezator to crash;
 - representing something malfunctioning or not working at all;
 
-...then, please, use [github issues][] to submit an issue as soon as possible.
+...then, please, use [GitHub issues][] to submit an issue as soon as possible.
 
 Please, include as much information as you can:
 
@@ -358,20 +361,20 @@ Nevertheless, never hesitate to ask for help, even if you don't have much info a
 
 ### Minor issues
 
-If however, the problem is not as serious/urgent, that is, it doesn't cause Nodezator to crash or malfunction, then, please, open a discussion on [github discussions][] instead. There's a dedicated category for this kind of problem called "Minor issue".
+If however, the problem is not as serious/urgent, that is, it doesn't cause Nodezator to crash or malfunction, then, please, open a discussion on [GitHub discussions][] instead. There's a dedicated category for this kind of problem called "Minor issue".
 
-It doesn't mean your issue is any less important. It is just that in Nodezator and other Indie Python repos we use [github issues][] for things that crash the app or otherwise prevent the user from doing something that is supposed to be available (stuff that cause crashes or malfunctioning). When such a critical issue appears, any other work is paused and all attention is given to that issue so that it can be fixed ASAP.
+It doesn't mean your issue is any less important. It is just that in Nodezator and other Indie Smiths's repos we use [GitHub issues][] for things that crash the app or otherwise prevent the user from doing something that is supposed to be available (stuff that cause crashes or malfunctioning). When such a critical issue appears, any other work is paused and all attention is given to that issue so that it can be fixed ASAP.
 
 This measure is taken for the benefit of the users: by doing things this way, whenever you have an urgent/critical issue, it won't compete for space with other less urgent matters. We'll be able to promptly schedule time to solve the issue.
 
-Minor issues, suggestions of improvements, feature requests, feedback about bad experiences, etc. are all important, but they don't have the same urgency as something that crashes the app or causes it to malfunction. This is why we use [github discussions][] for the less urgent stuff. They'll be tended to all the same, just not with the same urgency.
+Minor issues, suggestions of improvements, feature requests, feedback about bad experiences, etc. are all important, but they don't have the same urgency as something that crashes the app or causes it to malfunction. This is why we use [GitHub discussions][] for the less urgent stuff. They'll be tended to all the same, just not with the same urgency.
 
-Of course, [github discussions][] is used for many other important stuff as well, as we'll see in the next section.
+Of course, [GitHub discussions][] is used for many other important stuff as well, as we'll see in the next section.
 
 
 ## Discussions/forum
 
-Consider [github discussions][] as the official online forum for Nodezator.
+Consider [GitHub discussions][] as the official online forum for Nodezator.
 
 It is used for many things like announcements to the community, to list planned/requested features, to communicate and discuss current work, etc.
 
@@ -392,14 +395,14 @@ If you have...
 
 Contact me any time via [Twitter/X][] or [email][].
 
-You are also welcome on the Indie Python's [discord server][].
+You are also welcome on the Indie Smiths's [discord server][].
 
 
 ## Patreon and donations
 
-Please, support Nodezator and other useful apps of the Indie Python project by becoming our patron on [patreon][]. You can also make recurrent donations using [github sponsors][], [liberapay][] or [Ko-fi][].
+Please, support Nodezator and other useful apps of the Indie Smiths project by becoming our patron on [patreon][]. You can also make recurrent donations using [GitHub sponsors][], [liberapay][] or [Ko-fi][].
 
-Both [github sponsors][] and [Ko-fi][] also accept one-time donations.
+Both [GitHub sponsors][] and [Ko-fi][] also accept one-time donations.
 
 Any amount is welcome and helps. Check the project's [donation page][] for all donation methods available.
 
@@ -413,7 +416,7 @@ The `nodezator_icons` font used in the app for its icons was created by me and i
 The logos/images listed below, featured in Nodezator's splash screen (and sometimes in other spots in the app), are all mine:
 
 - the Kennedy Richard "KR" logo;
-- the Indie Python project logo;
+- the Indie Smiths project logo;
 - the Nodezator logo;
 - the robot, called Zenith Green, Nodezator's mascot.
 
@@ -435,19 +438,19 @@ Also, other parts of the code, despite being carefully designed, might be redesi
 [youtube video]: https://www.youtube.com/watch?v=GlQJvuU7Z_8
 [pygame-ce]: https://pyga.me
 [numpy]: https://numpy.org
-[Indie Python]: https://indiepython.com
+[Indie Smiths]: https://indiesmiths.com
 
 [manual]: https://manual.nodezator.com
 
 [Twitter/X]: https://x.com/KennedyRichard
 [email]: mailto:kennedy@kennedyrichard.com
-[discord server]: https://indiepython.com/discord
+[discord server]: https://indiesmiths.com/discord
 
 [patreon]: https://patreon.com/KennedyRichard
-[github sponsors]: https://github.com/sponsors/KennedyRichard
+[GitHub sponsors]: https://github.com/sponsors/KennedyRichard
 [liberapay]: https://liberapay.com/KennedyRichard
 [Ko-fi]: https://ko-fi.com/kennedyrichard
-[donation page]: https://indiepython.com/donate
+[donation page]: https://indiesmiths.com/donate
 
 [defining your first node]: https://manual.nodezator.com/ch-defining-your-first-node.html
 [loading nodes]: https://manual.nodezator.com/ch-loading-nodes.html
@@ -455,10 +458,10 @@ Also, other parts of the code, despite being carefully designed, might be redesi
 [nodes gallery]: https://gallery.nodezator.com
 
 [node pack submission form]: https://docs.google.com/forms/d/e/1FAIpQLSd1XceOnzEeaBZcpkkXEFiAVO_5YUbd43sieQUekh1PZ8dm5A/viewform?usp=sf_link
-[nodes gallery repository]: https://github.com/IndiePython/gallery.nodezator.com
+[nodes gallery repository]: https://github.com/IndieSmiths/gallery.nodezator.com
 
-[github issues]: https://github.com/IndiePython/nodezator/issues
-[github discussions]: https://github.com/IndiePython/nodezator/discussions
+[GitHub issues]: https://github.com/IndieSmiths/nodezator/issues
+[GitHub discussions]: https://github.com/IndieSmiths/nodezator/discussions
 
 [The Unlicense]: https://unlicense.org/
 [Open Font License]: https://en.wikipedia.org/wiki/SIL_Open_Font_License

{nodezator-1.5.3 → nodezator-1.5.5}/README.md

@@ -32,7 +32,9 @@ main_callable = get_circle_area
 
 ![node image](https://nodezator.com/images/get_circle_area_node.png)
 
-You can store these functions/node definitions anywhere you want in your disk and once you launch Nodezator just provide the path so Nodezator can load them. The only requirement is that you organize these nodes definitions in separate files and store then in a folder (more about that further ahead in another section).
+You can store these functions/node definitions anywhere you want in your disk and once you launch Nodezator just provide the path so Nodezator can load them. The only requirement is that you organize these nodes definitions in separate files and store them in a folder. This small video (~2min) actually shows you how to define and load a node in **less than 60 seconds**:
+
+[![video: Defining and loading a node in less than 60 seconds](https://img.youtube.com/vi/cMfoaEs0fGY/hqdefault.jpg)](https://www.youtube.com/watch?v=cMfoaEs0fGY)
 
 You can actually turn **any** callable into a node very easily: classes, methods, etc. All callables available in the Python ecosystem can be turned into a node (even the ones defined in C, for instance).
 
@@ -56,14 +58,14 @@ There's also a [youtube video][] presenting Nodezator:
 
 [![thumb of youtube video](https://img.youtube.com/vi/GlQJvuU7Z_8/hqdefault.jpg)](https://www.youtube.com/watch?v=GlQJvuU7Z_8)
 
-Nodezator is made with pure Python on top of the [pygame-ce][] library (and a bit of the excellent [numpy][] library as well), by [Kennedy Richard Silva Guerra][] (born in 1990), as part of the [Indie Python][] project.
+Nodezator is made with pure Python on top of the [pygame-ce][] library (and a bit of the excellent [numpy][] library as well), by [Kennedy Richard Silva Guerra][] (born in 1990), as part of the [Indie Smiths][] project.
 
 > [!NOTE]
 > Despite being maintained mostly by a single person, Nodezator is a serious and active project that gets a couple of large releases every year.
 
 We recommend Nodezator for **intermediate Python users**. Or, in case you are not a programmer, have an intermediate Python user next to you so that person can help you set up a no-code/low-code workflow for you.
 
-Nodezator can already be used in production and supports a vast variety of workflows. It still has a long way to go, though. So, please, be patient and also consider supporting it: https://indiepython.com/donate
+Nodezator can already be used in production and supports a vast variety of workflows. It still has a long way to go, though. So, please, be patient and also consider supporting it: https://indiesmiths.com/donate
 
 After you finish reading this README file, you may also want to visit Nodezator's homepage: https://nodezator.com
 
@@ -76,7 +78,7 @@ On top of making it very easy to define nodes, Nodezator comes packed full of us
 
 As we said before, Nodezator allows you to convert callables from third-party libraries with minimal effort. Here are just a few screenshots showing the usage of Nodezator with different libraries.
 
-Here's is a simple graph showing Nodezator usage with the [Pillow](https://python-pillow.org/) library.
+Here's a simple graph showing Nodezator usage with the [Pillow](https://python-pillow.org/) library.
 
 ![Pillow demonstration](https://nodezator.com/images/nodezator_pillow_demo.png)
 
@@ -130,7 +132,7 @@ Simply put, Nodezator is just a visual, node-based representation of Python.
 
 ### Socket proximity detection
 
-Having to click exactly over a socket to drag a new connection out of it and on top of that having to drop such new connection exactly on top of another socket are both repetitive tasks that are difficult to do right in one quick motion. Often, people loose precious time trying to ensure the mouse is exactly over the desired socket, specially considering how often those tasks are performed in any graph edition session.
+Having to click exactly over a socket to drag a new connection out of it and on top of that having to drop such new connection exactly on top of another socket are both repetitive tasks that are difficult to do right in one quick motion. Often, people lose precious time trying to ensure the mouse is exactly over the desired socket, specially considering how often those tasks are performed in any graph edition session.
 
 Because of that, Nodezator features socket proximity detection to assist the user when establishing or replacing existing connection. The user doesn't need to click exactly over a socket to drag a new connection out of it anymore. Dropping the new connection exactly over the other socket isn't necessary either. As long as the mouse is close enough, these actions can be carried over effortlessly. Here you can see it in action:
 
@@ -214,6 +216,8 @@ However, users are encouraged to define their own nodes for their specific purpo
 
 ![A user-defined node](https://nodezator.com/images/node.png)
 
+In case you missed it at the beginning of this README, here's the link to a small video demonstrating how to define and load a node in less than 60 seconds: https://www.youtube.com/watch?v=cMfoaEs0fGY
+
 Nodes are created from Python scripts organized within folders that we call **node packs**. You can create a node pack folder **anywhere you want in your disk**. Under the hood, Nodezator treats it as a package in some contexts, so you can name that folder whatever you like, as long as it is a Python identifier. That is, it must start with a letter or underscore and contain only letters, digits and underscores.
 
 In other words, you **create nodes by writing Python functions/callables using your preferred text editor or IDE** and only then you **launch Nodezator in order to load them as nodes**, so you can create, edit and execute graphs.
@@ -243,7 +247,7 @@ Once you distributed your nodes, you may want a place wherein to let people know
 
 You can do all this on the [nodes gallery][] website. There you can search node packs by name, author and tags.
 
-To have a link to your node pack added to the nodes gallery/database, upload it somewhere people can download/install it from, as described in the manual's chapter about [distributing your nodes][], then submit the relevant info about your node pack in this [node pack submission form][]. Alternatively, you can also submit a pull request to the [nodes gallery repository][] on github following the instructions on the README.md file.
+To have a link to your node pack added to the nodes gallery/database, upload it somewhere people can download/install it from, as described in the manual's chapter about [distributing your nodes][], then submit the relevant info about your node pack in this [node pack submission form][]. Alternatively, you can also submit a pull request to the [nodes gallery repository][] on GitHub following the instructions on the README.md file.
 
 You can also [email][] me if you need any help.
 
@@ -289,9 +293,13 @@ The in-app version is always the most accurate, since it is updated first, where
 
 Everyone is welcome to suggest and contribute changes.
 
-If the proposed change is small enough, you can submit your pull request for analysis right away and it will be answered ASAP.
+If the proposed change is small enough, you can submit your pull request (PR) for analysis right away to the `develop` branch and it will be answered ASAP.
+
+Please, if submitting a pull request, use the `develop` branch, not the `main` branch. This way it is easier to refine/complement your changes before merging them with `main`.
+
+More complex pull requests will also be welcome in the future, but due to the complexity of the app, I will first need to finish implementing the missing system test cases to ensure everyone's future contributions do not break each other.
 
-More complex pull requests will also be welcome in the future, but due to the complexity of the app, I will first need to implement some automated GUI tests to ensure everyone's future contributions do not break each other.
+Speaking of system testing, Nodezator has system testing capabilities that take advantage of GUI automation, with a few test cases already implemented. Just press **Shift+Ctrl+F8** to see the current system test cases run automatically. Once the tests finish running, a report with the results is displayed so you can inspect them. If you need, the report can be exported to a variety of formats with the buttons at the bottom of the report. You can also configure the system testing session in the menu **Gui Automation > System testing > Setup and run custom session**.
 
 
 ## Issues
@@ -304,7 +312,7 @@ If you find a bug that...
 - causes Nodezator to crash;
 - representing something malfunctioning or not working at all;
 
-...then, please, use [github issues][] to submit an issue as soon as possible.
+...then, please, use [GitHub issues][] to submit an issue as soon as possible.
 
 Please, include as much information as you can:
 
@@ -321,20 +329,20 @@ Nevertheless, never hesitate to ask for help, even if you don't have much info a
 
 ### Minor issues
 
-If however, the problem is not as serious/urgent, that is, it doesn't cause Nodezator to crash or malfunction, then, please, open a discussion on [github discussions][] instead. There's a dedicated category for this kind of problem called "Minor issue".
+If however, the problem is not as serious/urgent, that is, it doesn't cause Nodezator to crash or malfunction, then, please, open a discussion on [GitHub discussions][] instead. There's a dedicated category for this kind of problem called "Minor issue".
 
-It doesn't mean your issue is any less important. It is just that in Nodezator and other Indie Python repos we use [github issues][] for things that crash the app or otherwise prevent the user from doing something that is supposed to be available (stuff that cause crashes or malfunctioning). When such a critical issue appears, any other work is paused and all attention is given to that issue so that it can be fixed ASAP.
+It doesn't mean your issue is any less important. It is just that in Nodezator and other Indie Smiths's repos we use [GitHub issues][] for things that crash the app or otherwise prevent the user from doing something that is supposed to be available (stuff that cause crashes or malfunctioning). When such a critical issue appears, any other work is paused and all attention is given to that issue so that it can be fixed ASAP.
 
 This measure is taken for the benefit of the users: by doing things this way, whenever you have an urgent/critical issue, it won't compete for space with other less urgent matters. We'll be able to promptly schedule time to solve the issue.
 
-Minor issues, suggestions of improvements, feature requests, feedback about bad experiences, etc. are all important, but they don't have the same urgency as something that crashes the app or causes it to malfunction. This is why we use [github discussions][] for the less urgent stuff. They'll be tended to all the same, just not with the same urgency.
+Minor issues, suggestions of improvements, feature requests, feedback about bad experiences, etc. are all important, but they don't have the same urgency as something that crashes the app or causes it to malfunction. This is why we use [GitHub discussions][] for the less urgent stuff. They'll be tended to all the same, just not with the same urgency.
 
-Of course, [github discussions][] is used for many other important stuff as well, as we'll see in the next section.
+Of course, [GitHub discussions][] is used for many other important stuff as well, as we'll see in the next section.
 
 
 ## Discussions/forum
 
-Consider [github discussions][] as the official online forum for Nodezator.
+Consider [GitHub discussions][] as the official online forum for Nodezator.
 
 It is used for many things like announcements to the community, to list planned/requested features, to communicate and discuss current work, etc.
 
@@ -355,14 +363,14 @@ If you have...
 
 Contact me any time via [Twitter/X][] or [email][].
 
-You are also welcome on the Indie Python's [discord server][].
+You are also welcome on the Indie Smiths's [discord server][].
 
 
 ## Patreon and donations
 
-Please, support Nodezator and other useful apps of the Indie Python project by becoming our patron on [patreon][]. You can also make recurrent donations using [github sponsors][], [liberapay][] or [Ko-fi][].
+Please, support Nodezator and other useful apps of the Indie Smiths project by becoming our patron on [patreon][]. You can also make recurrent donations using [GitHub sponsors][], [liberapay][] or [Ko-fi][].
 
-Both [github sponsors][] and [Ko-fi][] also accept one-time donations.
+Both [GitHub sponsors][] and [Ko-fi][] also accept one-time donations.
 
 Any amount is welcome and helps. Check the project's [donation page][] for all donation methods available.
 
@@ -376,7 +384,7 @@ The `nodezator_icons` font used in the app for its icons was created by me and i
 The logos/images listed below, featured in Nodezator's splash screen (and sometimes in other spots in the app), are all mine:
 
 - the Kennedy Richard "KR" logo;
-- the Indie Python project logo;
+- the Indie Smiths project logo;
 - the Nodezator logo;
 - the robot, called Zenith Green, Nodezator's mascot.
 
@@ -398,19 +406,19 @@ Also, other parts of the code, despite being carefully designed, might be redesi
 [youtube video]: https://www.youtube.com/watch?v=GlQJvuU7Z_8
 [pygame-ce]: https://pyga.me
 [numpy]: https://numpy.org
-[Indie Python]: https://indiepython.com
+[Indie Smiths]: https://indiesmiths.com
 
 [manual]: https://manual.nodezator.com
 
 [Twitter/X]: https://x.com/KennedyRichard
 [email]: mailto:kennedy@kennedyrichard.com
-[discord server]: https://indiepython.com/discord
+[discord server]: https://indiesmiths.com/discord
 
 [patreon]: https://patreon.com/KennedyRichard
-[github sponsors]: https://github.com/sponsors/KennedyRichard
+[GitHub sponsors]: https://github.com/sponsors/KennedyRichard
 [liberapay]: https://liberapay.com/KennedyRichard
 [Ko-fi]: https://ko-fi.com/kennedyrichard
-[donation page]: https://indiepython.com/donate
+[donation page]: https://indiesmiths.com/donate
 
 [defining your first node]: https://manual.nodezator.com/ch-defining-your-first-node.html
 [loading nodes]: https://manual.nodezator.com/ch-loading-nodes.html
@@ -418,10 +426,10 @@ Also, other parts of the code, despite being carefully designed, might be redesi
 [nodes gallery]: https://gallery.nodezator.com
 
 [node pack submission form]: https://docs.google.com/forms/d/e/1FAIpQLSd1XceOnzEeaBZcpkkXEFiAVO_5YUbd43sieQUekh1PZ8dm5A/viewform?usp=sf_link
-[nodes gallery repository]: https://github.com/IndiePython/gallery.nodezator.com
+[nodes gallery repository]: https://github.com/IndieSmiths/gallery.nodezator.com
 
-[github issues]: https://github.com/IndiePython/nodezator/issues
-[github discussions]: https://github.com/IndiePython/nodezator/discussions
+[GitHub issues]: https://github.com/IndieSmiths/nodezator/issues
+[GitHub discussions]: https://github.com/IndieSmiths/nodezator/discussions
 
 [The Unlicense]: https://unlicense.org/
 [Open Font License]: https://en.wikipedia.org/wiki/SIL_Open_Font_License

nodezator-1.5.5/nodezator/__init__.py

@@ -0,0 +1,4 @@
+from .appinfo import MINIMAL_VERSION_STRING
+
+
+__version__ = MINIMAL_VERSION_STRING

{nodezator-1.5.3 → nodezator-1.5.5}/nodezator/__main__.py

@@ -4,10 +4,11 @@ Nodezator: A generalist Python node editor developed by
 Kennedy Richard <kennedy@kennedyrichard.com>.
 
 https://kennedyrichard.com
+https://bsky.app/profile/kennedyrichard.com
 https://x.com/KennedyRichard
 
 https://nodezator.com
-https://github.com/IndiePython/nodezator
+https://github.com/IndieSmiths/nodezator
 """
 
 ### standard library imports

{nodezator-1.5.3 → nodezator-1.5.5}/nodezator/appinfo.py

@@ -20,7 +20,9 @@ from collections import namedtuple
 
 AppVersion = namedtuple("AppVersion", "major minor micro release_level")
 
-APP_VERSION = AppVersion(1, 5, 3, "release_candidate")
+APP_VERSION = AppVersion(1, 5, 5, "release_candidate")
+
+MINIMAL_VERSION_STRING = '.'.join(map(str, APP_VERSION[:3]))
 
 
 ### titles for the application
@@ -33,7 +35,7 @@ TITLE = "Nodezator"
 ## supported by any major operating system;
 APP_DIR_NAME = "nodezator"
 
-ORG_DIR_NAME = 'IndiePython' # org name for pygame.system.get_pref_path
+ORG_DIR_NAME = 'IndieSmiths' # org name for pygame.system.get_pref_path
 
 ABBREVIATED_TITLE = "NDZ"
 

{nodezator-1.5.3 → nodezator-1.5.5}/nodezator/audioplayer.py

@@ -1,6 +1,8 @@
+"""Facility for playing audio."""
+
 ### third-party imports
 
-from pygame import Rect
+from pygame import Rect, error as PygameError
 
 from pygame.locals import (
     QUIT,
@@ -91,7 +93,18 @@ PLAYING_ICON = render_layered_icon(
 logger = get_new_logger(__name__)
 
 
+UNAVAILABLE_AUDIO_MESSAGE = (
+    "An error ocurred while trying to set the audio volume"
+    " (for usage by the widget that plays audio files to"
+    " preview them). You can still use Nodezator normally,"
+    " you just won't be able to listen to audio files within"
+    " the widget until you figure out the problem. Please, check"
+    " the audio on your system."
+)
+
+
 class AudioPlayer(Object2D):
+
     def __init__(self):
         """"""
 
@@ -137,11 +150,7 @@ class AudioPlayer(Object2D):
         )
 
         ###
-
         self.volume = 0.4
-        music.set_volume(self.volume)
-
-        ###
 
         volume_area = self.volume_area = Rect((0, 0), (100, 30))
 
@@ -189,6 +198,34 @@ class AudioPlayer(Object2D):
 
     def play_audio(self, audio_paths, index=0):
 
+        ### try setting the volume
+
+        try:
+            music.set_volume(self.volume)
+
+        ### if a pygame error occurs at this spot, it might
+        ### mean the mixer wasn't initialized properly due to
+        ### a problem on the user's system (at least it happened
+        ### before and it is the reason this check exists)
+        ###
+        ### inform the user of the problem its implications and
+        ### leave the player immediately by returning earlier
+
+        except PygameError:
+
+            logger.exception(UNAVAILABLE_AUDIO_MESSAGE)
+            USER_LOGGER.exception(UNAVAILABLE_AUDIO_MESSAGE)
+
+            dialog_message = UNAVAILABLE_AUDIO_MESSAGE + (
+                " Check the user log for details (on the graph/canvas,"
+                " press <Ctrl+Shift+j> or access the \"Help > Show user"
+                " log\" option on the menubar)."
+            )
+
+            create_and_show_dialog(dialog_message, level_name='error')
+
+            return
+
         self.audio_paths = (
             [audio_paths] if isinstance(audio_paths, str) else audio_paths
         )
@@ -328,7 +365,7 @@ class AudioPlayer(Object2D):
             try:
                 music.load(self.audio_path)
 
-            except Exception as err:
+            except Exception:
 
                 log_message = (
                     "An error ocurred while trying to"

{nodezator-1.5.3 → nodezator-1.5.5}/nodezator/config.py

@@ -82,9 +82,13 @@ SYSTEM_TESTING_DATA_DIR = DATA_DIR / "system_testing"
 APP_COLORS_FILE = DATA_DIR / "app_themes" / "emeralds_on_coal.pyl"
 
 
-### writeable path for config/logs, etc.
+### writeable paths for config/logs, etc.
 WRITEABLE_PATH = Path(get_pref_path(ORG_DIR_NAME, APP_DIR_NAME))
 
+### previous writeable path, that uses the previous name of
+### nodezator's parent project
+OLD_WRITEABLE_PATH = Path(get_pref_path('IndiePython', APP_DIR_NAME))
+
 
 ### check whether ffmpeg (and ffprobe) is available, storing
 ### the info as a boolean

{nodezator-1.5.3 → nodezator-1.5.5}/nodezator/data/aww/manual.nodezator.pysite/ch-defining-complex-viewer-nodes.htsl

@@ -189,7 +189,7 @@ main_callable = view_points
 
 <p>Before you delve into the code, however, I'd like to point out that <b>there is no perfect or correct way of defining loops in pygame</b>. You can use functions or classes, but even when using classes there are different ways to do it. I could even have split the node script into different modules to make the separation between the different parts even more clear.</p>
 
-<p>Do not stress over the details. The code to be presented is just what I thought was the best solution for what was needed. As long as you understand the purpose of the individual pieces you'll be able to come up with your own solutions. You are also always welcome to ask on <a href="https://indiepython.com/discord">discord</a> or <a href="https://github.com/IndiePython/nodezator/discussions">github discussions</a> every time you have questions.</p>
+<p>Do not stress over the details. The code to be presented is just what I thought was the best solution for what was needed. As long as you understand the purpose of the individual pieces you'll be able to come up with your own solutions. You are also always welcome to ask on <a href="https://indiesmiths.com/discord">discord</a> or <a href="https://github.com/IndieSmiths/nodezator/discussions">GitHub discussions</a> every time you have questions.</p>
 
 <p>First of all, we have the imports and the definition of constants:</p>
 

{nodezator-1.5.3 → nodezator-1.5.5}/nodezator/data/aww/manual.nodezator.pysite/ch-distributing-nodes.htsl

@@ -142,7 +142,7 @@
 
 <p>Beware that this template does not attempt to teach you the best way or configuration for your package. It just presents <b>one</b> possible and relatively straightforward way of packaging your node pack. Teaching about packaging in Python and the many options available is outside the scope of our project.</p>
 
-<p>Even so, we always welcome questions and people seeking help, so if you have any trouble just reach us on <a href="https://github.com/IndiePython/nodezator/discussions">github discussions for Nodezator</a> or the <a href="https://indiepython.com/discord">Indie Python discord server</a>.</p>
+<p>Even so, we always welcome questions and people seeking help, so if you have any trouble just reach us on <a href="https://github.com/IndieSmiths/nodezator/discussions">GitHub discussions for Nodezator</a> or the <a href="https://indiesmiths.com/discord">Indie Smiths discord server</a>.</p>
 
 
 <p><a href="ch-other-objects.htsl">Previous chapter</a> | <a href="index.htsl">Table of contents</a> | <a href="ch-conditional-execution.htsl">Next chapter</a></p>

{nodezator-1.5.3 → nodezator-1.5.5}/nodezator/data/aww/manual.nodezator.pysite/ch-loading-nodes.htsl

@@ -25,7 +25,7 @@
     <li>How to reference them in the .ndz file.</li>
 </ol>
 
-<p>If you ever encounter any kind of problem, with those or any other task you are trying to perform in Nodezator, don't hesitate to seek help on the <a href="https://indiepython.com/discord">discord server</a>.</p>
+<p>If you ever encounter any kind of problem, with those or any other task you are trying to perform in Nodezator, don't hesitate to seek help on the <a href="https://indiesmiths.com/discord">discord server</a>.</p>
 
 <p>Without further ado, let's learn how to do those things.</p>
 
@@ -223,9 +223,9 @@ pip install mynodepack
 
 <p>Hence, if you change the name of parameters/outputs or make other changes that result in an incompatible signature, your file will become invalid or you'll have to update the .ndz file by hand yourself.</p>
 
-<p>A feature that consists in a conflict resolution mode for Nodezator, to guide the user in the resolution of such problems is already listed among the <a href="https://github.com/IndiePython/nodezator/discussions/13">planned/requested features for Nodezator</a>.</p>
+<p>A feature that consists in a conflict resolution mode for Nodezator, to guide the user in the resolution of such problems is already listed among the <a href="https://github.com/IndieSmiths/nodezator/discussions/13">planned/requested features for Nodezator</a>.</p>
 
-<p>For now, if you want to update the signature of a node that is in use, it is easier to delete the instances of that node in the related .ndz files, make your changes, than instantiate and reconnect the node again. Or just seek help on the <a href="https://indiepython.com/discord">discord server</a>.</p>
+<p>For now, if you want to update the signature of a node that is in use, it is easier to delete the instances of that node in the related .ndz files, make your changes, than instantiate and reconnect the node again. Or just seek help on the <a href="https://indiesmiths.com/discord">discord server</a>.</p>
 
 
 <p><a href="ch-more-ways-define-nodes.htsl">Previous chapter</a> |  <a href="index.htsl">Table of contents</a> | <a href="ch-color-coding-inputs-outputs.htsl">Next chapter</a></p>

{nodezator-1.5.3 → nodezator-1.5.5}/nodezator/data/aww/manual.nodezator.pysite/ch-more-advanced-viewer-node-features-part2.htsl

@@ -22,7 +22,7 @@
 
 <p>Of course, if your cneeds are different, the <a href="https://pyga.me">pygame-ce</a> specifics to produce the specific visualization you need will be different.</p>
 
-<p>Such pygame-ce specifics are beyond our purpose/responsibility, since this is not a pygame-ce manual, but instead aims only to connect your pygame-ce knowledge with Nodezator tools. Still, when possible, we do want to offer additional guidance, even if outside the scope of our activities/responsibilities. Just keep going forward with your studies and reach out for help whenever needed in our <a href="https://indiepython.com/discord">discord server</a> or <a href="https://github.com/IndiePython/nodezator/discussions">Nodezator GitHub discussions</a>.</p>
+<p>Such pygame-ce specifics are beyond our purpose/responsibility, since this is not a pygame-ce manual, but instead aims only to connect your pygame-ce knowledge with Nodezator tools. Still, when possible, we do want to offer additional guidance, even if outside the scope of our activities/responsibilities. Just keep going forward with your studies and reach out for help whenever needed in our <a href="https://indiesmiths.com/discord">discord server</a> or <a href="https://github.com/IndieSmiths/nodezator/discussions">Nodezator GitHub discussions</a>.</p>
 
 <p>Nonetheless, keep in mind that no amount of examples will ever be enough to demonstrate all that you can achieve with pygame-ce for your custom visualizations. There simply isn't a single right way to do everything. This is not a bad thing, it only means pygame-ce is that much versatile (or more precisely, it provides bindings for the versatile underlying <a href="https://www.libsdl.org/">SDL</a> library). It all depends on factors like your proficiency with pygame-ce and the type of visualization you want for the data with which you are dealing.</p>
 

{nodezator-1.5.3 → nodezator-1.5.5}/nodezator/data/aww/manual.nodezator.pysite/index.htsl

@@ -10,7 +10,7 @@
 
 <p>Welcome to the nodezator manual. This guide is meant for Nodezator's users.</p>
 
-<p>You may also want to take a look at the <a href="https://github.com/IndiePython/nodezator/blob/main/README.md">README</a> file of Nodezator's repository, since it showcases a lot of Nodezator's features and capabilities. Or you may want to <a href="https://gallery.nodezator.com">download example nodes</a>, like the ones used in the <a href="https://www.youtube.com/watch?v=GlQJvuU7Z_8">video presenting Nodezator</a>.</p>
+<p>You may also want to take a look at the <a href="https://github.com/IndieSmiths/nodezator/blob/main/README.md">README</a> file of Nodezator's repository, since it showcases a lot of Nodezator's features and capabilities. Or you may want to <a href="https://gallery.nodezator.com">download example nodes</a>, like the ones used in the <a href="https://www.youtube.com/watch?v=GlQJvuU7Z_8">video presenting Nodezator</a>.</p>
 
 
 <h2>Table of contents</h2>