Dear Philip and the AppleScript list,
Thanks for the kind words. You are precisely correct about the need for
such resources and the relative lack of easy beginner-oriented or at
least beginner-task oriented materials was the biggest reason that I
abandoned no less than 3 attempts to learn AppleScript Studio in the
past. This time I am taking much more time to read through whatever
resources are available out there, including this list, MacScripter, the
Apple sample application source code, and some of the tutorials but
despite the wonderful example code found in various forum/list postings
out there, for beginners like me the "time-to-solution" for each problem
encountered along the way is regretfully prohibitive.
The new ASS weblog (Fool's Applescript Workshop) I set up at
foolsworkshop.com/applescript/ is just a kind of "pay back" for all the
helpful answers to questions I found along the way deep in nested online
discussions or downloaded/sample code.
However, I am not a skilled programmer, by any means, and my code is
often of the least-efficient-barely-functioning variety. Being therefore
under-qualified for the task, and harboring no great ambitions, I would
be very interested in having others skilled in ASS development
who are sympathetic to the many beginners out there like myself join as
contributors to the weblog (which we can rename once there are more
contributors to something a little less "foolish").
If there is anyone interested in joining as regular or occasional
contributors to this project, I propose that the solid majority of the
contents of its postings be roughly guided by the following guidelines:
1) To post relatively short but lucid explanations of how to solve
practical problems a developer might face in creating an AppleScript
Studio application, especially if one is a beginner and not that
familiar with XCode, Cocoa classes, or even the AppleScript language.
2) Whenever possible, these explanations should be accompanied by a
snippet of well-commented sample code, and if the posting author's
time allows, a sample XCode project which demonstrates the solution.
3) Whenever possible, links to forum/list postings, tutorials, Apple
documentation, etc. which provide the same/similar or completely
different solutions to similar problems should be provided so there are
other sources the beginner can turn to if they need more information.
4) Any original content created for postings be Creative Commons
licensed
so it may be shared and spread easily among interested parties.
If any of you are interested in joining as a regular or occasional
contributor to the AppleScript Studio weblog along the above lines, send
me an email at kmlawson at fas.harvard.edu and I can get you set up with
access to the blog's editing features so you can start posting at your
leisure. I'll be moving from Seoul to Taipei in the coming week, so I
might be a little slow in replies the next few days.
Respectfully,
K. M. Lawson
______
Hi Konrad
Just wanted to say how very impressed I am by your AppleScript Blog. I
have often thought it would be great if there were more such resources.
For whatever reason Apple don't seem to promote Studio strongly, and I
wonder how many people try it but then don't pursue it because it's hard
to find examples, tips etc. - many I suspect, and I think that's a
shame. Good on you for taking the trouble to add to the collective
resources!
Philip
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Studio mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/applescript-studio/email@hidden
This email sent to email@hidden
