No `Tuple` datatype support in project

[xp1632]

Just as we illustrated in https://github.com/xp1632/VPE_IP/issues/90#issuecomment-2047079227

Last thing to check: Tuple Input problems in VP project

• While we assign tuple datatype to java type net.imglib2.Localizable and net.imglib2.Dimensions
• We did a further check of this tuple datatype in the project

---

tuple in VP project

• tuple datatype is defined in project using TextInput widget:

• 

• While tuple has a format of ( , ) or ( , , ) , not a regular TextInput widget could handle

• Widget to get tuple value is not yet implemented

• Currently we only use tuple datatype in this node of making Tuple

• No inline Tuple Input that we could use in the Op Node Panel

---

• Thus we need to further check the ops that uses tuple datatype as input

• Think about how to pass and get tuple value

• Plan A is to add if type check for input during code snippet generation, and read string (100,100) and use 100, 100 when meeting tuple

• Plan B is to also delete the ops that requires tuple input for now

[xp1632]

Plan A: if tuple datatype check and add processing code in code snippet generation

• The code snippet generation part could be working
• however, when it comes to the $format part in NodeSpecGen, how should we deal with it?

---

• We need to figure out how to deal with
  • FinalDimensions(x, y)
  • (x,y)
  • x,y
  • x
  • y
  • ${input1}
  • (${input1}, ${input2})

[xp1632]

---

As we stated here: https://github.com/xp1632/VPE_IP/issues/80#issuecomment-2102144008

Thoughts about incompatible tuple, list type in Chaldene

• I don't think it's a good idea to make specific modification in generation pipeline for the type tuple, list input that Chaldene as a visual programming language doesn't support for now
• This is not a part of enhancement for pipeline but rather a remedy for Chaldene
• So I think this is where we finalize the pipeline after adding the __init__.json to achieve package import