DomainKey-Signature: a=rsa-sha1; c=nofws; d=louai.org; h=mime-version
	:in-reply-to:references:from:date:message-id:subject:to
	:content-type:content-transfer-encoding; q=dns; s=louai.org; b=X
	R4uaofDZ5jmAVr7gT+z5JBlnlYskQrMLD8ICLh8FpE7+dZKMtT0R8igg67kFUi4S
	yPJHqQ09ohcjjMtCiM1Rdw3hpVgPLhC2z0RZ+zdpvNr+o+3GYpdG55wHXQIbEIe2
	YFwBgAcCP6CcXETn+PBfUTzxUe64aY9z/0Fh5t8d1Q=
MIME-Version: 1.0
In-Reply-To: <list-5121628@media-motion.tv>
References: <list-5121628@media-motion.tv>
From: Louai Abu-Osba <me@louai.org>
Date: Mon, 22 Jul 2013 20:41:14 -0400
Message-ID: <CABan1zPfpMvsdKSGF+X7HyNEcJqmijuZ5imfpMidp9tt2rx1oA@mail.gmail.com>
Subject: Re: [AE] How the future of Adobe Scripting should look like
To: After Effects Mail List <AE-List@media-motion.tv>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Check out Jeff's most excellent:
http://www.redefinery.com/ae/view.php?item=3Drd_GimmePropPath

Not exactly script generation, but very helpful.

-louai

On Wed, Jun 26, 2013 at 2:09 PM, Byron Nash <byronnash@gmail.com> wrote:
> Great ideas Sebastien and Michael. I have put in feature requests for a
> script logger or listener before. That would be incredibly helpful in
> creating scripts and cut down on the time looking for that tricky object
> model syntax for a certain property you are after.
>
> I'd also like to see them support Python since that seems like it's becom=
ing
> the language of choice in DCC apps(Nuke, Maya, Softimage, etc...)
>
>
>
>
> On Wed, Jun 26, 2013 at 11:05 AM, Michael Powers <MPowers@cramer.com> wro=
te:
>>
>> Excellent. Thnx.
>>
>>
>>
>> For light duty scripters, like myself, it would also be helpful to have =
a
>> =93listener window=94 like the one found in 3dsMax, which shows Maxscrip=
t code
>> for most all UI actions. This makes generating new scripts a breeze in m=
ax.
>> For more involved scripting 3dsMax=92s far superior documentation is alw=
ays at
>> hand.
>>
>>
>>
>> From: After Effects Mail List [mailto:AE-List@media-motion.tv] On Behalf
>> Of S=E9bastien
>> Sent: Tuesday, June 25, 2013 1:08 PM
>> To: After Effects Mail List
>> Subject: [AE] How the future of Adobe Scripting should look like
>>
>>
>>
>> Hi guys,
>>
>> I was thinking of how Adobe should push forward our scripting abilities
>> and wrote a long post about it here: http://mytho.mn/future-adobe-script=
ing/
>>
>> I think it's somehow a big topic, now that we are on the way on unified
>> workflows between all the apps.
>>
>> As an AE scripter, my views are probably biased, but let's discuss about
>> it here to maybe build a better future ;)
>>
>> If you don't like links, here is a copy/paste of my post:
>>
>> We need scripting to change
>>
>> Today, each Adobe application have it=92s own scripting language, and it=
=92s
>> own set of UI API, and this is a big obstacle for us, to come with new a=
nd
>> exciting scripts and extentions for our beloved applications.
>>
>> With the Creative Cloud, Adobe is touting the synergy between all it=92s
>> flagship apps, the connected and seamless workflows from After Effects t=
o
>> Premiere, from Story to Audition, and yet, we can=92t design scripts tha=
t can
>> take advantage of that. In the center of this seemless ideology there is
>> metadata, but even for that, we don=92t have the handy tools.
>>
>> The all we can eat model
>>
>> In order to help us build impressive tools to make your applications
>> sexier, we desperatly need some improvements, and now that we=92re all u=
nder
>> the Creative Cloud shiny name, it=92s time to shape that future all toge=
ther.
>> And since you want us to access all your application to discover new
>> possibilities, it=92s time for me (us ?) to ask for the same favor in re=
turns.
>>
>> This is how I imagine the future of scripting, at an high level, and if
>> needed can provide specific exemples, and even in depth explanations on =
some
>> points. You know how to reach me ;)
>>
>> Gentleman, start your (scripting) engines
>>
>> First of all, we need a common scripting language for all the
>> applications, and a consistent set of API for all of them. Of course, th=
is
>> won=92t be done in a day, each app having it=92s own history before and =
after
>> their Adobe life, but why can=92t we have an abstraction layer that woul=
d
>> convert all our unified api calls into specific application language ?
>> Adding layers of interpretation is just a short term solution to a long =
term
>> problem. I hope that in a couple of years from now, UI accross all Adobe
>> apps will share the same language, and that we=92ll be able to run nativ=
ely
>> our scripts within all the apps.
>>
>> Un pour tous, tous pour un
>>
>> Then, we need to be able to call the API of every apps, from within any
>> app. Best exemple is: if I want to create a Premiere Pro Project from a =
set
>> of After Effects comps within After Effects, via scripting, the only way=
 is
>> to write a Final Cut Pro XML document and then let the user import it by
>> hand inside Premiere. That=92s inconveniant to say the least. And if I w=
ant to
>> create a Premiere Pro project with dynamic Links to a set of After Effec=
ts
>> comps, I simply can=92t, unless I=92m able to decypher the *.pproj filef=
ormat,
>> and believe me I tried.
>>
>> I can go on of course. I cannot change some PSD file specs within After
>> Effects, and we should be able to do that. The list could be very long, =
and
>> in fact, I even have a case study for that to share with you Adobe. I sh=
ould
>> be able to do these simples operation no matter what my host application=
 is.
>> And these exemples are just confined within the video application space.
>> Imagine what the community could achieve mixing the Edge tools, Flash or
>> After Effects=85
>>
>> So may it be via launching headless background apps, or a central
>> scripting runtime, it=92s your design choice, but please, let us do that=
.
>>
>> Files of the Conchord
>>
>> Within the same idea, we should be able to create every Adobe document
>> files
>> from any app. Creating Audition, Premiere, After Effects, Photoshop file=
s
>> from any of these apps will allow us to move interconnectivity forward i=
n
>> ways that will blow your mind. Let us add an icing of dynamic link from
>> within our scripts too. I can share a lot of ideas with you guys on this
>> one.
>>
>> Metadata is at the heart of an unified workflow. Adding XMP metadata int=
o
>> any Adobe supported file format should be as simple as a document.xmpAdd=
();
>> Your applications are supporting almost all media fileformat natively.
>> Enpower us with that so we can have fun with metadata writing and sharin=
g.
>>
>> The Dark Knight Rises
>>
>> With aescripts.com, the awarness around scripting have raised
>> significantly, the number of new tools for your customers is growing on =
a
>> daily basis, and people are hungry for more.
>>
>> So let us help you build tomorrow workflows. Extend and enhance scriptin=
g
>> so that we can create groundbreaking experiences for Adobe Creative Clou=
d
>> users, and push forward the worflows of tomorrow.
>>
>> Cheers,
>>
>>
>>
>> Seb
>>
>>
>> --
>> S=E9bastien
>>
>> mytho.mn
>
>