[JDEV] Client scriping language

[Scott Robinson]

Hmm. I'm not so sure I don't want to give the ability to access an expanded
API. As you said, a "full-fledged object-oriented generalized scripting
language" has a lot of complex stuff that _most_ scripters won't need.

However, I assume there will be a "Kruft for Workgroups/Corporations" and if
there isn't in implementation, someone else will write one. I can see the
advatange in database access immediately. SWIG links to LDAP, proprietary
internal servers and maybe even coding links to other applications (I know
I'll be changing my "status" every time I switch MP3s I'm listening to...)
could all be useful. Leaving links for all of this in a Jabber specific
language would place more work upon the coders than would be nessicary.

Scott, excuse the spelling errors. I'm still tired.

* arh14 at cornell.edu translated into ASCII [Sun, Aug 08, 1999 at 11:58:44AM -0400][<Pine.SOL.3.91.990808115444.1309B at travelers.mail.cornell.edu>]
> 
> Well, it depends on what you want to do.  Do you really need to offer 
> scripters a full-fledged object-oriented generalized scripting language?  
> There are necessarily going to be confines to the use of the scripting 
> language (nobody is going to be doing transaction modeling, or database 
> interaction, or some highly complex stuff).  Basically you are just going 
> to expose a small API, and you need to give scripters the ability to 
> access *only* this API.  If this API is very small, that could very well 
> mandate a very small scripting language with a few pre-defined hardcoded 
> keywords.  You really only need to give scripters just enough so that 
> they can do something with the exposed API.  I would think most of the 
> functionality of these full-fledged general scripting languages would be 
> lost on it.
> 
> Aaron
> 
> 
> On Fri, 6 Aug 1999, Scott Robinson wrote:
> 
> > Hmm. I sorta discounted creating a new scripting language because it a)
> > would be reinventing the wheel and b) it would only add to confusion. If we
> > use a already known language, it allows others to convert quicker.
> > 
> > Scott.
> > 
> > * Paul L. McNeely translated into ASCII [Sat, Aug 07, 1999 at 12:13:21AM -0=
> > 400][<001f01bee08b$324c74e0$e69ca8d0 at marshall.edu>]
> > > Why not derive a scripting language that is jabber specific? What I was e=
> > ven
> > > thinking actually since there has been a lot of talk about skins is actua=
> > lly
> > > have a script set the skin, up, button positions, lenght/width/etc. that =
> > way
> > > whatever skin you use may make the interface look totally different. You
> > > couldn't even have the script read constants to determine if the skin is
> > > compatible with the client (wouldn't want to try running a win32 skin on a
> > > unix console now would we?) I think it would however make X and 32 skins
> > > compatible, as long as both had the same dynamic interface and scripting
> > > engine.
> > > -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=
> > =3D-=3D-=3D-=3D-=3D-=3D-
> > > Paul L. McNeely (drderail at i.am) ICQ# 1305664
> > > Web Page: http://i.am/drderail
> > > Voicemail: 1-888-TELEBOT Extension: 37337245
> > > -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=
> > =3D-=3D-=3D-=3D-=3D-=3D-
> > >    West Virginia Christian Chat Mailing List
> > >      Sign up at onelist.com or E-mail me.
> > >      Marshall University Chat Mailing List
> > >            http://muchat.listbot.com
> > > -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=
> > =3D-=3D-=3D-=3D-=3D-=3D-
> > >=20
> > > ----- Original Message -----
> > > From: Scott Robinson <scott at tranzoa.com>
> > > To: <jdev at jabber.org>
> > > Sent: Friday, August 06, 1999 11:46 PM
> > > Subject: [JDEV] Client scriping language
> > >=20
> > >=20
> > >=20
> > >=20
> > > _______________________________________________
> > > jdev mailing list
> > > jdev at jabber.org
> > > http://mailman.jabber.org/listinfo/jdev
> > 
> 
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev