Curtis L. Olson said:
Jon Berndt wrote:
In addition to the status tag, I also support a author and version
tags. It would be great if people could go through and fill in these
fields as they can.
Is that for the FDM? JSBSim v2 config files will feature this header
(partially in
Jim Wilson wrote:
I'm done doing thumbs for now. Feel free to replace the ones I've posted with
improved versions, especially authors may want to.
Hi Jim,
Thanks for all your efforts (and thanks to everyone else who's generated
thumbnail images or filled in missing fields.)
Related(?)
On Monday 17 January 2005 18:49, Curtis L. Olson wrote:
For the upcoming release of FG, I'm working on a couple
scripts to create/manage a web page for individual downloads.
Here is where I'm at so far. There is plenty room for
improvement, but this will at least get us started:
On Tuesday 18 Jan 2005 22:31, Lee Elliott wrote:
I loved the entry for the ufo:)
LeeE
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
For the upcoming release of FG, I'm working on a couple scripts to
create/manage a web page for individual downloads. Here is where I'm at
so far. There is plenty room for improvement, but this will at least
get us started:
http://www.flightgear.org/Downloads/aircraft/
If aircraft
I don't want to sound like someone who likes to nitpik but ... :)
Is there any good reason to use PNGs for the thumbnails?
There will be 60 aircraft thumbnails and we are averaging about 32K per
thumbnail at the moment even with max PNG compression.
That equates to nearly 2MB just for
A fair point ... I'll take care of it ...
Curt.
Paul Surgeon wrote:
I don't want to sound like someone who likes to nitpik but ... :)
Is there any good reason to use PNGs for the thumbnails?
There will be 60 aircraft thumbnails and we are averaging about 32K per
thumbnail at the moment even
You can also lower the quality of PNG image as well as up the
compression level. Doing so can make PNG's smaller than JPEG's.
For example a top quality JPEG has a larger file size than a best quality PNG.
So I don't know what you use to create the PNG's but you should be
able to edit these
On Mon, 17 Jan 2005 12:49:49 -0600
Curtis L. Olson wrote:
For the upcoming release of FG, I'm working on a couple scripts to
create/manage a web page for individual downloads. Here is where I'm at
so far. There is plenty room for improvement, but this will at least
get us started:
On Tuesday, 18 January 2005 00:32, Arthur Wiebe wrote:
You can also lower the quality of PNG image as well as up the
compression level. Doing so can make PNG's smaller than JPEG's.
Now you've made me curious.
I was using GIMP2 and set the compression to level 9 (max)
How how does one lower the
Chris Metzler wrote:
Cool. The one thing I'd recommend is including info about development
status (at the very least, the one-word status that's used in the
--min-status command line switch). Without it, there will be users
d'l'ing a plane with great enthusiasm only to be disappointed to find
In addition to the status tag, I also support a author and version
tags. It would be great if people could go through and fill in these
fields as they can.
Is that for the FDM? JSBSim v2 config files will feature this header (partially
in working
with the DAVE-ML spec):
fileheader
Jon Berndt wrote:
In addition to the status tag, I also support a author and version
tags. It would be great if people could go through and fill in these
fields as they can.
Is that for the FDM? JSBSim v2 config files will feature this header
(partially in working
with the DAVE-ML spec):
Curtis L. Olson said:
Chris Metzler wrote:
Cool. The one thing I'd recommend is including info about development
status (at the very least, the one-word status that's used in the
--min-status command line switch). Without it, there will be users
d'l'ing a plane with great enthusiasm only
Chris Metzler wrote:
I think this is a good idea. Even if it's just at the alpha/beta/
finished level.
That part was already implemented but seems to have broken along the
lines. The idea was this:
fgfs --show-aircraft --min-status=production
Erik
___
Erik Hofman wrote:
Chris Metzler wrote:
I think this is a good idea. Even if it's just at the alpha/beta/
finished level.
That part was already implemented but seems to have broken along the
lines. The idea was this:
fgfs --show-aircraft --min-status=production
No wait, this is the only option
On Fri, 07 Jan 2005 11:02:32 +0100
Erik Hofman wrote:
No wait, this is the only option where the order is important. This does
work:
fgfs --min-status=production --show-aircraft
Right, but doesn't this presume that they already have the aircraft
installed? I just checked -- the
On Friday, 7 January 2005 11:09, Erik Hofman wrote:
That part was already implemented but seems to have broken along the
lines. The idea was this:
fgfs --show-aircraft --min-status=production
We were refering to the web page that Curt is putting up and not FG itself.
Paul
Chris Metzler wrote:
On Fri, 07 Jan 2005 11:02:32 +0100
Erik Hofman wrote:
No wait, this is the only option where the order is important. This does
work:
fgfs --min-status=production --show-aircraft
Right, but doesn't this presume that they already have the aircraft
installed? I just checked --
On Friday 07 January 2005 07:35, Chris Metzler wrote:
On Tue, 4 Jan 2005 19:48:27 +0200
Paul Surgeon wrote:
It would be really nice if the level of development was
listed as well as a brief description about the aircraft.
That would help people decide whether they really want to
On Fri, 7 Jan 2005 21:12:01 +
Lee Elliott wrote:
On Friday 07 January 2005 07:35, Chris Metzler wrote:
On Tue, 4 Jan 2005 19:48:27 +0200 Paul Surgeon wrote:
It would be really nice if the level of development was
listed as well as a brief description about the aircraft.
That would help
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Arnt Karlsen schrieb:
Zip files are everywhere, we aren't going to get sued for using them,
..no? ;-) Never heard of The SCO Group and Microsoft?
http://www.groklaw.net/article.php?story=20041228040645419 or
On Tue, 4 Jan 2005 19:48:27 +0200
Paul Surgeon wrote:
It would be really nice if the level of development was listed as well
as a brief description about the aircraft.
That would help people decide whether they really want to download the
aircraft or not.
For example :
Jim Wilson wrote:
gzip extracts pkzip files.
Maybe the Linux version, nut the one shipped with IRIX.
Erik
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Jim Wilson wrote:
Unzip is an archiver and runs on just about anything. Comes with several
linux distributions as well.
Yes, but not all. That's the point. Should we honor Windows users where
there are some version of windows that ship with an ZIP extractor or
honor the UNIX world that comes
Erik Hofman wrote:
-Original Message-
From: [EMAIL PROTECTED] [mailto:flightgear-devel-
[EMAIL PROTECTED] On Behalf Of
Sent: 05 January 2005 09:00
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Individual aircraft downloads
Jim Wilson wrote:
Unzip
On Wednesday 05 Jan 2005 09:22, Vivian Meazza wrote:
We should do both - that seems to be the solution adopted by most web sites
which offer downloads. Why should we be different? We should not expect
windows or UNIX users to download and install some additional software.
I could make a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dave Martin schrieb:
On Wednesday 05 Jan 2005 09:22, Vivian Meazza wrote:
We should do both - that seems to be the solution adopted by most web sites
which offer downloads. Why should we be different? We should not expect
windows or UNIX users
James Turner wrote:
For some reason, I have never seen code to do this with the .tar.gz
format, thought in principle it should work; the issue is that ZIPs
have a table of contents that can be read without extracting all the
files, whereas for a .tar.gz I think you'd have to uncompresss
On Wednesday 05 Jan 2005 10:44, Christian Mayer wrote:
Dave Martin schrieb:
I could make a really scathing comment about that using words like plib,
OpenAL and SimGear...
But those are for *developers* and not *users*.
I was more making the point that unless a Linux *user* uses one of
Erik Hofman said:
Jim Wilson wrote:
Unzip is an archiver and runs on just about anything. Comes with several
linux distributions as well.
Yes, but not all. That's the point. Should we honor Windows users where
there are some version of windows that ship with an ZIP extractor or
Dave Martin wrote:
Christian Mayer wrote:
Dave Martin schrieb:
I could make a really scathing comment about that using words like
plib,
OpenAL and SimGear...
But those are for *developers* and not *users*.
I was more making the point that unless a Linux *user* uses one of the
On Wed, 5 Jan 2005 18:03:38 -, Vivian wrote in message
[EMAIL PROTECTED]:
Our Windows users (and they are probably the majority) for the most
part expect everything to be done for them, and for it all to work
right out of the box. Otherwise, they will give up at the first
hurdle, and,
On Wed, 5 Jan 2005 12:30:04 -, Jim wrote in message
[EMAIL PROTECTED]:
Erik Hofman said:
Jim Wilson wrote:
Unzip is an archiver and runs on just about anything. Comes with
several linux distributions as well.
Yes, but not all. That's the point. Should we honor Windows
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Oliver C. schrieb:
|
| Could you change the file format from *.tgz to *.tar.gz?
|
| I ask because *.tgz is used by Slackware as a package format (it's a
tar.gz
| file with a install script in it) and this is leading to confusion
| when you have
On Tuesday 04 January 2005 11:37, Christian Mayer wrote:
Oliver C. schrieb:
| Could you change the file format from *.tgz to *.tar.gz?
|
| I ask because *.tgz is used by Slackware as a package format (it's a
tar.gz
| file with a install script in it) and this is leading to confusion
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Oliver C. schrieb:
| On Tuesday 04 January 2005 11:37, Christian Mayer wrote:
|
|Oliver C. schrieb:
|| Could you change the file format from *.tgz to *.tar.gz?
||
|| I ask because *.tgz is used by Slackware as a package format (it's a
|
|tar.gz
|
||
On Tuesday 04 Jan 2005 11:17, Oliver C. wrote:
On Tuesday 04 January 2005 11:37, Christian Mayer wrote:
Oliver C. schrieb:
| Could you change the file format from *.tgz to *.tar.gz?
|
| I ask because *.tgz is used by Slackware as a package format (it's a
tar.gz
| file with a
Christian Mayer wrote:
Linux can easily unzip those and Windows users have the unzipper already
comming with their OS (when it is WinXP...)
But only then - and who wants WinXP without being forced to !? ;-)
On the other hand PowerArchiver for Windows easily handles .tar.gz or
.tgz
Martin Spott wrote:
Christian Mayer wrote:
Linux can easily unzip those and Windows users have the unzipper already
comming with their OS (when it is WinXP...)
But only then - and who wants WinXP without being forced to !? ;-)
On the other hand PowerArchiver for Windows easily handles
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Spott schrieb:
Christian Mayer wrote:
Linux can easily unzip those and Windows users have the unzipper already
comming with their OS (when it is WinXP...)
But only then - and who wants WinXP without being forced to !? ;-)
On
Christian Mayer wrote:
BTW: of all Windows versions you only want to use 2000 or XP (= 2000.1).
The rest is either unstable (95, 98, ME) or doesn't run modern software (NT)
This doesn't alter the fact that there are still a lot of perfectly
capable systems out there running 98SE - they shouldn't
Jon Stockill wrote:
Martin Spott wrote:
But only then - and who wants WinXP without being forced to !? ;-)
On the other hand PowerArchiver for Windows easily handles .tar.gz or
.tgz files,
As does winzip AFAICR.
but WinZip is commercial, isn't it !?
Martin.
--
Unix _IS_
Martin Spott wrote:
Jon Stockill wrote:
Martin Spott wrote:
But only then - and who wants WinXP without being forced to !? ;-)
On the other hand PowerArchiver for Windows easily handles .tar.gz or
.tgz files,
As does winzip AFAICR.
but WinZip is commercial, isn't it !?
Yes, but it's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Spott schrieb:
Jon Stockill wrote:
Martin Spott wrote:
But only then - and who wants WinXP without being forced to !? ;-)
On the other hand PowerArchiver for Windows easily handles .tar.gz or
.tgz files,
As does winzip AFAICR.
Christian Mayer wrote:
That's why I prefer .zip. Then at least the WinXP users have a native,
free tool that works out of the box.
tar and gzip come free out of the box on Unix.
We have to get (un)zip separately to get it working. It's either way and
I don't feel like giving windows users the
On Monday, 3 January 2005 23:43, Curtis L. Olson wrote:
Here's a preview of something I'd like to have working in time for the
0.9.8 release. As we go forward it would be nice to have thumbnail
images for each aircraft.
It would be really nice if the level of development was listed as well as a
On Tuesday 04 Jan 2005 17:32, Erik Hofman wrote:
Christian Mayer wrote:
That's why I prefer .zip. Then at least the WinXP users have a native,
free tool that works out of the box.
tar and gzip come free out of the box on Unix.
We have to get (un)zip separately to get it working. It's
Dave Martin wrote:
How about a simple set of links on the same page to applications which can
handle tar.gz on Windows.
ftp://ftp.uni-duisburg.de/Windows/Win32/apps/powarc61.exe
It's freeware,
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
Martin Spott writes:
Dave Martin wrote:
How about a simple set of links on the same page to applications which can
handle tar.gz on Windows.
ftp://ftp.uni-duisburg.de/Windows/Win32/apps/powarc61.exe
$ untarka
untarka v0.34: super untar + untar.Z + untar.gz
contains code (C) by
This is realy a big problem about FG project ;)
If a distro choosed to name the packages *.tgz we have to avoid that extension??
i'm a slak user and i hadn't met any problem with *.tgz files
The slack packages are gzipped tarballs whose filenames end with .tgz
rather than .tar.gz. They
Oliver C. said:
On Tuesday 04 January 2005 11:37, Christian Mayer wrote:
Oliver C. schrieb:
| Could you change the file format from *.tgz to *.tar.gz?
|
| I ask because *.tgz is used by Slackware as a package format (it's a
tar.gz
| file with a install script in it) and this is
Erik Hofman said:
Christian Mayer wrote:
That's why I prefer .zip. Then at least the WinXP users have a native,
free tool that works out of the box.
tar and gzip come free out of the box on Unix.
We have to get (un)zip separately to get it working. It's either way and
I don't feel
Ioan Suciu wrote:
This is realy a big problem about FG project ;)
If a distro choosed to name the packages *.tgz we have to avoid that extension??
i'm a slak user and i hadn't met any problem with *.tgz files
The slack packages are gzipped tarballs whose filenames end with .tgz
rather than
Jim Wilson wrote:
gzip extracts pkzip files.
[EMAIL PROTECTED]:~$ gunzip test.zip
gunzip: test.zip: unknown suffix -- ignored
No it doesn't
--
Jon Stockill
[EMAIL PROTECTED]
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
On 4 Jan 2005, at 23:49, Jim Wilson wrote:
tar and gzip come free out of the box on Unix.
We have to get (un)zip separately to get it working. It's either way
and
I don't feel like giving windows users the benefit of the doubt (the
number of windows _developers_ is frighteningly low compared to
Jon Stockill said:
Jim Wilson wrote:
gzip extracts pkzip files.
[EMAIL PROTECTED]:~$ gunzip test.zip
gunzip: test.zip: unknown suffix -- ignored
No it doesn't
gunzip -S .zip test.zip
Yes it does ;-)
Best,
Jim
___
Flightgear-devel
Jim Wilson wrote:
Jon Stockill said:
Jim Wilson wrote:
gzip extracts pkzip files.
[EMAIL PROTECTED]:~$ gunzip test.zip
gunzip: test.zip: unknown suffix -- ignored
No it doesn't
gunzip -S .zip test.zip
Yes it does ;-)
That only handles a single file in the archive - so it'd work with a
.tar.zip
Jim Wilson said:
Jon Stockill said:
Jim Wilson wrote:
gzip extracts pkzip files.
[EMAIL PROTECTED]:~$ gunzip test.zip
gunzip: test.zip: unknown suffix -- ignored
No it doesn't
gunzip -S .zip test.zip
Yes it does ;-)
Hmmm...think I had one of these:
On Wednesday 05 January 2005 01:47, Jim Wilson wrote:
Jon Stockill said:
Jim Wilson wrote:
gzip extracts pkzip files.
[EMAIL PROTECTED]:~$ gunzip test.zip
gunzip: test.zip: unknown suffix -- ignored
No it doesn't
gunzip -S .zip test.zip
Yes it does ;-)
[EMAIL PROTECTED]:~
Roy Vegard Ovesen said:
On Wednesday 05 January 2005 01:47, Jim Wilson wrote:
Jon Stockill said:
Jim Wilson wrote:
gzip extracts pkzip files.
[EMAIL PROTECTED]:~$ gunzip test.zip
gunzip: test.zip: unknown suffix -- ignored
No it doesn't
gunzip -S .zip test.zip
Yes
Here's a preview of something I'd like to have working in time for the
0.9.8 release. As we go forward it would be nice to have thumbnail
images for each aircraft. I've also included the ability to read a
version string out of the aircraft-set file, and where one doesn't
exist, they script
Curt wrote:
Here's a preview of something I'd like to have working in time for the
0.9.8 release. As we go forward it would be nice to have thumbnail
images for each aircraft.
Do you want aircraft designers to do anything about this?
Regards,
Vivian
Vivian Meazza wrote:
Curt wrote:
Here's a preview of something I'd like to have working in time for the
0.9.8 release. As we go forward it would be nice to have thumbnail
images for each aircraft.
Do you want aircraft designers to do anything about this?
Eventually, probably yes ...
On Monday 03 January 2005 21:43, Curtis L. Olson wrote:
Vivian Meazza wrote:
Curt wrote:
Here's a preview of something I'd like to have working in
time for the 0.9.8 release. As we go forward it would be
nice to have thumbnail images for each aircraft.
Do you want aircraft designers to
On Monday 03 January 2005 22:23, Curtis L. Olson wrote:
Here's a preview of something I'd like to have working in time for the
0.9.8 release. As we go forward it would be nice to have thumbnail
images for each aircraft. I've also included the ability to read a
version string out of the
Oliver C. wrote:
Could you change the file format from *.tgz to *.tar.gz?
I ask because *.tgz is used by Slackware as a package format (it's a tar.gz
file with a install script in it) and this is leading to confusion
when you have Slackware *.tgz files and *.tgz files that are no Slackware
Actually, I think *.tar.gz is more popular that *.tgz.
And makes more sense than .tgz. But it's really a trivial thing.
Anyway you go will work.
On Mon, 03 Jan 2005 18:58:51 -0600, Curtis L. Olson
[EMAIL PROTECTED] wrote:
Oliver C. wrote:
Could you change the file format from *.tgz to
On Tuesday 04 January 2005 00:55, Curtis L. Olson wrote:
Ampere K. Hardraade wrote:
On January 3, 2005 04:43 pm, Curtis L. Olson wrote:
Eventually, probably yes ... at least by maintaining a
version number in the aircraft-set.xml file and by
providing a small thumbnail image (probably with
69 matches
Mail list logo
