[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Scripts

In article <c065574058.fjgraute@xxxxxxxxx>,
   Fred Graute <fjgraute@xxxxxxxxx> wrote:
> > * BASIC: another usable language, but few scripts!

> Well, create some. :-)

No thanks! I haven't done any BASIC for years.

> > Anyway - the Perl Script directory is empty!

> Sorry, I don't do Perl.

Sorry I do! It's a language to make one feel sorry. I struggle!

> > * Python: there is a port by Chris Gransden, but a quick instal does
> > not enable these scripts to be used.

> It's been a while since I used Python so I don't know why Python 2.7
> doesn't work. The scripts were created for the Python 2.4 port.

> Ah, it seems the alias for Python 2.7 is not *Python but *Python27 so
> change that and the scripts might work.

Indeed. But also the content of !ScriptSED.Languages.python has to be
changed to point to python27. I presume any new language must be declared

> > * Strong: The "Apply script" window lists stronged as a Language yet
> > the directory lists no such subdirectory.

> Yes, you can use a file with StrongED commands as a script but it needs
> some glue code to work. I have a BASIC file with that glue code but I
> don't think it's been part of any StrongED release.

That could be interesting. 

> > However there is a "sed" directory = but Sed does not appear to be
> > available?

Having found the declarations in !ScriptSED.Languages there is no sed and
there is a stronged. so the !ScriptSED.Scripts does not agree with

This caused me confusion as it looked as if sed was being misinterpreted as

> sed (short for Stream EDitor) is text processing utility for Unix/linux.
> It's similar to, but not as powerful as, awk. Also on Duncan's site.

> > I think the supplied Scripts need a tidy to ones which are relatively 
> > easily made usable? And if they don't work - why include them?

> The supplied scripts were mostly intended to show how the mechanism
> worked with the intention that users would use them as a template for
> their own scripts.

Fairynough! Which is why I am trying to grok it to better write up the
instruction page...

> I'd be happy to make changes but I have to admit that this is way at the
> bottom of my list of priorities...  Now if someone were to step in...

It looks a fairly simple tidy - if you understand what you are doing
(which is why I started this thread) but then you, Fred, would have to
integrate the tidying which might be more work than actually doing it?

The structure of !StrongED is very complicated: I'm sure there are good
reasons and once you understand, probably straight forward.

Richard Torrens.
http://StrongED.Torrens.org for StrongEDinstructions (in preparation) and mailing list archives