Hi all
Is it possible to detect dependencies from within a patch?
Often people report problems without mentioning '... couldn't create' errors. Also, people not so familiar with Pd don't know what library a certain objects belongs to and maybe also don't know how to search for it in "Find externals".
I think the ability to give proper feedback at patch loading time would help to address this issue.
Roman
well, I guess that's why you have declare for.
and I once proposed this https://github.com/pure-data/pure-data/issues/281
Em seg., 22 de fev. de 2021 às 06:08, Roman Haefeli reduzent@gmail.com escreveu:
Hi all
Is it possible to detect dependencies from within a patch?
Often people report problems without mentioning '... couldn't create' errors. Also, people not so familiar with Pd don't know what library a certain objects belongs to and maybe also don't know how to search for it in "Find externals".
I think the ability to give proper feedback at patch loading time would help to address this issue.
Roman _______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
On Tue, 2021-02-23 at 14:51 -0300, Alexandre Torres Porres wrote:
well, I guess that's why you have declare for.
Sure. What I mean is there is no introspection about what [declare] actually did.
and I once proposed this https://github.com/pure-data/pure-data/issues/281
That is the discussion I was looking for. Thanks for the pointer.
Roman
On 2/22/21 10:06 AM, Roman Haefeli wrote:
Hi all
Is it possible to detect dependencies from within a patch?
Often people report problems without mentioning '... couldn't create' errors. Also, people not so familiar with Pd don't know what library a certain objects belongs to and maybe also don't know how to search for it in "Find externals".
I think the ability to give proper feedback at patch loading time would help to address this issue.
while not giving "proper feedback", there has been a feature request in deken to support something like this for ages.
i've implemented a little prototype of how it could look like: https://github.com/pure-data/deken/issues/84#issuecomment-786533931
dfmgsadr IOhannes
On Fri, 2021-02-26 at 10:52 +0100, IOhannes m zmoelnig wrote:
On 2/22/21 10:06 AM, Roman Haefeli wrote:
Hi all
Is it possible to detect dependencies from within a patch?
Often people report problems without mentioning '... couldn't create' errors. Also, people not so familiar with Pd don't know what library a certain objects belongs to and maybe also don't know how to search for it in "Find externals".
I think the ability to give proper feedback at patch loading time would help to address this issue.
while not giving "proper feedback", there has been a feature request in deken to support something like this for ages
i've implemented a little prototype of how it could look like: <https://github.com/pure-data/deken/issues/84#issuecomment-786533931
Thanks for the pointer. This would address my request. Further down, I found this:
https://github.com/pure-data/deken/issues/122
From what I understand, this would somewhat diminish the need for helping users identify missing externals when the _specified_ stuff is installed automatically.
Roman
On 2/26/21 1:41 PM, Roman Haefeli wrote:
Thanks for the pointer. This would address my request. Further down, I found this:
https://github.com/pure-data/deken/issues/122
From what I understand, this would somewhat diminish the need for helping users identify missing externals when the _specified_ stuff is installed automatically.
yes, but:
- the ticket is 5 years old. it's not likely (though possible) that it
will be tackled anytime soon.
- it's still very unclear how the actual user-interface would look like
(a requirements.txt file is all nice and dandy if you are working on the cmdline; less so if you never heard of such a thing and just got this freaky Pd patch from somebody)¹.
- and the biggest issue
as of now, deken is stateless. this is cool, as it makes everything simple to implement. however, it also means that deken doesn't know anything about which libraries are already installed, and which versions thereof. when you click on a search-result, it will just blindly (re-)install the selected library (and immediately forget about it again). i think this can become somewhat dangerous when doing in a fully automated way. esp. the "uninstall before re-install" option (which is enabled by default).
fmdsar IOhannes
¹ what i do imagine is something like: using the [declare] object as the dependency specification. right-clicking on a [declare] and selecting "Open" would open up deken with all the libraries specified in [declare] filled in the search form. this doesn't deal with versioned dependencies though.
This would be a nice feature to have within the deken plugin: to search among already installed externals
however, it also means that deken doesn't know anything about which libraries are already installed, and which versions thereof.
Currently, you can browse from pd's browser, but it involves going back and forth between deken and the pd browser.
-
Alexandre Torres Porres -
Fede Camara Halac -
IOhannes m zmoelnig -
IOhannes m zmölnig
-
Roman Haefeli