On Mon 2002-09-09 (21:42), [EMAIL PROTECTED] wrote:
> > I don't want a JS engine - but is it that hard to create a filter list
> > that does identify anything that does look like a file?
> >
> > The main JS commands should be easy to understand - but maybe soem kind
> > or filter file with regexp where to find the next file could be done
> > easily (while it's more hard to create this filter read mechanism first)
> >
> > > > javascript:winopen("somepage.html", <size and location>)
> > javascript:winopen("\([^"]*\).*) -> \1
> >
> > (PS: on the other hand it's pretty simple to run a grep and detect those
> > files manually)
>
> Really? have you try this?
> javascript:window.open("i" + "nde" + "x.h" + "tml")
>
> "winopen()" is not even a "JS command" it is a user defined function.
> What worked for you in a specific case does not work in the general cases.
agreed - the more complicated you want to make links by JS, the more
you'll find the need for a real JS engine.
> If you want this kind of support, you need a JS engine.
... but in general, JS is mainly used to open a window of its own with a
given, full html file name. A basic filter on "*.htm*" could add some
extra hits.
Kind regards
Martin
