1) Python4Capella:
What do you mean exaclty? “in batch”?
I really like P4C and I would like to work with it in the future, however my prerequesite would be to have my “properties”/new attributes" interactive with a regular capella user.
Here:
Here my properties are instantly accessible to the user.
Is what you are thinking about/suggesting with P4C something that needs the user to “leave” Capella View, and go into the Python Scripts/menus?
If there is anything that can be done and that does not involve having the user “leaving” Capella, then I am all for it!
2) Coding Java:
I am still learning about EMF, not sure i could attain this coding level yet (Check Capella or even Sirius sessions).
Question about your proposition: would such java code/method, as you imagine it, be attached to some add-on/viewpoint I created → and Then if “activated”, then whenever i create a PVMT attribute (or sirius property), the default value would be edited by my additional “activate” java code? (never used that yet).
Optional:
I don’t want to create something that requires the user to leave the capella view/diagrams, but here is a side question, out of curiosity let’s say, does P4C allow using UI libraries? Which would allow us to create our own “capella side views” based on Python UI libraries, theoretically? Thanks
Edit
Edit: If you really think about it, one solution would be to create my own capella class that would be inherited from some other capella Class. (Default values can be controlled, editable manually, accessible with M2DOC, i can add as many attributes as I need)