Q: why is the path not "flucoma"?

[umlaeute]

stupid question, but: everybody knows FluCoMa as "flucoma".

so why is the directory for the distributed binaries FluidCorpusManipulation?

I would have expected it to be flucoma (all lower-case, for cross-platform compatibility), so people could just do [declare -path flucoma] in their patches and happily patch away...

[tremblap]

this is a good question. the answer is partly aesthetic (flu coma is a condition we wish to no one). as for declaring, it is rarely that simple because it is a library so you need to get your head around all this, so instead we have this amazing PR that should get us on deken very soon!

[umlaeute]

well yes. thanks for your insight.

my point was mainly that if you are advertising the product as "flucoma" (which you apparently do, e.g. the homepage is named https://www.flucoma.org/, the GitHub project is https://github.com/flucoma, the repository is named https://github.com/flucoma/flucoma-pd), then you probably should use the name consistently.

or put otherwise: if you think that the associations invoked by the colloquial/short term are undesired, then you probably should start with the "official" addresses (homepage, ...) rather than the end user.

but that's just my 2¢ (and I guess there are other considerations which I'm blissfully unaware of, like consistency with Max/MSP, SC3, the CLI,...)

[tremblap]

we'll put flucoma in the text that deken is searching for, but changing the name now is going to break the internet.

for the record, when I got the funding, it was such an accident that I didn't think too much how much that name would stick. I tried to change the acronym with the funder, only to be told that I can change everything except the amount of money and the acronym 😆

anyway, we're stuck with it, both acronym and package name. I think I remember deken can have tags / text (with the object list IIRC) to make them searchable, right? fluid* must be searched for, for instance, no?

[ben-wes]

@umlaeute based on https://github.com/pure-data/deken/blob/main/developer/README.md, it looks to me like there's no way to add tags or strings to improve a library's findability except for the object list, right?

and since there's no [flucoma] object, we would need to create a custom object list that includes such an object anyway (seems a bit dirty, but maybe acceptable? - although it creates the risk of list and actual objects getting out of sync) via

deken package --objects more_than_actual_objects.txt FluidCorpusManipulation

?

[umlaeute]

i guess the simplest solution would be to include a flucoma-help.pd patch in the (packaged) distribution.

this way deken package will automatically create an entry for the [flucoma] "object" (even if there is no such actual object).

you would get away with just touch FluidCorpusManipulation/flucoma-help.pd (creating an empty file) before packaging, but that might be a bit unexpected for people who are trying to open that file (as nothing will happen).
so ideally, this help-patch would include some meaningful information for the casual user.

this will allow the people to find the library if they are searching for objects or both (but not if they limit the search to libraries only)

EDIT you could also upload a dummy "flucoma" library once (say: flucoma[v0.0].dek) that is empty except for a README.deken.pd telling people that they downloaded the wrong library and that they should get the FluidCorpusManipulation instead. (this will ensure that they will also find something if they search for library=flucoma)

[tremblap]

these are all great ideas. Proposed workflow: 1. we merge the PR (I'm unsure what is missing, I think a flag for nightlies)
2. when it appears on deken all good and jolly, I duplicate the overview patch with flucoma in the name.
3. when that is working, I also like the idea of a 'pointer' entry with a readme. we can send people to the work and also the hardly discovered overview file in the package...

[ben-wes]

unsure what is missing

flucoma/actions#8 and a v6 tag on that side, then #118

duplicate the overview patch

README.deken.pd is meant as an introduction patch (which also links to the overview patch). so it might be the simplest option to copy this to flucoma-help.pd for the deken build?

[ben-wes]

copy this to flucoma-help.pd for the deken build

done here in a separate actions PR now:

• Add flucoma-help.pd so deken indexes a [flucoma] object for findability actions#10