FROM : John C. Daub
DATE : Mon May 19 00:34:29 2008
on 5/18/08 6:56 AM, Georg Seifert at georg.<email_removed> wrote:
> I will specify my needs:
>
> - Most of my users most likely know python better than AppleScript.
> They will most likely use it to access and modify the model.
> - The scripts need to do quite processor intensive operation. e.g. My
> model contains a three structure with +20000 leafs.
> - the ability to install custom modules is not to important as I
> provide a plugin interface for bigger projects.
>
> I think this speaks for the embedding solution.
It seems like it, yes. I mean, if you use Scripting Bridge, you still have
to somewhat understand the nature of AppleScript, then Scripting Bridge. If
you're trying to minimize the learning curve for your users, a more
Python-centric solution may be better.
> But it could also be helpful to access other apps from within the
> script. This would be easier with applescript, isnšt it?
Maybe, maybe not. Again, I think it would depend upon just what other apps
might be likely to be chained into the mix here.
I personally feel that AppleScript is a good architecture to expose
scriptability in one's app, given it's place within the Mac OS X world. But
to choose to use AppleScript as the language to drive your scripts well,
that's up to the scripter.
> And does anyone has experience with performance?
I would gather this is tough to quantify, as it'll depend a lot upon
implementation both of how you hook up your scripting and then the scripts
themselves. It'll be something you'll just have to determine in your own
app.
--
John C. Daub }:-)>=
<mailto:<email_removed>> <http://www.hsoi.com/>
"...as the war machine keeps turning, death and hatred to mankind." - Black
Sabbath
DATE : Mon May 19 00:34:29 2008
on 5/18/08 6:56 AM, Georg Seifert at georg.<email_removed> wrote:
> I will specify my needs:
>
> - Most of my users most likely know python better than AppleScript.
> They will most likely use it to access and modify the model.
> - The scripts need to do quite processor intensive operation. e.g. My
> model contains a three structure with +20000 leafs.
> - the ability to install custom modules is not to important as I
> provide a plugin interface for bigger projects.
>
> I think this speaks for the embedding solution.
It seems like it, yes. I mean, if you use Scripting Bridge, you still have
to somewhat understand the nature of AppleScript, then Scripting Bridge. If
you're trying to minimize the learning curve for your users, a more
Python-centric solution may be better.
> But it could also be helpful to access other apps from within the
> script. This would be easier with applescript, isnšt it?
Maybe, maybe not. Again, I think it would depend upon just what other apps
might be likely to be chained into the mix here.
I personally feel that AppleScript is a good architecture to expose
scriptability in one's app, given it's place within the Mac OS X world. But
to choose to use AppleScript as the language to drive your scripts well,
that's up to the scripter.
> And does anyone has experience with performance?
I would gather this is tough to quantify, as it'll depend a lot upon
implementation both of how you hook up your scripting and then the scripts
themselves. It'll be something you'll just have to determine in your own
app.
--
John C. Daub }:-)>=
<mailto:<email_removed>> <http://www.hsoi.com/>
"...as the war machine keeps turning, death and hatred to mankind." - Black
Sabbath
| Related mails | Author | Date |
|---|---|---|
| Georg Seifert | May 17, 17:16 | |
| has | May 17, 23:12 | |
| John C. Daub | May 17, 23:47 | |
| has | May 18, 11:56 | |
| John C. Daub | May 18, 13:06 | |
| Georg Seifert | May 18, 13:56 | |
| has | May 18, 22:47 | |
| John C. Daub | May 19, 00:34 |






Cocoa mail archive

