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.
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.