Looks really useful. I know that moving stuff around in the UI for the scripts I work on is always a pain in the a. Will your script import from a script you already have. I guess this would make it aqn “editor” rather than a “designer”.
Cool idea. Maybe you could allow more extensive control strings though? For instance put control codes in curly brackets before/after the button text and have them of the form “key”:value? Then you would just need to chop out the bit from { to } and eval it as a dict
I’ve done things like this in the past, but I should have done some research before posting :rolleyes:
IIRC I figured out a way to check code before eval to prevent executing arbitrary code accidentally. I can’t remember where I put it though…
anyway something with keywork args would be cool!
I wish Python scripts had an edit mode. Just hit tab and then objects could be dragged and resized - hit n-key and you get properties of the object like min and max values. I did an interface like this once in Flash. The trouble is how do you save the changes because you’d have to write to the script itself while it was running. But what I had thought of was how about using a separate interface file like the Mac uses with .nib XML files. It means you get reusable interfaces for one thing and you don’t have to clutter your source code with interface code.