daioros wrote:
Let's make this straight.
Recording scripts isn't just enough because they do only basic stuff.
And all examples i've found in the Internet are all basic too.
Even looking at recorded scripts I don't have any knowledge of the variables used by the program or the image, like size of the image, layers, depth, colors, format, a particular pixel in a particular position...
I've searched in the Help and no clue either.
It's impossible to make advanced scripts if you don't have that stuff.
I don't care about learning Python, it's not a problem for me and it's completly an easy language.
But what I want to know is the name of that variables.
Is it so hard?
Is it too much to ask for?
You keep missing the point --
every product, whether it's a stereo or a camera or a car, or consumer software is "designed for a specific price point".
- First the manufacturer decides the selling price.
- Second, they ask, "What features do competing products in that price range have?"
- Third, they ask, "Which of those features does our product have to have if it's going to sell?
- Fourth, they ask, "How much money, time and other resources will we have to spend to create, add and maintain those mandatory features?"
- Fifth, they ask, "How much remaining money, time and other resources will we have available to add other features?"
- Sixth, they ask, "What new or improved features are our customers saying they want?"
- Seventh, they ask, "Which new or improved features are most requested?"
- Eighth, they ask, "How likely is it that our competitors will add such a feature?"
- Ninth, they ask, "For each of the most requested features, how much money, time and other resources would we have to spend to create, add and maintain such a feature?
- Tenth, for each possible new feature they ask, "If we add this, will it significantly increase sales, decrease sales ("ugly", "hard", "confusing", "unnecessary"), or have no effect on sales?"
Then they decide which features to add, based on resources and demand. And for software that retails in the $80 range, the vendor has to face the fact that
many customers will only buy every third or fourth upgrade.
Writing, testing and maintaining advanced scripting examples and documentation would be
incredibly resource intensive and would add
nothing that
most PSP users want. "Providing documentation"
sounds like "something they could do in their sleep". But the
fact is that people expect everything to be formatted "exactly correct". If
all the indenting isn't uniform and
all the fonts aren't correct it looks
extremely sloppy and amateurish.
"Command syntax uses bold Arial 10 pt. Example code uses Calibri italics. Descriptive text uses Times Roman. Optional parameters are indicated by ...", etc.
It's the same reason Corel hasn't added photomerge to PSP although it has been requested
many times by
many users -- it would cost a lot to add, it would have no effect on sales, and programs are available for free that can do that limited task.