I'm just picking on on ScriptUI and was wondering what the general consensus on resource string vs. code based is with members here; does anyone have a preference? Pros and cons? Personal experiences?
Right off the bat, I'm noticing resource string seems to be way less documented whereas code base seems to be heavily. Also, debugging seems to be more of a headache as well with resource string... I do like the look and feel of my code when done with RS, however, my problem at the moment brings me closer and closer to scrapping it's use and sticking to code base altogether.
Any thoughts?
Izz
ScriptUI: Resource String vs Code Based
-
larsen67
ScriptUI: Resource String vs Code Based
I avoid using 'resource string' for the debugging reasons… Im not a natural coder thou… A designer that muddles thru…
-
Mike Hale
ScriptUI: Resource String vs Code Based
For what it is worth here are my thoughts.
Resource strings do seem to have a disadvantage when debugging. To me they are also harder to read and understand the dialog structure. I also find resource strings harder to 'build as you go'. So I use normal properties and methods type coding when creating dialogs.
The only advantage I see in them is you can use CSUIB to create a dialog without learning much about ScriptUI. But in the long run I think it is better to learn how to code the dialog rather than using an old, out of date app like CSUIB.
I dislike working with resource strings so much I have thought about creating a script that converts resource strings from other scripts I need to modify into normal code.
However the scripts that ship with Photoshop from Adobe seem to be split between the two ways of creating a dialog depending on the script's author so I am not sure there is one clear winning or best way. I guess it depends on which way makes the most sense to you.
Resource strings do seem to have a disadvantage when debugging. To me they are also harder to read and understand the dialog structure. I also find resource strings harder to 'build as you go'. So I use normal properties and methods type coding when creating dialogs.
The only advantage I see in them is you can use CSUIB to create a dialog without learning much about ScriptUI. But in the long run I think it is better to learn how to code the dialog rather than using an old, out of date app like CSUIB.
I dislike working with resource strings so much I have thought about creating a script that converts resource strings from other scripts I need to modify into normal code.
However the scripts that ship with Photoshop from Adobe seem to be split between the two ways of creating a dialog depending on the script's author so I am not sure there is one clear winning or best way. I guess it depends on which way makes the most sense to you.