Post a reply

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

affriedl

Re: Script engine integration - what for?

I consider both to be good ideas - but then I'm not the one doing the work either :-) The inclusion of a scripting environment hosted by the application would allow people to program the appliction versus programming hosting the application themselves.

I believe that there are many more users who would prefer to script the application you already have rather than trying to re-create it for themselves.

My situation is an excellent case to consider: If I could script the WinSCP application to copy, move or delete (or not to) based upon events that occur external to the usual considerations of WinSCP then my need for a component goes away completely.

I have embedded interpreters in C/C++ projects in the past, including SpiderMonkey, Tcl, and Python. I would be willing to attempt this and send you my result as a proof of concept - however I use Visual Studio 2005 and have no clue if the Borland Project can be imported or not.
martin

Re: Script engine integration - what for?

If I decide to do something like that I would prefer some kind of reusable component (COM, .NET) rather then embeding scripting engine to WinSCP. I believe that it is more general approach.
affriedl

Script engine integration - what for?

I am glad you asked. I would like to be able to execute a command line batch file against a profile something like:

winscp3.exe /console /javascript=reconcile.jscp MyProfile

Or perhaps I want to be able to script a task I do on a faily regular basis, or perform some operation on a file that was just synchronized locally - like copy it somewhere with a different name.

If the applications' object model is exposed to a good object oriented script interpreter like JavaScript, Python, or ? then new features can be implemented in script by anyone. The community of users are then able to write (and share with everyone else) the new functionality they need and want. This usually creates a fury of development by your end-users and makes an application even more popular.

My preference would be to implement JavaScript (Mozilla SpiderMonkey) since it is such a well known language - Python would be my second preference but only because it is less well known to me.

The creation of a really good application model is key to success in embedding an interpreter - and the task as a whole is non-trivial to say the least - serious undertaking.
martin

Re: Scripting Engine Integration

What for? :-)
affriedl

Scripting Engine Integration

I would like to see an embedded interpreter: Python, SpiderMonkey, Tcl - anything would work.