Emanuele Mazza

Hi @anpin thanks for the contribute offer, it will be really appreciated, there's still a lot to work to do with Mosaic, and any help can be useful. At the...

Mosaic is now available in flathub!!! thanks to [soma95](https://github.com/somas95) https://flathub.org/apps/details/org.d3cod3.Mosaic So for average linux users without technical background about compiling, code and terminal commands, this install method is highly recommended.

OK, let me tell you what i have right now with params and objects: 1 - simple inlets, no GUI related, just inlets for internal use, NO saving/restore to/from xml...

I'm trying to port some objects to test specific stuff, and i just find out the Order of inheritance and multiple inheritance problem with the ofxVPParameters code, generating duplicate symbols...

Yes, i agree, and it's perfectly clear! About the question about ParamAbstract classes, i think they don't need to be separated, one big class will do the job fine. Generally...

Yes, it's handy, you're right, it's better with it! About the non-unique name, i'll leave it too, for GUI labeling issues. Imagine a patch with 3 "constant" objects, having the...

This is what i'm imagining it, we will have (maybe) three map vars? map objects; map parameters; map links; So, when we create a PatchObject, we store a reference to...

Perfect, i think we are really close. About ```PinLink```, i think we can keep it abstract, letting the Pins/Params to take care of the type, but we'll see what's best...

Amazing! I'm really happy to see it working! About the first two issues, can we just limit the logical flow direction with the ```bIsConnected``` variable for inlets? ```c if(bIsConnected) inletParam.editable...

Ok, just pushed the last commit on refactor-params-and-gui branch