[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-13 12:42:37
[Download RAW message or body]

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

On Tuesday 13 November 2001 04:25 am, Cornelius Schumacher wrote about Re: 
[RFC] Unified Application Scripting Interface:
> What applications do you have in mind for your scripting interface? It
> would probably help to get a better understanding, if you could provide
> some use cases.

Example for KDE PIM:
	A secretary has access to 50 staff KOrganizer calenders and every morning 
she needs to get an idea of who is doing what.  For her to open 50 calenders 
would take all morning.  So a staff developer could write a simple shell 
script that would tell KOrganizer via dcop to iterate through a list of 
calenders and open them up.  Apply a filter to only show a certain event and 
then save the calender to an HTML file in a certain directory.  Now this 
process assumes that KOrganizer has the needed dcop interfaces.  

The idea here is that as far as the secretary knows she is using KOrganizer.  
We are allowing end users and developers to expand on the features of current 
applications via automation.  

The next stage involves using a shared parent object.  This way the script 
using python/ruby or perl can access the parent objects public member 
functions.  This requires about as much preparation as setting up dcop 
interfaces in an application so it is really up to the developer.  The 
advantage of this shared parent object or "object twin" is that you can pass 
large objects back and forth without the overhead it causes to dcop.  You can 
also allow more flexibility in the nature of the script plug in.

I hope this clears up some of your questions.  I designed most of my examples 
around Kate, and KDevelop because this was the source I was most familiar 
with.

If you have any questions please let me know.
- -ian reinhart geiser
- -- 
:-- Ian Reinhart Geiser --:
GPG Key: D6A6 7E16 13A9 B5A7 9E18 D1A7 3F2E B64D 19BC 76F8
===========================================================
Leveraging always beats prototyping.
===========================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE78RU+Py62TRm8dvgRApLUAKCgWU3gpVGqzHpCmiNjsJ5XOUCp4QCg5QaX
TDhW8KSO8mRExMGDXc040nk=
=l7Hf
-----END PGP SIGNATURE-----

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