The idea of having heavily used functions in multiple locations is a good idea. If you use quickdrop it should not matter where a primitive is located.
If you say deleting something is useful for users, then explain how it is useful. Don't just say it. Explain how having the repeated functions is NOT useful for users.
Why don't certain functions belong in multiple palettes? For instance, you highlighted Cluster to Array and Array to Cluster. Shouldn't they belong in both with the Array and Cluster palettes? If not, then which of those two palettes does it belong in?
First case:Array to Cluster onces the array is converted to Cluster, in the array palette no function is useful for further process we have to go for Cluster palettle functions. Second case: Cluster to Array onces the Cluster is converted to Array, in the Cluster palette no function is useful for further processing of Array,we have to go for Array Palettle funtions.
what's my opinion is *most useful functions related to their functional palette catageory. Array to Cluster related to Array palette Cluster to Array releated to Cluster palette Colour box constant releated to Picture Fucntion palette. boll to (0,1) related to Bollean function palette.
I considier array to cluster and cluster to array complementary functions that belong on the same palette. If I'm thinking of an array/cluster conversion, and not one way vs. the other first, I might start looking on the array palette, or I might start looking on the cluster palette. I don't want to have to guess wrong and have to go find the other palette. What is the harm if they are both on both palettes? Absolutely nothing!
Please give a reason why you think having functions on multiple palettes is a bad thing. You still haven't said why.
When proposing a new idea on the exchange, the typical practice is to state a problem about how the current situation is bad, and propose a better idea and make a case of how the new idea improves upon the old. Your idea does neither.
