Am 2008-03-15 um 22:13 schrieb has:
>> << 1 >>
>> Why does this work:
>> document = InDesign.make(new=k.document)
>> document.save(to=ComposedFile(path))
>>
>> but not this:
>> document = InDesign.make(new=k.document).save(to=ComposedFile(path))
>
> Seems to work on CS3. What are you
Am 2008-03-15 um 21:37 schrieb has:
> Henning Hraban Ramm wrote:
>> I struggled a lot with paths containing non-ASCII characters.
> Hmmm. Is this with the 0.18.1 release? Do you get the same problem
> with the current appscript trunk?
Sorry - since yesterday it works (with 0.18.1).
Some problems
a week ago I was having some problems setting up my PATH variables, though
now I seem to have the environment under control. I'd like to specify the
location for all installed libraries - python.org mentions the use of
.pydistutils.cfg. I placed this in ~/.pydistutils.cfg:
install-base=$HOME/Co
Henning Hraban Ramm wrote:
> Perhaps more FAQs:
>
> << 1 >>
> Why does this work:
> document = InDesign.make(new=k.document)
> document.save(to=ComposedFile(path))
>
> but not this:
> document = InDesign.make(new=k.document).save(to=ComposedFile(path))
Seems to work on CS3. What
Henning Hraban Ramm wrote:
> I struggled a lot with paths containing non-ASCII characters.
Hmmm. Is this with the 0.18.1 release? Do you get the same problem
with the current appscript trunk?
Ta,
has
--
Control AppleScriptable applications from Python, Ruby and ObjC:
http://appscript.sourcef
Richard Brosnahan wrote:
>> 1. suggestions for an appscript FAQ (has)
>
> I would love to see notes about using appscript with Xcode. In
> particular,
> writing full blow applications using appscript instead of scripting
> bridge.
Could you clarify? Using appscript (or SB) in Xcode is no d
