[lua] and [pdlua] integration with ELSE

[porres]

• [ ] ELSE ships with a modified version of [pdlua] without the [pdlua] and [pdluax] objects, can you consider adopting the same structure and not say you're shipping the original [pdlua]?
• [ ] upgrade to current latest pdlua stuff both in plugdata and ELSE of course
• [ ] I'm hoping for the new [lua] object with inline scripting as the ultimate [lua] object, in which the 'pdlua' documentation would be present. Right now [lua] stopped working altogether, see https://github.com/porres/pd-else/issues/2180

[timothyschoen]

[pdlua], [pdluax] and [lua] can live side-by-side. No need to choose :)

Since I contribute a lot to the pdlua repo, it's convenient for me to keep using the pdlua submodules instead of the version shipped with ELSE. This makes it easier for me to contribute, and easier to sync up with work that Albert and Ben do upstream. But I will help you update the version shipped with ELSE to keep it all in sync.

Anyway, I hope pdlua gets merged into pure-data at some point, so we'll no longer have 2 pdlua implementations floating around

[porres]

[pdlua], [pdluax] and [lua] can live side-by-side. No need to choose :)

Does this mean [lua] will be part of ELSE/PlugData and not in [pdlua]?

Anyway, I hope pdlua gets merged into pure-data at some point, so we'll no longer have 2 pdlua implementations floating around

Me too, we just need to keep insisting on it, make a PR, etc...

[porres]

this is all taken care I guess, but a functional [lua] object is still missing... maybe a new issue just for that or edit this one?