Program Testers

[Navion]

My thoughts :

1- About bitmap filters : no matter what your code and interface, you just can not remove the trial-and-error method entirely out of the equation.

2-About graphics in general : if you do lots of it, chances are, one job after the other, each job requires a number of repetitive and specific steps.

3- About users : a casual user will probably enjoy a drag-drop-move-insert-effect-gadgety type of interface, because its cool and fun to play with. A power user on the other hand has these things in mind : productivity, repeatabilty, etc.

I cater mostly to the power user. In order to meet the goals of point 1 and 2 above, I feel a script language is more productive than a graphic visual interface trying to record and execute those steps. Writing and managing a complex interface requires a lot of time and effort. A script language, much less so.

Here is an example of such a script in my B2 program. The script is self explanatory but in a nutshell, it does the following : load a bitmap, enlarges it, vectorizes it, apply a texture, saves a large bitmap of the result. It then scales it down and make a comparison bitmap of the original and the scaled down version of the result. Then applies an invert filter and once again a comparison bitmap.

The script can be saved, modified, etc... etc.... It's a one-click thing to re-do the 19 steps of this job and results are automatically saved. That's my approach on graphics.

Here as screen shot of the working environment and the final comparison2 bitmap (saved as jpg)





As expected, the forum software does its usual job of scaling down my screen shot. Here's another pic that should show the script window better.