Article View: adobe.scripting.indesign
Article #8796Re: The top 4 things that bug me about InDesign scripting so far
From: nycynik
Date: Tue, 26 Sep 2006 16:00
Date: Tue, 26 Sep 2006 16:00
11 lines
1522 bytes
1522 bytes
you know what, i totally agree with you on all points. Thanks for putting this out there. #1 is huge with me, all the function names are the same, so i constantly have ot check what page i am on to know what im looking at. And i did make a pdf of just the one section that I was interested in, but then i still have only 1 index in my pdf, to search.. #2 eh, this may be a bit of `you say tomato, they say tomato.` imho #3 I wish they had user contributable examples. I'm not 100% sure how they would keep it organized, but I think many people are doing exactly the same thing, and this would help out a lot, but probably hurt some people who are charging money for scripts, so I dont know. #4 I woud like your idea, or at least a summary of the thread. Good Points!
Technical Details
Message-ID:
<3bc1c832.2@webcrossing.la2eafNXanI>Path:
arc1-ca.pugleaf.net!g2news2.google.com!news3.google.com!news4.google.com!border1.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!newspeer1.nwr.nac.net!newsfeed.freenet.de!news.albasani.net!news.isoc.lu!webcrossingReferences:
<3bc1c832.-1@webcrossing.la2eafNXanI>Show Full Headers
Complete Article Headers
X-Google-Thread: f939a,9c31209a8bed7967 X-Google-Attributes: gidf939a,public X-Google-Language: ENGLISH,ASCII-7-bit From: nycynik@adobeforums.com Path: arc1-ca.pugleaf.net!g2news2.google.com!news3.google.com!news4.google.com!border1.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!newspeer1.nwr.nac.net!newsfeed.freenet.de!news.albasani.net!news.isoc.lu!webcrossing Newsgroups: adobe.scripting.indesign Subject: Re: The top 4 things that bug me about InDesign scripting so far Message-ID: <3bc1c832.2@webcrossing.la2eafNXanI> Date: Tue, 26 Sep 2006 09:00:35 -0700 References: <3bc1c832.-1@webcrossing.la2eafNXanI> Lines: 18 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit