* [EMAIL PROTECTED] (Curt Olson) [2003.10.15 11:38]:
> Cameron Moore writes:
> > One way to fix this would be Javascript.
> 
> [sound of the front door slamming]
> 
> [very rapid foot steps are heard fading off into the distance ...]

[ zzzzzip - Cameron zips up his flame-retardent jacket ]

I said "One way..."  And BTW, I agree.  I only use JS when I have no
other choice.  To me the only other choice is having a separate
"graphical" page for each ftp mirror, which I don't particularly like
either.

So why not JS?  One can assume that anyone using the GRAPHICAL interface
will have a GRAPHICAL browser, so bye-bye lynx/links.  One can also
assume that only hardcore/anal users will have JS disabled, and they
will be more than skilled enough to ftp to the mirrors on their own
without the need to use the graphical interface.

I could work on a prototype if you will consider it, but if it's gonna
get shot down just due to the fact that it's JS, I won't bother.  It
can't be any worse than python.  ;-P

> I think I've been watching too many cartoons lately ... my excuse is
> that my 2.5 year old daughter now lists "SpongeBob SquarePants" as her
> favorite TV show.  Thankfully we somehow managed to completely skip
> the Barney/Teletubbies stage and went straight to something that's
> funny and entertaining. :-)

My 20-month old son likes "SpongeBobPants" too (yes, it all one word).

> > Here's my idea:
> > 
> > Create a <select> input on the graphical download page with the
> > different ftp mirrors -- default to master.  Add an event handler to the
> > <select> so that it updates a variable (ie. $MIRROR) when the user
> > changes it.  Update the links over the graphical interface to use an
> > onClick() event instead of an href element.  The onClick() simply
> > directs the user to ftp://$MIRROR/fgfs/Scenery-0.9.2/e000n00.tar.gz or
> > whatever is appropriate.

-- 
Cameron Moore
[ "Bombay is 250ms from New York in the new world order" - Alan Cox ]

_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel

Reply via email to