First off, a big THANK YOU to all the developers who have taken the time to write the wonderful actions that many of us use on a daily basis.
I’d like to make several requests. When you develop an action in the future or update an existing one, is there anyway you can include a version number with the action? One that is visible in the Mac OS finder? This would make it much easier to determine which actions are current.
And second, demos are extremely helpful. I know it’s a lot of extra work, but seeing exactly what an action does and the benefits it provides would be very helpful to many of us FWP users.
Some of you are already doing both of what I’ve asked for and I for one truly appreciate the extra effort. Thanks again for all your efforts on our collective behalf.
It is fairly simple to see what an action does. Switch it off and publish again. Compare the output, and you have your answer.
Like a do-it-yourself-demo…
It is fairly simple to see what an action does. Switch it off and publish
again. Compare the output, and you have your answer.
Like a do-it-yourself-demo…
With many, yes. There are several I’ve struggled with, trying to work out
the context of their use. Sometimes a little example or documentation goes
a long way for some of us.
Absolutely. My advise came from the experience I was not satisfied with a manual or explanation. For me it worked better to compare output (HTML) to understand.
Writing manuals myself sometimes, I understand it can be quite boring for a developer to explain for others ‘how to’ when the work is done, and one is excited to start with the next challenge…
Absolutely right. I understand that it can take me hours to explain or
demonstrate something that took me under two minutes to do. Add that to the
distractions that keep us from investing more time into the community and
you see why some things are left incomplete.
On Friday, December 13, 2013, atelier email@hidden wrote:
Absolutely. My advise came from the experience I was not satisfied with a
manual or explanation. For me it worked better to compare output (HTML) to
understand.
Writing manuals myself sometimes, I understand it can be quite boring for
a developer to explain for others ‘how to’ when the work is done, and one
is excited to start with the next challenge…
With many, yes. There are several I’ve struggled with, trying to work out
the context of their use. Sometimes a little example or documentation goes
a long way for some of us.
Ernie Simpson
You all have some very valid points, but I think this comment sums it up for me.
