Hi list,
I noticed that deken can search for individual objects. But, when I search for an object of my jmmmp library, I can't find them. What am I doing wrong?
I had a look at https://github.com/pure-data/deken/blob/master/developer/README.md#objectlis..., but when browsing the libraries where objects can be searched (Gem, maxlib, cyclone, ...) I didn't see any example of a objectlist file on how to build on. Since I'm on windows and there are no deken tools available, I upload my library through puredata.info - so, any object list would have to be in the package.
I guess the main question might be: my package already has a README.txt with a list of objects, but not exactly formatted as described in github. Is it enough to format the list on that file using the "object-name at the beginning, followed by a TAB (|\t|) and a short (single-line) description of the object" format, or do I need to add a jmmmp.txt file with said list?
If the latter, how exactly must be the content of the file, can some comments be there, or it must be the list only? Does anyone know of a concrete example, without me having to look through all libraries to find one?
Best,
Joao
Am 5. Jänner 2020 16:02:52 MEZ schrieb "João Pais" jmmmpais@gmail.com:
Since I'm on windows and there are no deken tools available,
what about the precompiled deken.exe available on github?
mfg.hft.fsl IOhannes
where is it? I downloaded the zip file, used the "find file" button, and searched the page, but deken.exe didn't come up.
Does that mean that a database entry can only be made using the deken command line?
Am So., 5. Jan. 2020 um 20:44 Uhr schrieb IOhannes m zmölnig < zmoelnig@iem.at>:
Am 5. Jänner 2020 16:02:52 MEZ schrieb "João Pais" jmmmpais@gmail.com:
Since I'm on windows and there are no deken tools available,
what about the precompiled
deken.exeavailable on github?mfg.hft.fsl IOhannes
On 1/5/20 11:28 PM, João Pais wrote:
where is it? I downloaded the zip file, used the "find file" button, and searched the page, but deken.exe didn't come up.
On https://github.com/pure-data/deken/tree/master/developer#windows is read:
If you don't want to install Python3, bash (MSYS),... on your Windows machine, you can also download self-contained binaries from our Continuous Integration setup: Windows 32bit Windows 64bit
These builds are snaphots of the latest development branch of deken. If they don't work for you, you might want to check the releases page for downloads that have been tested by humans.
the links in this paragraph take me to the exe files. the "releases" page on github also has windows binaries.
the windows binaries for the cmdline tool are not included in "deken" package available via deken, as the cmdline tools are targetted at developers (who want to upload their own packages) whereas the "Find externals..." button is targetted at users (who want to download other people's packages).
Does that mean that a database entry can only be made using the deken command line?
no. but it is the simplest way. i strongly suggest to use it.
having said that: you can also manually upload an objectlist-file, as described on the page you linked to.
i don't know why you think you can add the information into
README.txt, the documentation says that the file must have the same
name as the .dek-file with a .txt appended. so if your deken-package is
called "frobnozzel(Windows-i386-32)(Sources).dek", then the objectlist
file must be called "frobnozzel(Windows-i386-32)(Sources).dek.txt".
the file format is described as:
The objectlist file has one line per object, with the object-name at the beginning, followed by a TAB (\t) and a short (single-line) description of the object.
this format doesn't allow for any additional data (e.g. the one you would like to put into a README.txt).
the part that is missing from the docs is, that this file must be uploaded besides the .dek file. so the objectlist-file is is *not* part for the .dek file, but can be downloaded separately. (so there's also little use in downloading deken packages and searching their contents for the objectlist)
i hope this helps,
gamsdr IOhannes
On 07/01/2020 14.59, IOhannes m zmölnig wrote:
the part that is missing from the docs is, that this file must be uploaded besides the .dek file. so the objectlist-file is is *not* part for the .dek file, but can be downloaded separately. (so there's also little use in downloading deken packages and searching their contents for the objectlist)
With my latest upload experiences, I found the *.dek.txt and the *.dek.sha256 are uploaded automatically with the *.dek file. It even attempts to create a GPG signing of the package and presumable upload that too. This was the Linux-deken, so YMMV.
i hope this helps,
gamsdr IOhannes
Greetings,
Fred Jan
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
-
Fred Jan Kraan -
IOhannes m zmölnig -
João Pais