|
 |
On 4/14/2011 14:22, Jaime Vives Piqueres wrote:
> My problem with the executable option was that my script needed
> editing in *all cases*, for every scene.
You *could* prompt every time you run the script? Or take a file name on the
command line to indicate what the parameters are? Or the name of an ini file
to read from? Depending on how many there are?
--
Darren New, San Diego CA, USA (PST)
"Coding without comments is like
driving without turn signals."
Post a reply to this message
|
|
|
|
> One thing that should be noted is that not all people accept all
> scripting languages equally well, and some may refuse to install
> interpreters for whatever language you choose. I, for instance,
> would hesitate to install a PHP interpreter on my machine, but would
> be ok with Perl, Python or Ruby (and, as you probably guess, have Tcl
> installed already); I must confess this is an only marginally
> rationalized preference, but I may not be alone with such a
> preference.
>
That was exactly my fear about distributing just my handy PHP
script... ;)
> That said, when it comes to writing platform-independent scripts
> with the intention to distribute them, I think the most commonly used
> language for such a purpose might be Perl.
Yes, it seems so, but I've already decided in favor of the last of
your options:
> In case you should decide to split up the script into a kind of
> config file and the actual code, Java would probably be the way to
> go.
Not for that reason, but I finally decided to write it in Java using
Netbeans. I can just distribute a single jar (plus the source code for
the curious), and seems easy enough as to have it finished by tomorrow.
--
Jaime Vives Piqueres
La Persistencia de la Ignorancia
http://www.ignorancia.org
Post a reply to this message
|
|
|
|
El 14/04/11 23:29, Darren New escribió:
> On 4/14/2011 14:22, Jaime Vives Piqueres wrote:
>> My problem with the executable option was that my script needed
>> editing in *all cases*, for every scene.
>
> You *could* prompt every time you run the script? Or take a file name
> on the command line to indicate what the parameters are? Or the name
> of an ini file to read from? Depending on how many there are?
>
Yes, of course all these were possible... I just wanted to avoid the
extra work of implementing any of them. So I was originally looking for
an interpreted language for which I could just distribute the editable
script. But by now I've already realized that I cannot be that lazy...
in the end, it's just a few text fields, some dropdowns and a button.
--
Jaime Vives Piqueres
La Persistencia de la Ignorancia
http://www.ignorancia.org
Post a reply to this message
|
|
