[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: [RFC] Unified Application Scripting Interface
From:       ian reinhart geiser <geiseri () yahoo ! com>
Date:       2001-11-12 22:41:45
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 12 November 2001 05:29 pm, Neil Stevens wrote:
> I still don't understand what these scripts are supposed to be doing.  How
> are the scripts to be given access to the various parts of the
> application? DCOP?  If so, then what's the point of having a script loader
> in every single application, as opposed to a central scripting facility?
>
Read the pdf, it is very short and a quick read.
The idea is that some out of process behavior is not appropriate for 
automation.  The idea behind this is to provide a common interface for script 
engines to extend the application.  If you read the linked document you will 
see that the API is made to provide access to the parent object in the 
application so that you can use something like python or ruby to embed and 
extend the current application or just script it.

This is to bridge the gray area between plugins and dcop scripting again, 
this is spelled out in the pdf file, if you read it.

> Imagine this:  You have a library of scripts, each with a name, and a set
> of DCOP interface name(s) they use.  The user could select a script, and
> then select from a list of running applications that provide the required
> DCOP interface(s).

I think you are complicating the issue here, the idea is that the 
application has control over itself.  DCOP already allows applications to be 
controlled from the outside.  Read the paper, the idea is that there is a 
consistent, language independent way to make light weight extensions to 
applications.  These extensions can be everything from automation to full 
blown plugins written in C++.  

If you think along the lines of how ScriptFoo in GIMP works or how they 
python extensions work in XCircut, you will see how this becomes very useful.

Cheers
- -ian reinhart geiser
- -- 
:-- Ian Reinhart Geiser --:
GPG Key: D6A6 7E16 13A9 B5A7 9E18 D1A7 3F2E B64D 19BC 76F8
===========================================================
Programming is an unnatural act.
===========================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE78FApPy62TRm8dvgRAsjhAJkBZnrhukaYvVC1De2xBLfbFQkpfACdHmP1
wODlaVxbbQUvykUKXNdfTE0=
=z0hh
-----END PGP SIGNATURE-----

[prev in list] [next in list] [prev in thread] [next in thread]